Last updated: October 10, 2026
Privacy Policy
Controller and contact
The data controller is Théo Soubra-Belay. For privacy questions or to exercise your rights, contact: theo.soubrabelay@nevermiss-ai.online.
Scope
This policy describes the processing carried out by NeverMiss when you use the website, application, collaboration features and the connectors and sources you choose to associate with NeverMiss, including email services and WhatsApp. Third-party services that you choose to connect also apply their own terms and policies.
Data collected directly
NeverMiss may process information you provide when creating and using an account: name, email address, phone number when provided, authentication provider, avatar, organization, role, team size, preferences, language, time zone, subscription, billing, support requests and actions performed in the product. NeverMiss account passwords are managed by Supabase Auth and are not stored in plain text by NeverMiss.
Data from connectors
Gmail. With your authorization, NeverMiss uses the openid, email and gmail.readonly scopes. Access is read-only and may cover account identity, email address, technical identifiers, threads, senders, recipients, dates, subjects, labels, snippets and message bodies necessary for analysis. Offline access enables the continuous processing you authorize. OAuth tokens are protected server-side. NeverMiss cannot send, modify or delete your emails. Outlook. With your authorization, NeverMiss processes in read-only mode the Microsoft profile, email address, tokens, identifiers, senders, recipients, dates, subjects, previews, bodies and context required for analysis. NeverMiss does not write, modify or delete Outlook emails. Email IMAP connectors using a password. With your authorization, NeverMiss processes the email address and account identifier, the required password or connection secret, technical IMAP identifiers, relevant folders, message identifiers (UID), their validity (UIDVALIDITY) and synchronization cursors, as well as senders, recipients, dates, subjects, content and context needed for authorized features and derived results useful to the service. This connection method is used for compatible IMAP email providers, including Infomaniak. The password or connection secret is encrypted and protected server-side; it is not stored in plain text. NeverMiss uses these connections in read-only mode and does not use these secrets to send, modify or delete your emails. Email content needed for analysis is retrieved when the analysis runs. NeverMiss does not retain exact source snippets in its scan records after processing. Technical identifiers and structured results needed to operate the service may be retained for the periods described below. WhatsApp. You may associate your number with the NeverMiss flow and send messages to the NeverMiss number to create tasks. Necessary content is protected during processing. The full message is erased after successful processing or, only for a failed event that cannot otherwise be replayed, no later than 72 hours. If you have accepted the current Terms, a short exact quote from the part that created each task may be kept separately, encrypted and accessible only to the task owner for up to 90 days. For audio, the quote comes from the transcript. It is not visible to collaborators and is deleted earlier if the task, WhatsApp connection or account is deleted. WhatsApp provides no link to the specific message; the quote helps you search for it in the conversation. Slack. For authorized pre-launch accounts, “Connect and activate Slack” records explicit, versioned consent before OAuth. Detection activates after Slack authorization and security checks; activation stays pending while a check is temporarily unavailable. No processing starts without consent. Target coverage includes joined public channels, private channels you belong to and your authorized direct/group messages; non-joined public channels are excluded. Unknown public membership prevents retrieval. Temporary content is encrypted, purged after terminal processing and limited to 72 absolute hours. Leaving a channel stops collection; rejoining does not backfill the absence. Disabling stops collection and purges temporary content. Disconnecting revokes user access without automatically deleting business tasks. Uninstalling the Slack app or explicitly requesting deletion removes Slack-associated data: internal target ≤7 calendar days; observed Slack obligation 14 business days. Independently proven contributions from other sources are preserved; ambiguous mixed fields are neutralized. Backups and restores follow applicable deletion controls; access must not resume before deletion replay. Availability is limited: no broad rollout. The “Créer une tâche dans NeverMiss” shortcut (the current French label, meaning Create a task in NeverMiss) uses a signed Slack interaction and a personal modal: editable title, optional deadline and explicit confirmation, with no channel publication. Opaque state expires after 10 minutes and does not retain message text; the confirmed title is retained as task data. The encrypted bot credential is shared at app/enterprise/workspace installation level, separate from user credentials. Disconnecting one user does not revoke a still-valid installation bot or another user's access. Uninstall invalidates the bot and triggers deletion; account deletion removes its contribution without deleting other users' independent data. Bounded telemetry contains no Slack text or tokens.
Use of artificial intelligence
Necessary content for automatic detection may be analyzed by Mistral AI using Chat Completions, currently mistral-small-latest. For the actual production organization, API training is opted out, Zero Data Retention is enabled and Labs models are OFF. The applicable DPA is effective March 12, 2026. These settings do not establish exclusively EU inference; detailed region/subprocessor mapping is a separate workstream. The manual shortcut does not require AI. AI is probabilistic: review tasks and deadlines; exhaustive or error-free detection is not guaranteed.
Tasks, analyses and derived data
From connected sources, NeverMiss may produce derived data such as a task, summary, deadline, priority, status, follow-up, signals, labels or an excerpt useful for understanding the result. A task is considered used after an explicit action: editing, completing, archiving, adding a note, changing membership or sharing. Simply generating or viewing a task is not enough. A used task may remain useful after its private source is deleted; it can then no longer open the deleted source message.
Collaboration and sharing
When you share a task, authorized members can see the information actually shared, including its summary, deadline, priority, status, collaborative notes and activity required for collaboration. Private source content, tokens and connections are not shared. A private task is deleted with the account. A shared task or note that remains useful to other members may remain with its author dissociated and shown as “Deleted user”. Private source data is deleted. An item with no surviving member is deleted, and no owner is invented automatically.
Purposes of processing
NeverMiss processes data to create and secure accounts, connect authorized sources, detect and organize important actions, provide tasks and reminders, enable collaboration, manage subscriptions and service communications, answer support requests, prevent abuse, resolve incidents and improve the strictly necessary operation of the product. NeverMiss does not sell personal data or use it for targeted advertising.
Legal bases
Depending on the purpose and context, processing may rely on performance of the requested service or contract, NeverMiss's legitimate interests in security, operation and strictly necessary service improvement, compliance with legal obligations, or your consent where required. Acceptance of legal documents is not general consent to all data processing. Separate consent is requested where a specific legal basis requires it. You may withdraw consent at any time without affecting the lawfulness of earlier processing. Some features can no longer operate after the corresponding authorization is withdrawn.
Providers and processors
NeverMiss uses providers to operate the service: Supabase for authentication, database, storage and server processing; Vercel for hosting and delivery; Mistral AI for AI analysis; Stripe for billing; and Resend for service emails. Google may also provide authentication. Third-party services you choose to connect, such as Gmail, Outlook, compatible IMAP email providers and WhatsApp, are external sources subject to their own terms. Their legal role depends on the processing and applicable agreements; connecting them does not automatically make them NeverMiss subprocessors. These providers process data required for their function under the applicable terms. NeverMiss does not describe their downstream processors, provider retention periods or processing locations as more limited than is actually guaranteed. Cloudflare Turnstile protects sign-in, sign-up and password-reset requests against bots. Cloudflare processes technical signals, including IP address, browser characteristics and site origin, for this protection and to improve bot detection. Further information: https://www.cloudflare.com/turnstile-privacy-policy/
International transfers
Some providers or their processors may process data outside your country or the European Economic Area. Where required, these transfers must be covered by an appropriate mechanism, such as an adequacy decision, standard contractual clauses or another recognized safeguard. The precise location may depend on the provider, service and applicable terms.
Retention periods
NeverMiss applies the following periods: • automatically generated task with no explicit user action: 30 days after creation; simply viewing it does not suspend this period; • task with an explicit user action: while useful and until the applicable deletion; • detailed collaborative activity: 12 months; • invitation: valid for 14 days; expired or revoked invitation: deleted 30 days after expiry or revocation; • unread notification: up to 90 days; read or archived notification: 30 days; • temporary WhatsApp content for a non-replayable retry: up to 72 hours; • WhatsApp quote linked to a task: up to 90 days, deleted earlier if the source, task or account is removed; • encrypted temporary Slack content: up to 72 hours, with earlier purge after terminal processing, disablement or disconnection; • completed email technical scans and jobs: 30 days; • technical account-deletion details: 90 days; • pseudonymized technical proof of deletion: 12 months after completion; • attributable AI metrics: up to 12 months; • NeverMiss operational logs: 30 days; specific security events: up to 12 months where necessary. Account data and other active data are retained while the service is used and then deleted according to the processing, your actions and applicable obligations. Provider logs and backups follow their applicable terms; NeverMiss does not publish an unverified provider period here.
Connector disconnection and revocation
Disconnection stops new reads and removes the connection and associated private source references from NeverMiss. For OAuth connectors, NeverMiss deletes tokens and attempts to revoke access with the provider where technically possible. You can also revoke Gmail from your Google account and Outlook from your Microsoft account. For password-based IMAP connectors, NeverMiss deletes its encrypted password or connection secret. This disconnection does not necessarily change the mailbox password with the provider. You can change it directly with the provider to invalidate that secret globally. For WhatsApp, disconnection removes the link and associated private data. For Slack, disabling task detection retains authorization but stops Events, reconciliation and task analysis for that connection; disconnection immediately removes the connection from runtime, deletes the active local token and starts bounded remote revocation. A task with an explicit user action may survive without its source email or message. Reconnecting Slack reuses the logical identity when it matches, but never automatically re-enables detection or restores purged private content.
Account deletion
Deletion starts immediately after confirmation. Some technical operations may require processing time and continue until completion. NeverMiss normally aims to complete deletion within 24 hours, but this is not an absolute guarantee. Any request still open after 24 hours is flagged for priority follow-up until resolved; after 30 days it becomes critical and requires human intervention. The action is irreversible. New writes are blocked, private data and private tasks are deleted, and connector access is removed or revoked where technically possible. Collaborative items still useful to other members may survive with the author dissociated. A new registration creates an empty account, and individual restoration is not available. NeverMiss retains a pseudonymized technical deletion fingerprint for 12 months after completion. It is used to prevent accidental recreation and secure the deletion process.
Backups
Residual copies may temporarily remain in technical backups subject to rotation cycles and access controls. They are not used to restore an individual deleted account and are processed under the applicable infrastructure terms.
Technical and security logs
NeverMiss retains limited operational logs for 30 days to operate the service, diagnose errors and ensure reliability. Specific security events may be retained for up to 12 months where necessary to investigate an incident, prevent abuse or protect users. NeverMiss seeks to prevent logs from containing unnecessary private content, tokens or secrets.
Audience measurement, performance and fonts
NeverMiss no longer loads Vercel Web Analytics or Vercel Speed Insights in its frontend and does not replace them with another browser-tracking tool. The fonts used by the interface are hosted and served directly by NeverMiss. Loading them does not cause a browser request to Google Fonts.
Google User Data and Limited Use
NeverMiss uses gmail.readonly because the feature needs to read the necessary messages to detect tasks, follow-ups, deadlines and commitments requested by the user. Categories accessed may include account identity, email address, technical identifiers, threads, senders, recipients, dates, subjects, labels, snippets and necessary bodies. NeverMiss may derive tasks, summaries, deadlines, priorities and signals from them. Necessary content is sent to Mistral AI solely to provide this analysis. NeverMiss does not sell Google User Data, use it for advertising, or use it to train or improve a general-purpose model. The actual production Mistral organization has API training opted out, ZDR enabled and Labs OFF; these settings do not establish exclusively EU inference. Disconnection removes local tokens and private references, stops new reads and triggers an attempted Google revocation. You can also revoke access manually in your Google Account. Reconnecting begins new collection and does not restore private history that was previously deleted. NeverMiss's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Individual rights
Depending on applicable law, you may request access, rectification, erasure or restriction of your data, object to certain processing, request portability where applicable, and withdraw consent where processing is based on consent. You may also complain to the competent data protection authority. To exercise your rights, write to theo.soubrabelay@nevermiss-ai.online. Reasonable identity verification may be requested.
Security
NeverMiss applies technical and organizational measures intended to protect data, including access controls, environment separation, encryption in transit, server-side token protection, access restrictions and deletion procedures. No system is completely risk-free. NeverMiss does not claim certifications it has not obtained and encourages users to protect their own accounts and devices.
Changes to this policy
This policy may change to reflect the product, providers or applicable requirements. For a material change, NeverMiss will provide appropriate notice and request renewed consent where required by law or by the nature of the change.
Contact
Data controller: Théo Soubra-Belay. Privacy contact and rights requests: theo.soubrabelay@nevermiss-ai.online.