GDPR
This page explains how Quantinoid LLC handles personal data in Capexo under the General Data Protection Regulation (GDPR) and the UK GDPR, and how you can use your rights. It adds detail to our privacy policy. Last updated 16 April 2026.
1. Who is responsible for your data
Capexo is operated by Quantinoid LLC, a company registered in the United Arab Emirates with operations in the United States and Europe. Who is responsible for personal data depends on the kind of data.
- Programme data: the company that uses Capexo is the controller of the data its people enter, such as plans, risks, issues, decisions, budget figures, meeting notes and the names and roles of team members. Quantinoid LLC is its processor and handles that data only on the company's instructions, to provide the service.
- Account, billing and support data: Quantinoid LLC is the controller of your account details, sign-in records, billing records, support correspondence and the technical data we use to secure the service.
2. Lawful bases
Where we are the controller, we rely on these lawful bases under Article 6 of the GDPR. Where we are the processor, the company that uses Capexo decides the lawful basis for its programme data.
- Contract: to create and run your account, provide the service your company signed up for, take payment and answer support requests.
- Legitimate interests: to keep the service secure, detect and prevent abuse, fix faults, improve the product, and keep evidence of e-signatures. We weigh these interests against your rights, and you can object to them.
- Legal obligation: to keep tax and accounting records and to respond to lawful requests from authorities.
- Consent: where we ask for it, for example for optional emails. You can withdraw consent at any time.
3. Your rights
Under the GDPR you have these rights over your personal data:
- Access: to get a copy of the personal data we hold about you and information about how we use it.
- Rectification: to have inaccurate or incomplete data corrected.
- Erasure: to have your data deleted where there is no longer a good reason for us to keep it.
- Restriction: to ask us to limit how we use your data, for example while we check a concern you have raised.
- Portability: to receive the data you gave us in a structured, commonly used, machine-readable format, or to have it sent to another provider where that is technically possible.
- Objection: to object to processing based on our legitimate interests, and to object to direct marketing at any time.
- Withdrawing consent: where we rely on consent, to withdraw it at any time, without affecting what we did before.
- Complaint: to complain to a data protection supervisory authority, in particular in the country where you live or work, or where you think the law has been broken.
4. How to use your rights
To get a copy of your account data, you do not need to write to us: in the app, open Settings, Account and choose Download your data. You get one JSON file with your account, profile, settings, plan, and the companies and projects you belong to. A project admin can export each project's content from Project admin.
For anything else, email us and tell us which right you want to use. We may ask you to confirm your identity before we act. We will answer within one month, as the GDPR requires. If a request is complex, we may extend this by up to two further months, and we will tell you why. Using your rights is free, unless a request is clearly unfounded or excessive.
If your request is about programme data, the company that uses Capexo is the controller and will decide how to respond. We will pass your request to that company without undue delay and help it answer. We would rather you came to us first, but you can complain to a supervisory authority at any time.
To use your rights, email: hello@capexo.co
5. International transfers
Quantinoid LLC is based in the United Arab Emirates, and our team and sub-processors work in several countries, which include the United States and India. Personal data may therefore be processed outside the European Economic Area, the United Kingdom and Switzerland.
Where personal data goes to a country without an adequacy decision, we protect it with the European Commission's Standard Contractual Clauses, with the UK addendum for UK data, or another safeguard the law allows. These are part of our data processing agreement with customers and of our agreements with sub-processors. You can ask us for a copy.
6. Sub-processors
We use three sub-processors to run the service. Each one is bound by a data processing agreement. We have no AI sub-processor: your AI provider works under your own account and key. Supabase also runs the server functions that pass AI agent requests from the web app to that provider. The same list appears on our security page.
If we add or replace a sub-processor, we will update this list and the security page. Where your data processing agreement provides for it, we will tell you in advance so that you can object.
- Supabase, for the database, authentication, file storage and the server functions that pass AI agent requests to your AI provider
- Vercel, for application hosting and content delivery
- Resend, for transactional email
7. Data processing agreement
Customers can ask us for a data processing agreement under Article 28 of the GDPR. It sets out what we process and why, the instructions we follow, our security measures, our sub-processors, the Standard Contractual Clauses for transfers, how we help with requests from individuals and breaches, and what happens to the data when the service ends.
To request a data processing agreement, email: hello@capexo.co
8. Security measures
We protect personal data with technical and organisational measures that fit the risk. In plain words:
- Data travels over HTTPS between your browser and our services, and Supabase encrypts the database and stored files at rest.
- Row-level security in the database limits records to members of the company that owns them.
- Roles set what each person can edit, and the database enforces them.
- Passwords are stored as hashes by Supabase Authentication, never in plain text.
- Access to production systems is limited to authorised personnel using multi-factor authentication.
- Changes made through the app's record forms are written to an audit log.
- We do not store AI keys: on the web they are saved only in your browser, encrypted with a key the browser cannot export, and our server uses a key only for the one request it comes with, without storing or logging it.
9. Breach notification
If we become aware of a personal data breach that affects programme data, we will tell the company concerned without undue delay, with the information it needs to meet its own obligations, and we will help it respond.
If a breach affects data we control and is likely to put people's rights at risk, we will notify the competent supervisory authority within 72 hours of becoming aware of it where feasible, as the GDPR requires. If the risk to you is high, we will also tell you without undue delay.
10. Retention and deletion
We keep your data while your account is active. When your account is deleted, we permanently delete your data within 30 days. Backups that contain deleted data are purged after 30 days. Audit logs are kept for 12 months.
We keep invoices and payment records for as long as tax and accounting law requires. Signature certificates stay in the project's documents for as long as the project exists. You can download your account data at any time from Settings, Account in the app. Ask us to export anything else or to delete your data, and we will do so unless the law requires us to keep it.
11. AI and your own key
AI is optional, on Pro, Enterprise and Lifetime. Each person turns it on in their own settings and chooses whether to use it for agents and project updates, for speech to text, or both. A company admin can block AI for the company. The providers are Anthropic, OpenAI, OVHcloud, Mistral or Groq. When the desktop app is released, it will also be able to use another OpenAI-compatible service.
Each person adds their own key. The provider they chose works under their own account and that provider's terms, so it is not our sub-processor. In the web app, an agent request goes with the person's key to our server on Supabase, which adds the agent's instructions and what the request needs from that programme's records, which can include the names and roles of team members, and sends it to the provider. Our server uses the key for that one request only. It does not store or log your key, and it does not log the request.
Audio for speech to text, the key test and the list of models go from the device straight to the provider, and we do not store recordings. When the mobile apps are released, they will work as the web app does. The desktop apps, which are coming soon, will send every AI request from the computer straight to the provider.
We store what you keep from AI: an accepted change with the passage it was based on and, for a typed request, its first 500 characters, and each health assessment. AI does not make decisions about people. A proposed change is saved only when a person accepts it.
Speech, including dictation into a record's text fields, is turned into text by your provider's speech service or on your device, as you choose (always on your device if your provider is Anthropic, which has no speech service). In the browser, you can choose on-device speech, so the audio does not leave your device.
12. Cookies and browser storage
The Capexo app sets no cookies of its own. It keeps a few things in your browser's storage, each either needed for the app to work or a choice you made.
To work, it keeps your sign-in session; a short note of a failed Google sign-in, until the message is shown; the plan you picked on the pricing page, until checkout; changes you made offline, until they are sent; and a copy of the app's own files, so it loads quickly and can open offline.
On your device, it remembers your language, light or dark theme, whether the sidebar is collapsed, grid or list view for projects, whether the Gantt chart shows dependency arrows, your starred dashboards and recent projects, and which tips, notices, What's new items and voice privacy note you have already seen, so they are not shown again. In the demo, it remembers the role you chose.
Two things are kept only when you ask for them: your own AI key, encrypted with a key the browser cannot export, until you sign out; and the on-device speech model, once you download it.
On the login and sign-up pages, Google's sign-in service draws the Continue with Google button. When the page loads, your browser connects to Google, which receives your IP address and browser details, and Google sets its own cookie, g_state, to remember the state of its sign-in prompt. Google handles this under its own privacy policy.
You can clear all of this in your browser's settings. Doing so signs you out, resets your choices and drops any changes not yet sent. This website does not store anything in your browser. Neither uses tracking cookies, advertising cookies or third-party analytics.
We do not use cookies or browser storage to track you across websites or to build a profile of you.
13. Children's data
Capexo is a service for businesses and is not intended for anyone under 16. We do not knowingly collect personal data from children. If you believe a child has given us personal data, contact us and we will delete it.
14. Changes to this page
We may update this page when the law, the service or our sub-processors change. If we make significant changes, we will tell you by email or in the app. The date at the top of this page shows when it last changed.
15. Contact
If you have a question about the GDPR, a data processing agreement or how we handle your data, contact us.
Privacy and GDPR questions: hello@capexo.co