Who is responsible?
Five Dots is a product of Revenue Wizards B.V., the controller responsible for the personal data described here.
Vijzelstraat 68–78, 1017 ES Amsterdam, Netherlands.
Privacy contact: Haris Odobasic — privacy@fivedots.ai.
Questions about Five Dots or this notice: help@fivedots.ai. Requests about your personal data go to the privacy contact above.
This notice covers this website, enquiries and the waitlist, the account area at app.fivedots.ai, and the Five Dots plug-in for your AI assistant. The website itself does not connect to your AI assistant or CRM, access their contents or create a product account.
Information we process
Visiting the website
Our hosting provider, Vercel, processes technical request information such as your IP address, requested page, request time and browser information to deliver and protect the website. Operational and security records may also be generated. Our legitimate interests are operating a reliable website, investigating faults and preventing abuse.
Contacting us
We use your contact details, message and information you choose to share to answer enquiries and manage correspondence. This is based on our legitimate interest in responding to you, or taking steps at your request before entering a contract where applicable. We keep enquiries for up to five years after resolution, reviewing necessity and deleting information earlier when it is no longer needed. A specific legal obligation or ongoing legal claim may require longer retention.
The waitlist
When you sign up, we use your first name, email address and selected AI assistant to manage your registration and send relevant Five Dots availability updates and invitations. We record signup time, consent wording and subscription status. Selecting an AI assistant does not grant us access to it.
By signing up, you consent to join the Five Dots waitlist and receive occasional Five Dots product updates from Revenue Wizards B.V., including availability news, feature announcements and an access invitation. The signup button and the explanation beside it communicate this purpose before you submit. You can withdraw through an unsubscribe link or our privacy contact. Withdrawal will not affect the lawfulness of earlier processing. Joining will not subscribe you to unrelated Revenue Wizards marketing.
We keep waitlist profiles until withdrawal, closure of the waitlist or five years after signup, whichever comes first, with earlier deletion where no longer necessary. Continued participation after five years will require renewed consent. Minimum consent and unsubscribe records may be retained where necessary to demonstrate compliance and prevent unwanted messages; they will not be used for marketing.
Guides you unlock with your email
Some guides on this website, such as “Claude as your RevOps system”, open in full after you enter your email address. We use your email address and the language of the page to give you access, to send you one email with a personal link that opens the guide on your other devices, and to send you occasional Five Dots emails. We record when you signed up, which guide and page you used and the consent wording shown beside the form. Entering your email does not create a Five Dots account or add you to the waitlist.
By entering your email, you consent to receive occasional Five Dots emails from Revenue Wizards B.V., as stated beside the form. You can withdraw at any time through the unsubscribe link in every email or through our privacy contact; you keep access to the guide. If you had unsubscribed before, we do not subscribe you again and do not email you. Withdrawal will not affect the lawfulness of earlier processing.
We keep guide sign-ups until you withdraw or five years after you signed up, whichever comes first, with earlier deletion where no longer necessary. Minimum consent and unsubscribe records may be retained where necessary to demonstrate compliance and prevent unwanted messages; they will not be used for marketing.
Using Five Dots in ChatGPT, Codex or another AI assistant
Five Dots supplies audit methodology, a knowledge base and a skills library through its MCP server at app.fivedots.ai. Your assistant sends the tool inputs below to our server and receives our responses. The connection also identifies your Five Dots account and, when you sign in as a member, that member. This is not an anonymous service.
Your assistant uses your separately authorised connections to read your business systems and keep your work in a workspace you choose. Five Dots does not connect directly to your CRM or workspace and does not receive their credentials. Our tools do not ask for CRM records, customer or deal names, financial figures, interview transcripts, audit findings, scores, reports or your conversation history. Those remain with your assistant and chosen services, under their own permissions and privacy terms.
Keep search and help inputs to generic topic words. If you or your assistant put personal or confidential information into a tool input, that information is transmitted to Five Dots for processing even though it is not requested. A tool response may repeat an input, for example a search term or an unrecognised identifier. Do not put passwords, API keys, payment-card details, government identifiers or health information into these fields.
Tool inputs, purposes and outputs
| Tool | Input and purpose | Output and storage |
|---|---|---|
get_playbooklist_modules | No tool-specific input. Retrieve the session guide or audit catalogue. | Our guidance, module names, versions, steps and estimates. A service event records the call. |
start_run | Connected-tool names, chosen audit scope, workspace status (existing, newly created or chat only), and an optional target completion date. Used to plan an audit and its schedule. | A run identifier, methodology version, module plan, estimates and any calculated due dates. We store the run linked to your account and starting member, its scope, connector names, planned modules, version and timestamps. The workspace status and target date are processed to produce the response, but are not saved in the run record. We do not receive the workspace address or its contents. |
get_instructions | Module identifier, optional run identifier, and an optional data or interview mode for a reference copy. Used to select the methodology and check that a module belongs to a run. | Steps, scoring criteria, an empty findings structure, remediation guidance and relevant knowledge references. No completed findings are submitted. Service events record the fetch and any run identifier, without recording which module a run has reached. |
search_knowledgeget_knowledge | Generic search words, optional domain and result limit; or a knowledge-node identifier. Used to find and retrieve our reference material. | Matching titles, summaries, identifiers, links and available article text. Search text is processed for the request and is not saved in our application database or routine service-event log; the fact that the tool was called is recorded. |
list_skillsget_skill | Optional category and generic search words; or a skill identifier and optional supporting-file path. Used to select a playbook or one of its reference files. | Skill listings, versions, attribution, playbooks and supporting files available to the account. Search text is not saved in our application database or routine service-event log; the call is recorded. A file path selects a file in our library, not a file on your computer. |
request_help | An optional article identifier or generic help topic. Used to select product help. | Help articles and an email template for you to complete in your own assistant. The topic is not saved in our application database or routine service-event log; the call is recorded. This tool does not create a support ticket or send email. If you email us for support, we receive your message and any information you include. |
Responses go back to the assistant provider you use, such as OpenAI for ChatGPT or Codex, or Anthropic for Claude. They include the requested methodology, any run plan and relevant access or error messages. The provider processes these responses as part of your conversation under its own terms and your settings. If you authorise your assistant to save or share work through another service, that service also receives the material you choose to send. Disconnecting Five Dots does not delete those separate copies.
Account and connection information
We process the account name and plan; member names, work email addresses, roles, membership status and invitations; identity-provider user and organisation identifiers; domain-joining settings; onboarding and last-sign-in timestamps; and billing and subscription identifiers and status from Stripe. Authentication requests carry credentials or tokens so we can verify access. Sign-in is handled by WorkOS. Where an API key is issued, our database stores its hash, label, status and use timestamps rather than the key itself. These details are separate from the business records used in your audit. We also process the primary AI assistant chosen when the account is created, or later changed by an administrator, to tailor onboarding emails and group accounts; choosing it gives us no access to that assistant. When the account is created we also ask how you found Five Dots (online search, AI search, social media, a referral or other) and, if you choose a referral, the name you enter for who referred you. We use this answer to understand which channels bring new accounts. Enter only a name you are comfortable sharing with us.
Service events and how we use them
For tool calls we retain the tool name, account and member identifiers where available, time, outcome, response duration and any supplied run identifier. Connection, authentication, rate-limit and account-administration events are also recorded. Where an account cannot access some content, we record the access limitation and may record identifiers of our own modules, articles or skills. Content identifiers are omitted when that request carries a run identifier. These records describe service use, not your audit findings or completed work.
We use these records to operate and secure the service, enforce account access, investigate problems, understand feature use and provide onboarding assistance. The service can use account age, audit-plan creation, instruction-fetch counts and access-limit events to select onboarding emails. Marketing emails about plans require an opt-in; onboarding emails include an unsubscribe control. Essential sign-in, invitation, billing and account-closure notices are separate.
For Free-level accounts, we also use instruction-fetch counts, repeated access-limit responses and team size to flag possible interest in paid features to our team. The stored signal consists of the account identifier, signal type and time. The account name and signal may be sent to our internal Slack, and staff can review them in our account console. We also record Free-plan and paid-plan milestones to measure conversion. These signals are not evidence that your audit is complete and do not include its results. You can object to use of your personal data for direct marketing, including related profiling, through our privacy contact.
Last sign-in and tool activity can also be used to identify inactive Free accounts and send closure warnings. Our inactivity process, when enabled, warns administrators before closure after 180 days without activity and allows at least 30 days after closure before permanent deletion begins. Signing in before deletion begins reopens the account. Cancellation of a paid subscription, disconnecting a plugin and requesting deletion are different actions. An account administrator can also delete the account in Account settings. Access ends for everyone at once and any subscription is cancelled; we keep the account’s records for 30 days so that it can be restored on request, then delete them permanently in the same way as an inactive account. Signing in does not restore a deleted account.
Our bases for these uses are performance of the service contract where applicable and our legitimate interests in secure operation, customer assistance and understanding product use. Promotional email subscriptions rely on consent. You can object to processing based on legitimate interests; direct-marketing objections apply without needing to give a reason.
Retention and deletion
Product account records are stored in an EU-hosted database. Our published account policy is to keep account and member records for the life of the account and delete them within 90 days of closure, except records needed for legal obligations or claims. Run plans, account-linked service events, access records and account signals are included in an account deletion. Closing an inactive account first suspends access; it does not immediately erase its data.
The inactive-account deletion process removes the account’s product records and WorkOS organisation. A WorkOS user who belongs to another account is retained for that account. A separate closure record remains with the account name and identifier, organisation identifier, dates, reason and any Stripe customer identifier, to record the deletion and prevent an old connection from recreating the account.
Account deletion does not automatically remove CRM and mailing-list contacts, Stripe billing records, incident reports, analytics events or internal Slack messages. A privacy deletion request covers these separate locations too, subject to any applicable legal retention or security need. Our published incident-report period is 12 months. Hosting logs and backups follow the configured provider retention; browser cookie lifetimes are not the same as the retention of server-side analytics events. You can ask our privacy contact for the periods applying to your information and request earlier deletion where applicable.
Contacts, product messages and internal notifications
Website waitlist registrations are stored in Resend and copied into our internal contact list in the product database. Account creators are also recorded there. We may hold your name, work email, company, selected assistant, source of the contact, consent and unsubscribe status, stage, tags, notes and follow-up dates. Staff may add business contacts from enquiries or professional contact sources. We use this information to manage the relationship and respond to your requests; an entry in our contact list does not itself subscribe you to marketing.
Guide sign-ups are stored in Resend too. They are not copied into our internal contact list or announced in our internal Slack.
Account creation offers a separate optional marketing checkbox. When you opt in, we record the wording, date and subscription choice and synchronise it with Resend. Resend’s unsubscribe status takes priority. We record which lifecycle email was sent, when and to whom to avoid duplicate messages. Your name, work email, account name or chosen assistant may also appear in a signup notification in our internal Slack.
Waitlist retention is described above. Enquiry and relationship notes follow the correspondence period of up to five years after resolution, with earlier deletion when no longer necessary. Minimal consent and suppression records are retained as needed to respect your choices and demonstrate compliance. You can request deletion of a contact record separately from closing a product account.
Providers and international transfers
Access is limited to authorised people and providers who need information for the purposes below. The information processed depends on how you interact with us; joining the waitlist does not automatically share your details with every provider.
| Provider | Purpose | Information handled |
|---|---|---|
| Vercel | Website and product hosting and protection | IP address, requested page, request time, browser information, and operational and security records. |
| Ahrefs | Website traffic analytics, without cookies | Pages visited, referring site, browser and device type, and approximate location derived from the IP address. Privacy policy ↗︎ |
| Google Analytics Google Ireland Limited | Website traffic analytics, with cookies, only if you accept them | Pages visited, referring site, browser and device type, approximate location, and a cookie identifier that recognises a returning browser. Google may process this information in the United States. Privacy policy ↗︎ |
| PostHog PostHog, Inc. | Website and product usage analytics. On the website with cookies, only if you accept them; in the account area without cookies | Pages visited, clicks, referring site, browser and device type, approximate location and errors. On the website, a cookie identifier that recognises a returning browser. In the account area, your sign-in user identifier and role. Hosted in the European Union. Privacy policy ↗︎ |
| Resend Plus Five Five, Inc. | Waitlist contacts, guide sign-ups, Five Dots emails and product notifications | Name, email address, selected AI assistant, consent and subscription status, onboarding and account-notice messages, operational alerts, message content, delivery and unsubscribe information. Privacy policy ↗︎ |
| Slack | Internal collaboration, signup notifications and account-interest signals | Name, work email, account name, selected assistant, how you found Five Dots and any referrer name you entered, signup information, account-interest signals and information you choose to share in correspondence. |
| ClickUp | Project management and internal collaboration | Project contacts, tasks and related correspondence. |
| Google Workspace | Identity management, business email and collaboration | Account identifiers, contact details and email content. |
| Stripe | Payments and billing when you purchase services | Billing contact details, transaction information and payment details submitted to Stripe. Privacy policy ↗︎ |
| WorkOS | Sign-in, invitations and sign-in emails for the account area and the plug-in | Name, work email address, sign-in identifiers and the IP address at sign-in. Hosted in the United States. Privacy policy ↗︎ |
| Supabase | Product database, hosted in the European Union | Account, member, run, service-event, contact, consent, email-history, account-signal and closure records, and incident reports described above. Privacy policy ↗︎ |
| Anthropic | AI assistance for our internal engineering and development | Code, prompts and technical context supplied for those tasks. |
The website submits waitlist registrations to Resend; a copy is synchronised to our internal contact list in the product database. Our internal use of Anthropic is separate from your use of an AI assistant with Five Dots and does not give our engineering tools access to your CRM records or audit findings.
Stripe may act as a processor or an independent controller depending on the activity.
These providers support different activities and are not all subprocessors of customer product data. Where a provider processes personal data on our behalf, the relevant data-processing terms apply.
We do not sell your personal information.
Providers may process personal information outside the European Economic Area. Applicable transfers require an adequacy decision or appropriate safeguards, such as European Commission Standard Contractual Clauses and any necessary supplementary measures. Contact us for details of safeguards applying to your information and how to obtain a copy. Information may also be disclosed when required by law or necessary for legal claims.
Your controls and rights
You can disconnect Five Dots in your assistant’s plugin or connector settings to stop further calls from that connection. Account administrators can manage members and their access; contact support to revoke an issued API key. Removing a connection stops that connection’s future access but does not close your Five Dots account or erase information already retained.
To request an export, correction or deletion of your Five Dots account data, contact the privacy address below and identify the relevant account. Tell us if your request also covers contact-list records, analytics or support correspondence so we can locate all relevant information. You do not need to know our internal identifiers. Manage or delete conversations and workspace documents through the assistant and storage services holding them. Account administrators can also delete the account themselves under Account settings, Danger zone, as described above.
Use the unsubscribe link in product or lifecycle emails to stop those messages, and Cookie settings on this website to withdraw website analytics consent. Essential account and security messages may still be sent while needed to provide the service. You can object to direct marketing and related profiling at any time.
Depending on the circumstances, you can request access, correction, deletion, restriction or a portable copy of information you supplied. You can object to processing based on legitimate interests, always object to direct marketing, and withdraw consent at any time.
Email privacy@fivedots.ai. We normally respond within one month. If a permitted extension is necessary, we will explain why within that month. We may request proportionate information to verify your identity. Requests are normally free.
You may complain directly to the Autoriteit Persoonsgegevens, PO Box 93374, 2509 AJ Den Haag, Netherlands, or the supervisory authority where you live or work or where an alleged infringement occurred. You do not have to contact us first.
We use automated rules for access, service messages and inactivity handling as described above. We do not use your audit findings to make decisions about you. Contact us to query an account restriction or request human assistance.
Updates to this notice
We will revise this notice when our practices change and explain material changes where appropriate. New purposes requiring consent will require fresh consent.