Privacy
Last updated 24 October 2026
Who we are
MayaDoIt is operated by MayaDoIt AI LLC. This policy covers the website at mayadoit.ai, the MayaDoIt iOS and Android apps, the MayaDoIt desktop application, and the API behind them. Questions, requests and complaints all go to support@mayadoit.ai.
What we collect
- Your account. Email address, password (stored only as an argon2id hash, never in a form we could read), and your name and phone number (both required).
- Your profile. Whatever you enter in the profile builder so Maya can fill applications as you: work history, education, skills, location, work authorisation, and the voluntary demographic answers employers ask for. You choose what to put there, and a question your profile does not answer is a question Maya does not answer either.
- Employer accounts. Login email addresses and encrypted passwords for employer accounts Maya creates or recovers to carry out your authorized applications.
- Your applications. For each one: the employer, the role, the link, the outcome, and the resume Maya wrote for it, so your dashboard can show you what happened and hand the resume back.
- Your computers. The machine name, operating system, app version and time zone of each device running Maya, so you can see which computers are on your account and switch one off.
- Payment. Handled entirely by Stripe. We receive a subscription status and a customer reference. We never see or store your card number.
- Website measurement. The Google tag loads on website pages and can receive ordinary browser and request information under Google's policies. After the registration API accepts the form, MayaDoIt sends one
sign_upevent. That event contains no form values, profile facts, mailbox data, or application data.
Connected mailbox access, and its limits
If you connect Google Gmail or Microsoft Outlook, Maya can finish applications that pause for an emailed security code and record outcomes for applications shown in your dashboard. With K9 or K9+, you can separately enable hiring-manager outreach from your connected mailbox. Google grants gmail.modify. Microsoft grants openid, offline_access, User.Read, Mail.ReadWrite, and Mail.Send. Microsoft identity access signs you in, identifies the connected mailbox address and lets the encrypted grant work between runs.
- Recoverable security-code cleanup. After a confirmed application using a security code, Maya moves that exact consumed code message to Gmail Trash or Outlook Deleted Items. It remains recoverable. Maya does not permanently delete mail, change other labels, or make unrelated mailbox changes.
- Outreach requires your separate choice. Connecting your mailbox does not enable sending. On K9 or K9+, enable outreach in Account → Outreach to authorise a personalized introduction with your tailored resume attached after a confirmed application, when Maya finds a published hiring contact. Maya sends through your selected mailbox. Messages accepted by the provider appear in its Sent folder once processed. Acceptance does not confirm delivery to the recipient. The dashboard keeps the outreach status with that application. Turn outreach off at any time to stop new sends. A message already accepted by your email provider cannot be recalled by this setting.
- Sending permissions. Google's
gmail.modifycovers the bounded reads, the sending and the recoverable Trash moves described above. Maya does not create Gmail drafts. Microsoft'sMail.ReadWritedoes not grant send authority. Outreach also requiresMail.Send. Older connections may need to be reconnected. Changing or reconnecting your mailbox requires you to enable outreach again for that connection. - Security-code reads stay narrow. When an application is waiting, Maya searches only the few minutes after the application asks and can narrow that search to the employer domain. The code is typed into that employer's form.
- Outcome tracking is incremental. On first connection, Maya checks your mailbox's full history to find job-related messages. Afterward, Google or Microsoft supplies only mailbox changes since the saved checkpoint. Maya reads the sender, subject and preview of each new message to decide whether it belongs to a tracked application.
- Full text is exceptional. Application-related email text may be sent to Anthropic’s commercial API or Amazon Bedrock for inference, including outcome classification. For Gmail, Maya also fetches related calendar invitation (ICS) attachments to record interview details. For Outlook, Maya reads message bodies, not attachments. This does not use the Google Calendar API. Arbitrary Gmail attachments are not read. Sanitized application-email text and derived insights are sent to Voyage AI to create embeddings for owner-scoped retrieval and label correction, not generalized model training. A bounded pending copy of an authenticated recruiting message may be retained for up to seven days when classification must be retried or the message arrived before its application row.
- What is retained. Maya stores the provider message identifier, the matched application when there is one, the outcome category and the provider's reported message receipt time when valid (otherwise the time processed). Unmatched identifiers are retained while your account is open so an expired checkpoint does not make Maya read the same mail again. Application outcomes, interview history, sanitized source text, derived insights and embedding vectors are durable account data, not subject to the seven-day pending-mail limit. Closing the account deletes them. Disconnecting a mailbox stops further access but does not erase retained history or vectors.
- Encrypted, and yours to revoke. The refresh token is encrypted at rest with AES-256-GCM under a key held separately from the database. Disconnect at any time from your account page, which deletes Maya's token and stops further access. Maya also asks Google to revoke a Google grant. Revoke a Microsoft grant from your Microsoft account if you want it removed provider-side.
- Never used for anything else. MayaDoIt does not use your mail for advertising or to train generalized AI models. Owner-scoped retrieval and label correction are application features, not generalized model training. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Application access and browser data
- When an employer site requires an account, Maya may create or recover it on your behalf and store its credentials encrypted in the employer-account vault. The account remains yours. Signing in with Google, Microsoft or Apple through OAuth does not give Maya your identity-provider password.
- During application automation, Maya reads employer pages and may capture browser-page screenshots.
- Your session is kept in your browser's local storage because you asked to stay signed in.
Where it lives
Our application servers and stored account data are hosted on Amazon Web Services in the United States (us-east-1); the inference and embedding providers below also process the data described above. Data is encrypted in transit with TLS and at rest by the storage layer. The public API is served through an API gateway. MayaDoIt account passwords are hashed with argon2id; employer-account credentials are encrypted in the vault. Mailbox refresh tokens carry a second layer of application-level encryption.
Who else touches it
We do not sell your personal information, and we do not share it for anyone else's marketing. We never have.
Service providers include AWS for hosting and Bedrock inference, Anthropic’s commercial API for inference, Voyage AI for embeddings, and providers for payments, email delivery and Google Ads conversion measurement. The sign-up event carries no registration fields. The mailbox-processing data shared with inference and embedding providers is described above. From approximately 15:09 UTC on 24 October 2026, our Voyage AI organization’s model-training opt-out is enabled; this does not establish historical handling or imply zero data retention. Provider retention follows the applicable service terms and settings, separately from MayaDoIt’s application-retention periods. Write to support@mayadoit.ai for the current list of providers by name.
We disclose personal information otherwise only where the law requires it, and we will tell you unless we are forbidden to.
Mobile numbers and SMS consent
We use your mobile number to deliver requested verification and sign-in codes. We do not sell mobile numbers or SMS consent, or share them with third parties or affiliates for their marketing or promotional purposes. We share necessary information with messaging service providers to deliver and operate these messages.
How long we keep it
Your profile and your application history stay for as long as your account does, because they are what the product shows you. Close your account and both are deleted. We keep only what we must for tax and accounting - a record that a payment happened, not your profile.
Why we are allowed to hold it
Almost everything here we hold to perform our contract with you: you asked us to apply for jobs on your behalf, and a profile, an application history and a mailbox connection are what that takes. Keeping the service secure and working (rate limits, the record of which devices signed in) rests on our legitimate interest in running it safely, weighed against your privacy and documented.
The voluntary equal-opportunity answers are different, and they are the ones the law treats most carefully. Ethnicity, disability and the rest are special-category data, we hold them only on your explicit consent, every one of them may be left blank or answered “decline to state”, and withdrawing that consent is clearing the fields - nothing else in the product depends on them.
Billing records we keep because the law requires it, which is why a closed account leaves a payment record behind and nothing else.
Sending it across a border
We are a United States company and the service runs in the United States. If you are in the UK, the EU or the EEA, your data is transferred there (to us and to the providers named above) under the European Commission’s Standard Contractual Clauses, with the UK Addendum where the UK GDPR applies. That is the mechanism. The practical effect is that the same commitments follow the data across the Atlantic. Ask us for the detail and we will send it.
Your rights
Wherever you live, you can ask us for a copy of your data, ask us to correct it, or ask us to delete it. If you are in the UK, EU or EEA, those are your rights under the GDPR. In California, under the CCPA. Exercising them costs nothing and we will not treat you differently for it.
- Access and portability. A copy of everything we hold, and your profile in a machine-readable file you can take to another service.
- Correction. Your profile is editable in the app. Anything else, ask and we will fix it.
- Erasure. The delete button on your account page, which takes effect immediately and needs no request to us.
- Objection and restriction. You can object to processing we do on legitimate-interest grounds, or ask us to pause it while a dispute is open.
- Withdrawing consent. Clear the voluntary demographic answers and they are gone. Nothing else stops working.
- Complaining to a regulator. If we get it wrong you can complain to your own supervisory authority (the ICO in the UK, your national DPA in the EU) without going through us first. We would rather you told us, but it is your right and not our permission to give.
You do not have to ask us to delete your account - the button is on your account page and it takes effect immediately. For anything else, write to support@mayadoit.ai and we will answer within 30 days.
Children
MayaDoIt is not for anyone under 16, and we do not knowingly collect information from anyone under 16. If you believe a child has given us data, write to us and we will remove it.
Changes
If we change this policy in a way that matters, we will email you before it takes effect rather than quietly changing the date at the top.