Website, Cloud and Mac companion. Last updated 2 October 2026.
Unforgetter is operated by Tiny Agency ApS, CVR 44555689, Sigvej 2, 7700 Thisted, Denmark. Contact hello@unforgetter.com about privacy, access, correction, export or deletion.
We are the controller for applications, account administration and our own support and security activities. Where a business determines the purpose of its team content and we process it on its instructions, that business is the controller and we are its processor. The applicable processing agreement must cover that use, including ordinary personal information. Your organisation should explain its use of team memory to you.
| Activity and data | Purpose and legal basis |
|---|---|
| Alpha application: name, email, AI tools and optional description | Assess your request and arrange access: steps at your request before an agreement (GDPR Article 6(1)(b)); legitimate interest in assessing product fit where that basis does not apply (Article 6(1)(f)). No marketing list. |
| Account, profile, login credentials and sessions | Provide and manage your account and service: Article 6(1)(b). For business representatives, our legitimate interest in administering the business relationship: Article 6(1)(f). |
| Support correspondence, request metadata, IP addresses and security records | Answer questions and protect the service: Article 6(1)(b) where necessary to perform our agreement, otherwise Article 6(1)(f), our interests in support, reliability and preventing abuse. |
| Enabled personal memory: user messages, selected quotes, decisions, preferences, source references and search inputs | Provide the memory functions you enable: Article 6(1)(b) for your own data where necessary for that service. This does not provide a blanket basis for information about other people. |
| Team memory, membership and approved Drive content | For customer-controlled content we follow the customer's documented instructions. The customer must identify its own lawful basis, inform affected people and authorise the processing. OAuth permission alone does not establish that basis. |
We receive information directly from you, from enabled agent hooks and source publication, from your organisation and its members, and from Google Drive when you connect it. Name, email and AI-tool information are required to assess an alpha application; its project description is optional. Account details are needed for an account. Drive is optional. You can use the public website without applying.
Do not submit passwords, API keys, private project documents or sensitive personal information in the application form. Sensitive personal material is outside the external alpha scope. Do not connect material about other people unless you or your organisation have a lawful basis and the required arrangements.
The Mac companion is a client for the Cloud service, not a local-only memory system. When capture is enabled for approved sources, including folder-based project capture and automatic personal/team processing, current user messages are sent to Unforgetter Cloud. We use OpenAI to classify relevant context and candidate statements, maintain memory, and create search embeddings. Classification can receive authorised memory excerpts as context. This happens before the final decision about which statements to save or share.
A private or uncertain passage can therefore be processed by Unforgetter and OpenAI even if it is not saved as memory or shared with a team. A credentials filter blocks some secrets, but cannot guarantee that every sensitive detail is detected. Classification can make mistakes; review shared memory and request corrections.
Personal memory is separated from team-member access. Only separately approved teams can receive eligible shared statements. This does not mean that service providers cannot process the information.
We request that Responses API outputs are not stored as API application state. This setting is not a promise of zero retention across provider security records or every system. We do not claim that all AI processing takes place in the EU.
A connected agent receives the memory or Drive material its access allows. Its provider then processes it under the terms and settings of your agent account. Those providers are separate from the OpenAI service used by Unforgetter itself.
In your signed-in Cloud account, you can allow or block proposed updates for an already approved agent/project pair. This changes that project’s proposal permission within its existing data-class grant. It does not enable processing, connect a new agent or change team access.
Pause in the companion to stop that companion's conversation capture and automatic recall. Previously saved memory remains. Separately authorised Cloud agent connections have their own access.
“Do not save this message” excludes eligible content from capture; it can still be processed for context selection. “Do not share with the team” excludes the message from team capture; eligible personal facts can still be saved. Pause before sending a message if you want to stop this companion's automatic processing.
Disconnecting a device blocks that companion’s access; archiving a team closes team access. Neither is content deletion. Revoking Google authorisation requires removing Unforgetter in your Google account. Disconnect Drive in Unforgetter to remove its stored token; current Cloud versions also clear it when the device is disconnected. Older disconnected-device records may require separate cleanup. Contact us to request deletion, an access copy or an export; there is no complete self-service Cloud deletion/export flow in the alpha.
Connecting Google grants read-only Drive access that is broader than one folder. Unforgetter applies the approved team-folder boundary in its own service and checks access using your connected Google account. A team invitation does not give another member your Google account's permissions.
During setup, your Google name/email and folder or shared-drive listings pass through Cloud so you can choose a folder; these listings are not limited to an already selected folder. We keep an encrypted refresh token so you do not need to sign in for each request. We read files on demand; the Drive reader does not create a document index or save their contents into Unforgetter memory. Read results still pass through Cloud and reach your agent. Sheets reads can include hidden tabs; Slides reads can include speaker notes. Choose folders and files accordingly.
Disconnect Google Drive in Unforgetter removes the stored connection token. To also revoke the authorisation at Google, remove Unforgetter from your Google account's third-party connections. Disconnecting does not erase earlier excerpts held by an agent or its provider.
| Service | What it receives |
|---|---|
| Vercel | Website requests and the alpha form handler. |
| Railway and Postgres | Cloud accounts, authorised memory, processing records and database storage. Our current application and database deployment uses an EU region. |
| OpenAI | Text for classification, memory maintenance and search embeddings. |
| Resend, Porkbun mail forwarding and the receiving inbox | Application details and support correspondence for delivery and a personal reply. |
| Requests made with your authorised Drive connection. | |
| GitHub | Requests for Mac app downloads and updates, including network metadata such as your IP address. |
| The agents you connect | Permitted memory and on-demand source reads returned to that agent. |
An EU deployment does not mean every provider, support activity or onward recipient is restricted to the EU. Processing outside the EEA requires an applicable transfer safeguard, such as an adequacy decision for the relevant recipient or standard contractual clauses with any required supplementary measures. Contact us for the safeguards applicable to your processing and how to obtain a copy. Customer-controlled team processing must be covered by its processing agreement and approved subprocessors.
| Category | Retention and deletion |
|---|---|
| Applications and support | Kept while needed to assess your request, arrange access or resolve the support matter. Any further retention must have a specific purpose, such as a legal obligation or a dispute; it is not permission to keep correspondence indefinitely. |
| Local pending automatic messages | Cleared after confirmed delivery or terminal rejection. Pending messages expire after three days when the companion runs its maintenance. A device that is offline or no longer running may retain its local files until it runs or they are cleared. |
| Cloud raw event text and routing plans | The worker clears these fields after three days during cleanup. This is distinct from selected quotes and published memory. Cleanup depends on the worker running. |
| Saved memory, source quotes and history | Retained to provide the enabled memory service and its source history. Pausing capture, superseding a fact or archiving a team does not erase these records. Deletion requests must cover journal, generations, indexes and other retained copies. |
| Local memory snapshots | The companion can keep recalled memory snapshots on your Mac for context. Expiry prevents their use; it is not proof that the file has been erased. Local cache cleanup must also be covered when you request deletion. |
| Website runtime logs | Our current Vercel Pro plan provides one day of runtime log history. This is a platform log-access window, not a promise that every security record, backup or provider copy is deleted after one day. |
| Account and access records | Kept while required for the account, authorised connections and security. Revocation stops access; it does not itself erase every account or audit record. |
| Provider records and backups | Separate retention can apply. We assess these copies as part of deletion and explain any remaining lawful retention. We do not promise immediate deletion from every provider or backup, or describe an unverified backup lifecycle as a product guarantee. |
Depending on the processing and applicable conditions, you can request access, correction, erasure, restriction or data portability, and object to processing based on legitimate interests. Where we rely on consent, you can withdraw it without affecting the lawfulness of earlier processing. Contact hello@unforgetter.com. We may need proportionate information to verify your identity and protect other people's data.
We respond without undue delay and normally within one month. If a permitted extension is necessary, we explain why within that first month. For organisation-controlled content, contact your organisation; we assist it under our processing agreement. You can also contact us so we can identify the appropriate route.
Automatic classification selects and maintains context; it is not intended to make employment, credit or other decisions with legal or similarly significant effects about you. Do not use it as an automated decision system for those purposes.
You can complain to Datatilsynet, the Danish Data Protection Agency, or another competent supervisory authority.
The public website does not use advertising or analytics tracking. The Cloud service uses necessary authentication and security storage when you sign in or authorise a connection. These functions are separate from your permission to process memory or connect Google Drive.
If we introduce non-essential tracking, we will explain it and obtain the required choice before it runs. We update this notice when the service changes and bring material changes to your attention where required.