Marqov Platform Privacy Policy
BetaLast updated 16 November 2026
This policy describes the personal data the Marqov platform (app.marqov.ai and the Marqov API) handles: what we collect, what we use it for, who processes it for us, how long we keep it, and the choices you have. We collect what we need to run the platform, and we do not sell personal data.
The platform is operated by Marqov, Inc., a United States corporation (“Marqov”, “we”, “us”), which is responsible for the personal data described here. The marqov.ai website has its own privacy policy. Your use of the platform is also covered by the Terms of Service.
1. What we collect
Account details
Your email address, first and last name, and password. Passwords are stored hashed by our authentication provider; we never see them in plain text. We also record the invitation code or team invitation you used, and which version of the Terms and of this policy you agreed to, and when.
Access requests
If you request access, the name, email address, organisation and note you give us, whether and when you confirmed your email address, and the outcome of the request.
Teams
The teams you belong to, your role in each, and invitations sent by team owners and admins, including the invited email address.
Your content
The scripts, circuits, programs, parameters, projects, documents and images you save, and the jobs you run with their status, timing, results and cost. We would rather not hold personal data inside your programs or results, so please leave it out unless you need it.
Keys and provider credentials
- For each Marqov API key we keep a hash of the key (the key itself is shown to you once), a short prefix so you can recognise it, its name, permission level and spending limit.
- Credentials you connect for your own provider accounts are stored encrypted, with the encryption key held in our database provider’s secrets vault, and team members cannot read them back once saved. For Amazon Braket on your own AWS account we store no access keys: you grant Marqov an IAM role that it assumes for each job.
Billing records
Card details go straight to our payment processor, Stripe, and never reach our servers. We keep the records needed to run your team’s prepaid balance: amounts, dates, Stripe customer and payment references, holds, charges and refunds.
Technical data
IP addresses and user and API key identifiers, used to rate-limit requests (including sign-up attempts); request logs kept by our hosting providers; and error reports, from which we strip personal and sensitive fields before they are sent. We do not record session replays.
Cookies and analytics
The platform sets only the cookies it needs to work:
- sign-in cookies from our authentication provider, Supabase (their names start with
sb-); marqov_active_team, which remembers the team you are working in.
We use no advertising or tracking cookies. Page views and page speed are measured with Vercel Web Analytics and Speed Insights, which do not use cookies. Stripe sets its own cookies on its checkout page, under its own privacy policy. Your browser may also keep small preferences, such as your theme, in local storage.
Messages to us
If you email us, we keep the conversation so we can help you and refer back to it.
2. How we use it
- To create and run your account and team, sign you in and review access requests.
- To run your jobs, store your content and results, and show you your usage and costs.
- To take payments, manage the prepaid balance and issue refunds.
- To send service email you need, such as address confirmation, password resets, access approvals, team invitations and share notifications. The platform does not send marketing email.
- To keep the platform secure, prevent abuse and fraud, and find and fix faults.
- To understand, in aggregate, how the platform is used so we can improve it.
- To meet legal obligations, such as keeping tax records and answering lawful requests.
We do not use your content to train artificial intelligence or machine learning models. Where EU or UK data protection law applies, we rely on the contract with you for the first four uses, on our legitimate interests for security and improvement, and on legal obligation for the last.
3. Who processes data for us
These service providers help us run the platform and process data only to provide their service to us:
- Supabase: database and authentication, including some account emails.
- Vercel: hosting for the web application and API, and cookieless analytics.
- Amazon Web Services: the servers that run jobs and hosted code, file storage, and Amazon Braket simulators and quantum hardware.
- Temporal Technologies (Temporal Cloud): workflow orchestration; job data passes through it.
- Stripe: card payments, prepaid balance top-ups and refunds.
- Resend: delivery of the email we send.
- Sentry: error tracking, with personal fields removed first.
- Upstash: rate limiting, using IP addresses and account identifiers.
- Google Workspace: our own mailbox, when you write to us.
Quantum providers. When you run a job, its program, circuit and parameters go to the provider that runs it, for example Amazon Braket (and the hardware provider of the device you choose there), Microsoft Azure Quantum or IBM Quantum. Providers receive your job, not your account details, unless you connect your own provider account, in which case they handle it under your agreement with them.
We also disclose data when you ask us to (for example by sharing a link or inviting someone to your team), when valid legal process compels us (we will try to tell you first unless we are not allowed to), and, with notice, to a successor if Marqov is acquired or merges. Authorised Marqov staff access an account only when needed to run the platform, fix a fault, answer a support request or investigate abuse.
4. How long we keep it
- Account, team and content data: for as long as your account is open.
- When you ask, we delete or anonymise your account data, except what we must keep by law. Email ops@marqov.ai to ask; deletion is carried out by our staff. Backup copies are removed as backups expire.
- Billing and payment records: for as long as tax and accounting law requires.
- Logs and error reports: only as long as needed for security and fixing faults.
5. Security
Data is encrypted in transit with TLS. Provider credentials are encrypted in the database, API keys are kept only as hashes, and access to production systems is limited to authorised staff. No system is perfectly secure; if a breach affects your personal data, we will tell you and the authorities as the law requires. Please report security issues to ops@marqov.ai.
6. Your rights and choices
Wherever you live, you can ask us to:
- confirm what personal data we hold about you and give you a copy;
- correct it;
- delete or anonymise it, except what we must keep by law (this may mean closing your account);
- limit how we use it, or object to a use based on our legitimate interests;
- provide it to you or another service in a portable format.
You can change your name in your profile and download your results through the application or API. For anything else, email ops@marqov.ai. We may need to confirm your identity, and we will reply within the time the law requires. Using these rights will not affect how we treat you.
You may also complain to a data protection authority, such as the authority in your EU country, the UK Information Commissioner’s Office or the Office of the Australian Information Commissioner. California residents have the rights above under California law; we do not sell personal information or share it for cross-context behavioural advertising.
The platform is not intended for anyone under 18, and we do not knowingly collect their data. If you think a child has given us personal data, contact us and we will delete it.
7. International transfers
Marqov is a United States company and our service providers process data mainly in the United States, so if you are elsewhere your data is transferred there. For transfers from the EU, the UK and Switzerland we use the safeguards our providers offer, such as Standard Contractual Clauses. A quantum provider you choose may process your job in its own region.
8. Changes to this policy
We will update this policy as the platform changes and show the new “Last updated” date above. For a significant change, we will tell you in the platform or by email before it takes effect.
9. Contact
Marqov, Inc. Questions about this policy or your data: ops@marqov.ai.