Privacy policy

FullCup.ai's data controller is FF MARKETING DIRETO LTDA, CNPJ 37.307.198/0001-60, headquartered at Rua Amaury Filho, 120, Casa 1, Recreio dos Bandeirantes, Rio de Janeiro/RJ, CEP 22790-320, Brazil. Reach the data subject channel at support@fullcup.ai.

• Email, required to create an account or receive a receipt.
• Name, optional.
• Language and theme preference.
• Contribution amounts.
• IP address, to enforce rate limits and to prevent fraud.
• Public repository metadata, when a creator links a repository to a project: its name, the GitHub username of its owner, commit and tree identifiers, commit messages, and permalinks. Repository contents are read to assess a milestone but are never stored.

FullCup.ai never collects prompt content or response content. A receipt — the record every request produces — carries only consumption metadata: the model, the token count, the cost, and the time. Nothing else is written down.

Under Brazil's LGPD (article 7), FullCup.ai processes email and contribution data to perform the contract a backer or creator enters into, IP address and related signals under legitimate interest to prevent fraud and enforce rate limits, and financial records under a legal obligation, for tax purposes.

When a repository is linked to a project, or a commit is designated as a milestone's delivery, the person who owns the repository or authored the commit is not always the one with a FullCup.ai account — for example, when the repository belongs to an organization or the commit was written by the creator's collaborator. In that case, FullCup.ai processes that person's GitHub username and commit message under legitimate interest (LGPD, art. 7, IX), to let whoever financed the project verify the delivery, and does not seek their consent because it has no direct relationship with them. Anyone who identifies themselves in this data and wants it corrected, explained, or reviewed may write to support@fullcup.ai.

FullCup.ai uses Stripe for payment, OpenRouter for inference, Resend for email, GitHub to read the public repositories creators link, and Cloudflare for infrastructure. Data travels outside Brazil to operate these services, including to the United States.

FullCup.ai's financial records live in an append-only ledger, one that admits no alteration and no removal — that is what lets anyone rebuild and check the history independently.

Because of that, the ledger stores an opaque reference instead of your email. A deletion request removes your profile and undoes the link between you and that reference, and the financial record that remains identifies no one. What deletion does not do is erase the ledger entry itself.

Under Brazil's LGPD (article 18), you can ask FullCup.ai to confirm it processes your data, to access it, correct it, anonymize it, receive it in a portable format, learn who it has been shared with, and withdraw any consent you gave. Write to support@fullcup.ai — FullCup.ai confirms receipt right away, and a full answer follows within 15 days.

FullCup.ai sets only the cookies the product needs: session, theme preference, and language preference. No third-party tracking, no advertising.

A creator's own dashboard counts a visit to their project page as a hash of the visitor's IP address, browser identifier and the project, salted with a value drawn fresh each day and never stored anywhere else — yesterday's hash cannot be recomputed. That hash is kept for 2 days, only to avoid counting the same visit twice, then deleted. No cookie is set for this, and no IP address or browser identifier is ever stored on its own.

Studio Connect is the FullCup.ai extension for Chrome and Edge. It lets a creator generate NotebookLM files for a Cup. It runs in the creator's own browser, with the creator's own Google session, and nowhere else. FullCup.ai's servers never contact Google on a creator's behalf.

What reaches FullCup.ai

• The files generated for your requests: audio, video, slides, infographic or report.
• The current step of each request, so the studio can show where it is.
• The version of the extension.
• A random identifier created when the extension is installed. It is not linked to your Google account, and it tells FullCup.ai which installation is working on a request.
• The identifier of the NotebookLM notebook the extension created for the Cup, so the next request can reuse it.

What never reaches FullCup.ai

• Your Google password.
• Your Google cookies and tokens. The session stays inside your browser and is used only to open NotebookLM as you.
• Your full Google email address. The extension shows it masked, only to you, and does not store it.
• Your other tabs, your browsing history and the sites you visit.

What the extension keeps in your browser

The installation identifier, the requests in progress, the account you picked in masked form, the notebook identifier of each Cup and the last error. All of it lives in the extension's own storage in your browser.

Retention

The progress of a request disappears from FullCup.ai after 2 hours. Generated files follow the media library of the Cup they belong to: they stay there until the creator removes them. Notebooks created in NotebookLM belong to your Google account and follow Google's rules.

How to remove it

Open the extensions page of your browser, find Studio Connect and choose Remove. It stops at once and the data it stored in your browser is deleted with it. Files already in your media library stay there. To remove them, or to ask about the data above, write to support@fullcup.ai.