Moira Connect Privacy Notice

1. Who is responsible for processing

Moira Solutions B.V. is the controller for public-site interactions, sales enquiries, account administration, billing, security, and Moira's own product operations. In these contexts, contact [email protected] with a privacy question or request.

For content and personal data that a Customer submits to or retrieves through a connected provider account, Customer generally determines the purpose and means of processing and Moira acts as processor under the Data Processing Addendum. The provider may also process data under its own terms and privacy notice.

2. Data categories

The categories depend on how you interact with Moira Connect and which product features a Customer enables. We do not require more data than is reasonably needed for the relevant purpose.

• Identity and account data, such as name, work email, organisation, role, authentication identifiers, and sign-in events.
• Commercial data, such as sales enquiries, subscription status, invoice references, tax information supplied for billing, and payment status. Payment-card data is handled by Stripe rather than stored in the Moira application.
• Technical and security data, such as IP address, device and browser information, request identifiers, audit events, API-key metadata, access logs, and configuration state.
• Customer Data and provider-account data processed only as required to provide the requested connection, event, webhook, support, and recovery workflows.
• Mailbox data from a connected Gmail account, as described in sections 10 and 11.

3. Sources of personal data

We receive data directly from you, from a Customer administrator, from an identity provider or authentication service, from a payment provider, from a connected provider account where authorised, and automatically from use of the public site or service.

4. Purposes and legal bases

We process personal data to provide and support the service, create and secure accounts, administer subscriptions, authenticate users, operate connections, investigate reliability and security events, comply with legal obligations, and communicate about requested services. The legal basis is typically performance of a contract, compliance with a legal obligation, or Moira's legitimate interests in operating a secure, reliable service.

Where consent is required—for example, for a non-essential storage or analytics technology that Moira later enables—we will identify the purpose, obtain a positive choice before activation, and provide a way to withdraw it. The current public site does not enable optional analytics or advertising storage.

5. Recipients and subprocessors

Access is limited to authorised Moira personnel and service providers with a need to know. The current service dependencies are listed on the Subprocessor page, including the purpose and typical data scope for each.

A Customer-selected provider platform is not made equivalent to a Moira-controlled service provider: it receives data only through the Customer's authorised connection and under that provider's own terms and privacy notice.

6. International transfers

Moira and its service providers may process data in countries outside the European Economic Area. Where a transfer mechanism is required, we use an adequacy decision, the applicable EU Standard Contractual Clauses, or another lawful safeguard and apply supplementary measures where appropriate.

7. Retention and deletion

We retain personal data for the period needed for the purpose collected, including the active service term, security investigation, legal, accounting, and dispute-resolution requirements. Retention varies by category and cannot always be reduced to a single time period.

Customer workspace deletion and erasure follow the service's documented controls, including the mandatory seven-day delay before irreversible erasure. We may keep limited information where required by law, necessary to prevent fraud or abuse, or needed to establish, exercise, or defend legal claims.

8. Security and automated decisions

We use technical and organisational measures designed for the risk of the processing, including access controls, scoped credentials, auditability, encryption controls, and operational monitoring appropriate to the service. No internet service can promise absolute security, and Customers remain responsible for their own account configuration and user management.

Moira does not make solely automated decisions that produce legal or similarly significant effects about individuals through the public site or standard account administration. Operational rules may flag a connection, usage condition, or security event for review.

9. Your rights and complaints

Depending on applicable law, you may request access, rectification, erasure, restriction, portability, or objection to processing, and may withdraw consent where processing relies on consent. To make a request, email [email protected] and tell us which relationship or workspace it concerns so we can verify and route it safely.

If Moira processes data as a processor, please direct the request first to the relevant Customer as controller; Moira will assist the Customer as required by the Data Processing Addendum. You may also complain to the supervisory authority that is competent for your habitual residence, workplace, or alleged infringement.

10. Google user data and Gmail

This section applies when a Customer connects a Gmail mailbox through Moira Connect. Moira Connect connects the mailbox on behalf of the Customer's application, using Google sign-in (OAuth). The Customer is the controller of the mailbox content it directs Moira to process, and Moira acts as processor under the Data Processing Addendum, as described in section 1.

Information that Moira Connect receives from Google APIs is Google user data. This section describes what Moira requests, where it is kept, what leaves Moira, and how it is removed.

• Access requested: openid, email and profile, to identify which Google account is being connected, and https://www.googleapis.com/auth/gmail.modify. The gmail.modify scope lets Moira Connect read and search messages, compose and send messages, and label, archive and trash them. It does not permit permanently deleting messages, and Moira Connect does not ask for any broader Gmail scope.
• Scope of synchronisation: Moira Connect synchronises only the Inbox of a connected mailbox.
• What Moira stores: while the mailbox stays connected, Moira stores message content and a search index for it in its connector database. Access and refresh tokens are stored encrypted, using AES-256-GCM with a separate key for each record, which is itself wrapped by a master key.
• Search: the embeddings used for search are generated by a model that Moira hosts itself on its own Railway infrastructure.
• What Moira forwards: Moira sends message metadata — subject, snippet, sender and recipients, identifiers, and attachment names — as events to the Customer's application. Message bodies are not included in these events. What the Customer's application does with that data is governed by the Customer's own privacy notice, and the Customer is the controller for it.
• Disconnecting and deletion: when a connected Gmail mailbox is signed out or erased through Moira Connect, Moira first revokes the grant at Google and then deletes the stored tokens. Erasing the mailbox also deletes the message content and search index that Moira holds for it. Pausing a connection stops synchronisation but does not by itself revoke the grant or delete stored content.
• Mail that leaves the Inbox: when a message is trashed, archived, moved, or deleted at Google, it is permanently deleted from Moira once it has been out of the Inbox for more than 8 days. The purge runs daily and removes the message, its recipients, its stored attachments, its search entry and its event delivery records. Moira keeps only a content-free marker (account, provider message ID, version and time) so that a replayed sync event cannot bring a deleted message back. A message that returns to the Inbox is kept.
• Revoked access: if Google reports that Moira Connect's access to a mailbox has been revoked or has expired, Moira stops syncing it and marks it as needing to be reconnected. If the mailbox is not reconnected within 30 days, Moira erases its copy of the mailbox and the stored credentials. Reconnecting within that period cancels the erasure.
• You can also remove Moira Connect's access yourself at any time on your Google Account permissions page, linked below.

• myaccount.google.com/permissions

11. Limited Use of Google user data

Moira Connect's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In practice, Moira Connect uses Google user data only to provide the mailbox connection, search, and message actions that the Customer and the mailbox owner have requested.

• We do not use Google user data for advertising, including retargeting or personalised or interest-based advertising.
• We do not sell Google user data.
• We do not use Google user data to determine creditworthiness or for lending.
• We do not use Google user data to train, develop or improve AI or machine-learning models.
• Moira personnel do not read Google user data except with the user's consent, for example to resolve a support request; where necessary to investigate a security issue or abuse; or where required to comply with applicable law.

• Google API Services User Data Policy

12. The Moira Connect browser extension

Moira Connect offers a browser extension that lets a person operate their own LinkedIn account from their own browser, on instruction from the Moira Connect workspace of the organisation they work for. The person who links their browser is called the member here. The extension performs its requests inside the member's own signed-in LinkedIn session. It does not read or send the member's LinkedIn password, and it has no permission to read browser cookies.

Consent. Before a browser is linked, the connection page shows the member what the extension reads, what it does on their LinkedIn account, where the data goes and how long it is kept, and how to disconnect. Linking requires the member to tick a box and press a button. The extension reports that the member agreed and which version of the text they were shown, and Moira Connect records that report with the time. Moira Connect cannot see whether the box was ticked; it records the agreement the extension reports. When the text changes, the extension shows the member what changed and asks them to agree again, and does no work on their account until they do. Browsers linked before this version, without an agreement on record, keep working until the grace date and are asked to agree meanwhile; after that date they are held until they agree.

The extension contacts LinkedIn to carry out these actions and sends the following categories of data to Moira Connect. Moira Connect provides the data to the organisation through its configured API, events and webhooks, and uses the infrastructure providers identified on the Subprocessor page. The organisation is responsible for its downstream uses and recipients:

• Actions taken on the member's LinkedIn account are only those on the extension's fixed list: looking up profiles, sending and handling invitations, starting conversations and sending messages, sending InMail, and reading conversations, messages and connections. They are taken in the member's own session and appear on LinkedIn as the member's own actions. The extension refuses any other instruction and reports the refusal. Daily and hourly limits apply to sending invitations, starting conversations, sending messages, sending InMail and looking up profiles. They do not apply to accepting, ignoring or withdrawing invitations, or to the reads that keep conversations and connections in step.
• When a second browser asks to link, the server records the requesting network, shortened to /24 for IPv4 or /48 for IPv6, shows it to the member's team on the approval screen, and deletes it when the request is decided or expires. It is cleared as soon as the request is decided, and one left on an expired request is removed by a daily sweep, within a day of expiry. The full address is not kept, and no country is recorded. The network is reported by the edge proxy in front of Moira Connect, so it is a hint for the person approving and never grants anything by itself. To limit abuse, requests carrying an unknown pairing id or device token are counted per shortened network (/24 for IPv4, /64 for IPv6) using a keyed one-way code, removed by a daily sweep and kept at most about a day.
• Not collected: the member's LinkedIn password or cookies, financial information, health information, the member's country, or any location other than the location shown on the profiles that are looked up and the shortened network described above. The extension does not read other web pages.
• Data transmitted by the extension is not sold to third parties, is not used for advertising, is not used for any purpose unrelated to the extension's stated purpose, and is not used to determine creditworthiness or for lending.
• Moira Connect's collection, use and transfer of information through this extension adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. We use extension data only to provide or improve its disclosed connection features and their necessary security and reliability operations. Transfers are limited to necessary service delivery, applicable law, security or fraud protection, or a corporate transaction after the required prior consent. Moira personnel do not read extension user content except with explicit consent for the specific data, for aggregated and anonymised internal operations, where necessary for security or abuse prevention, or as required by law.
• To disconnect, the member chooses Disconnect this browser in the extension, or the organisation disconnects it from its dashboard. This takes effect at once and leaves the member's LinkedIn session untouched. It does not by itself erase what was already stored; to have that erased, ask the organisation's administrator or write to [email protected].

This section describes the extension as built, at data disclosure version 2026-11-02.1.

13. Changes to this Notice

We may update this Notice to reflect legal, technical, or operational changes. The version and publication date above identify the current notice. Where a change is material, we will use a reasonable additional notice method appropriate to the change and our relationship with you.