Privacy Policy

Effective July 28, 2026

Bestie (bestie.one) is operated by LucidMaze Unipessoal, Lda (Tax ID / NIF: PT518956318).

What Bestie is

Bestie is an autonomous-agent platform: you give it a goal in plain language, and it plans, uses tools (a browser, HTTP requests, web search, code execution, and, if you connect it, your Gmail account), and reports back what it did. This page explains, in detail, what information we collect — including any Google user data — how we use it, who we share it with, how we protect it, and how long we keep it.

Information we collect

• Account information: your email address, and either a hashed password or your Google account identifier, depending on how you sign in. Signing in with Google only verifies your identity (your name, email address, and profile picture, via Google's standard sign-in) — it does not by itself give us any access to your Gmail or other Google data.
• Run data: the goals you give the agent, the plan it builds, the tool calls it makes, and the results/reports it produces. This is stored so you can review a run's history and so the agent itself has context while a run is in progress.
• Network activity logs: for each run, a log of which destinations the agent's tools contacted (method, host, path, whether it was allowed by policy). This exists for your own auditability and to enforce the safety limits you configure.
• Credentials you explicitly submit: if a run needs a login or registration details only you can provide, the agent asks via a one-time secure form (never in chat). Submitted values are encrypted at rest and only decrypted for that specific run, for a limited time.
• Gmail data, only if you connect your Google account: connecting Gmail is a separate, explicit step in Settings from signing in — it requests its own permission from Google and issues a distinct, revocable access grant. Once connected, and only while a run you started is actively using the Gmail tool, we can access:
  • message metadata — sender, recipient(s), subject line, timestamp, and labels;
  • message body content, when the agent reads or searches a specific email;
  • the content of any email the agent composes and sends at your explicit request;
  • label/organizational changes the agent makes at your request (archive, mark read/unread, star, move to trash — trash is Gmail's reversible trash, never permanent deletion).
  We request exactly three Gmail scopes for this — read (gmail.readonly), send (gmail.send), and organize (gmail.modify) — and nothing broader. We never request a scope that allows permanently deleting mail, changing your account settings/filters, or accessing Gmail outside of a run you've started.

How we use Google user data

We use Gmail data solely to carry out the specific request you gave the agent for that run:

• the read scope lets the agent search and read messages so it can gather the information it needs to answer your goal;
• the send scope lets the agent send an email only when you've asked it to;
• the modify scope lets the agent organize your inbox (archive, label, star, trash) only when you've asked it to.

When the agent needs the language model to decide what to do next, any Gmail content it has read, or is about to send, is included in that request to our language-model infrastructure — this is what lets the model read the email you asked about, or draft the reply you asked for. That transmission happens only for the duration of generating that one response; the content isn't stored by that infrastructure beyond what's needed to serve the request.

When the agent sends an email or changes something in your inbox, we keep a short record of that specific action (what was done, and to which message) in your account's own audit log, so you have an accurate record of what was done on your behalf. This is part of your run history, described under Retention below — it is not shared with anyone else.

We do not use Google user data for advertising, and we do not sell it, rent it, or use it to build user profiles for any purpose unrelated to the run you asked for.

AI/ML model training

We do not use Google user data — including any data obtained through the Gmail API — to develop, improve, or train generalized or non-personalized artificial intelligence or machine learning models, whether our own or a provider's. Content from your Gmail account is transmitted to our language-model infrastructure solely to generate a real-time response to the specific request you made; it is not retained by that infrastructure for training and is not used to improve any model for any other user.

Sharing and disclosure of Google user data

We do not transfer or disclose Google user data to third parties, except:

• to our own language-model infrastructure, strictly to generate the agent's response to your request (see above) — this infrastructure is operated by the same company that operates Bestie, not an unrelated third party;
• if required to comply with a valid legal process (such as a court order or subpoena), or to protect the rights, property, or safety of Bestie, our users, or the public;
• in connection with a merger, acquisition, or sale of assets — in which case we'd require the successor to honor the commitments in this policy.

We do not sell Google user data, provide it to data brokers or information resellers, use it to determine creditworthiness or for lending purposes, or use it for any form of advertising (targeted, personalized, retargeted, or interest-based).

Data security

• Gmail OAuth tokens and explicitly submitted credentials are encrypted at rest (Fernet/AES), never stored in plain text.
• Each run executes inside its own isolated, hardened container with restricted network egress and no direct access to the platform's database or other tenants' data — the raw Gmail access token is never exposed to that container; only the control plane holds it.
• All traffic to and from the platform, and to Google's APIs, is encrypted in transit (HTTPS).
• Access to production data is limited to what's needed to operate the service.

Retention and deletion

• Disconnecting Gmail (Settings → Connectors) immediately revokes the grant with Google and permanently deletes the stored OAuth token from our database — the agent loses all access to your Gmail account from that point on.
• Disconnecting does not retroactively remove Gmail content from your existing run history. If the agent already read, searched, or sent email during a run before you disconnected, a record of that (including any email content the agent viewed or sent) remains part of that run's timeline and report, the same way any other run data is kept, until you delete it.
• You can delete this at any time: deleting a run or a whole conversation thread permanently deletes its timeline, network log, and report file, including any Gmail content it contains.
• Explicitly submitted credentials are time-limited and automatically expire; they are never retained indefinitely.
• You can request deletion of your entire account and all associated data — including any remaining Gmail-derived content — at any time by contacting support@bestie.one. We process account-deletion requests promptly.

Your choices

• You can disconnect your Gmail account at any time from Settings → Connectors.
• You can review the full timeline, network log, and report for any run you've started.
• You can delete individual runs or entire conversation threads at any time.
• You can request a copy of, or the deletion of, your account and associated data at any time via support@bestie.one.

International users

LucidMaze Unipessoal, Lda is based in Portugal, and we process personal data in line with the EU General Data Protection Regulation (GDPR). Our legal basis for processing your data is performance of our contract with you (running the agent as you've instructed) and our legitimate interest in operating and securing the platform. If you're in the EU/EEA, you have the right to access, correct, export, or erase your data, and to object to or restrict our processing of it — contact us at the address below to exercise any of these, or lodge a complaint with your local data protection authority (in Portugal, the CNPD).

Children's privacy

Bestie is not directed at, and should not be used by, anyone under 18.

Changes to this policy

If this policy changes, we'll update the effective date above. Material changes affecting how we handle Gmail data will be communicated to connected accounts directly, not just posted silently.

Contact

Questions about this policy or your data — including any Google user data — can be sent to support@bestie.one. Bestie is operated by LucidMaze Unipessoal, Lda (Tax ID / NIF: PT518956318).