Privacy Policy
In effect since November 16, 2026. Questions go to [email protected].





On this page
- 1. Who is responsible for your data
- 2. What stays on your computer
- 3. What we collect, why, and on what legal basis
- 4. What we do not collect
- 5. Legal bases under each law
- 6. Cookies and browser storage
- 7. Service providers and other recipients
- 8. International transfers
- 9. How long we keep data
- 10. Security
- 11. Children
- 12. Your rights
- 13. How to make a request, and how long an answer takes
- 14. Complaints to an authority
- 15. Changes to this policy
- 16. Contact
All My Hats is built so that your work stays on your computer. Your conversations with your AI tools go from your computer to your own AI provider, under your own account, and never pass through our server. Our server keeps what it needs to sign you in, count your devices, confirm your plan and save the hats you create: your email address, an ID and a name for each computer, your plan, and the names of your hats. To stop abuse it also uses the network address a request comes from. Payments run through Stripe, which is the only one that sees your card. The site has no analytics and no advertising, and sets one cookie, only when you sign in. We do not sell personal data. The rest of this page gives the detail, including how long each thing is kept and how to use your rights.
1. Who is responsible for your data
Laporte Technology, Belo Horizonte, MG, Brazil ("we", "us") decides how the personal data described here is used. In the words of the privacy laws, we are the controller.
Privacy questions and requests go to [email protected]. That address is our channel for everything Brazilian law assigns to the person in charge of data protection (the encarregado). We have not appointed a separate data protection officer.
This policy covers the All My Hats desktop app, the site at allmyhats.com, your account and the server behind them.
2. What stays on your computer
The app keeps these things on your computer and does not send them to us:
- Your conversations with your AI tools: what you type, the files and context you give a tool, and what the tool answers. The app hands them to the AI tool installed on your computer, and that tool sends them to its provider under your own account. That provider's privacy policy covers what happens to them there. The app stores its copy of your conversations in its own data folder on your computer. Your AI tool may keep its own history under its own settings.
- Your AI sign-ins and keys. The app has no sign-in screen for any AI provider and does not read, copy or send us your AI passwords, tokens or keys.
- Your All My Hats sign-in. The access token for this computer and the email you signed in with are kept in your operating system's credential store (Windows Credential Manager on Windows). Signing out deletes them.
- An ID for this installation: a random identifier the app creates once and keeps in its data folder. The app sends it to us when you sign in (section 3).
- Your settings: your theme, Brim's hat and the command the app uses to start your AI tool.
3. What we collect, why, and on what legal basis
Section 5 explains what each legal basis means under each law.
Your account
- Your email address, stored in lowercase.
- An account ID we assign.
- When the account was created and when its trial started.
- If the account started without a trial, the reason: this installation or this mailbox had already used one.
- A plan we granted by hand, if we ever did.
We use these to sign you in, to send you the emails listed below, and to know what your account may use. Legal basis: our contract with you.
Signing in
When someone asks for a sign-in code for an address, we store that address with a one-way hash of the code, a one-way hash of the challenge that goes with it, and a count of wrong attempts. We store this for any well-formed address, whether or not it has an account, because the server answers the same way in both cases so that nobody can learn which addresses have accounts. The code itself exists only in the email.
Legal basis: our contract with you, and the steps you ask for before one exists. For an address with no account, our legitimate interest in running a sign-in that does not reveal who is a customer.
Your devices
When you sign in to the app, it sends us:
- the ID of that installation;
- the name of the computer, as its operating system reports it (its host name);
- its system: Windows, macOS or Linux.
We also record when each device was registered, when it last confirmed its plan with us (about every 20 minutes while the app runs), and when it was signed out or replaced. For each signed-in device we keep a one-way hash of its access token.
We use these to count your two devices, to show you the list when you need to replace one, and to issue the signed pass that lets the app run. The pass names your account ID, the installation ID and your plan. We do not store passes. The app keeps the current one on your computer. Legal basis: our contract with you.
The trial record
When a trial starts, we record the installation ID and the mailbox it was claimed for. The mailbox is your address with a plus-suffix removed and, at Gmail, without dots, so that different spellings of one mailbox count once. If an account with a trial later signs in on another installation, that installation is recorded too.
We use this record for one purpose: one trial per person. It is kept apart from your account, and it stays for its full period even if the account is deleted (section 9). Legal basis: our legitimate interest in preventing repeated free trials.
Limits that protect the service
To stop code guessing, mass sign-ups and overload, the server counts requests. The counters are keyed on:
- the network address a request comes from: the IPv4 address, or the /64 network for IPv6;
- a one-way fingerprint of the email address typed, alone and together with the network address;
- the device or the browser session, for signed-in requests;
- the account, for how many times it replaced a device in 24 hours.
We also refuse addresses at a short list of throwaway mail services, by looking only at the domain typed.
Legal basis: our legitimate interest in keeping accounts and the service safe.
Your workspace and hats
Every account gets a workspace named "Personal". When the app saves your hats to our server, we store for each hat its name, color, kind (company, project, front or personal), its place in the list, the hat it sits under, and whether and when it was archived.
A hat's name is whatever you type. If you name a hat after a person or a company, we store that name. Legal basis: our contract with you.
The account area on the site
When you sign in on the site, the server creates a session: a random token kept in a cookie in your browser (section 6), of which we store only a one-way hash, with your account and the date it expires. Legal basis: our contract with you.
Your plan and payments
If you buy a plan, we send Stripe your email address, your account ID, and the plan and billing period you chose. You then enter your payment details on Stripe's own pages. We never receive or store your full card number.
Our server keeps:
- the plan, the billing period and its state: active, cancelled, payment failed or ended;
- when the paid period ends and, if a payment failed, since when;
- Stripe's identifiers for your subscription and for you as its customer;
- the identifiers of the payment events Stripe sent us, so that none is applied twice.
When a payment goes through, we read the amount, the currency, the date and the invoice number from Stripe to email you a receipt. Invoices and payment records are held in our Stripe account.
Legal basis: our contract with you. For keeping purchase records, our legal obligations under tax and accounting law.
Emails we send you
We email you a sign-in code when one is asked for, a receipt after each payment, a notice when you cancel, a reminder before a yearly plan renews, and notices of changes to prices, to the terms or to this policy. We send no marketing email. Legal basis: our contract with you.
Server logs
Our server writes a line for each request it receives: the time, the network address it came from, the address requested, the result, and the technical headers the browser or app sent, such as its type and version. The session cookie and the access token are left out of these lines. Error logs can also contain technical details of a failed request, such as Stripe's identifier for a subscription.
We use logs to find faults and to investigate abuse, and Brazilian law requires an online service like ours to keep access records for six months. Legal basis: our legitimate interest in running a secure service, and our legal obligation under Brazil's Internet Civil Framework (Law 12.965/2014, article 15).
Visits to the site
The site is a set of static pages hosted by Cloudflare. To deliver a page and block attacks, Cloudflare handles the network address of your request, your browser type and the page you asked for. Cloudflare shows us totals only, such as how many requests the site received and from which countries.
The site loads its fonts and scripts from our own address. It runs no analytics script, no advertising script and no social media widget. What you type into the guide's search stays in your browser: the page downloads the search index and searches it there. The guide's copy buttons put text on your clipboard and send nothing anywhere.
Legal basis: our legitimate interest in delivering and protecting the site.
Messages you send us
If you write to hello@, privacy@ or [email protected], we receive your address and whatever you write, and we keep the conversation to answer you and to have a record of what was agreed. Legal basis: our legitimate interest in answering you, or our contract with you when the message is about your account.
4. What we do not collect
- Your conversations with AI tools, your prompts, the answers, and the files those tools read or change. The app has no feature that sends them to us.
- Your AI provider passwords, tokens or API keys.
- Your queue, your notes and your files.
- Your card number. It goes to Stripe only.
- A password. There is none. Sign-in uses a code sent by email.
- Usage analytics or crash reports from the app. The app contains no analytics, no telemetry and no crash reporting.
- Tracking on the site. It has no analytics, advertising cookies, pixels or fingerprinting.
- Your name, phone number, postal address or date of birth. We do not ask for them. Stripe may ask for some of them when you pay.
- Special categories of data, such as health data or biometric data.
We do not sell personal data, and we do not share it with anyone for advertising.
We do not profile you. Some automatic rules do make decisions: a second trial is refused, throwaway addresses are refused, and requests beyond a limit are refused for a while. If you think one of them got your case wrong, write to us and a person will look at it.
5. Legal bases under each law
| What we say in section 3 | GDPR and UK GDPR | Brazil's LGPD |
|---|---|---|
| Our contract with you, and steps before one | Article 6(1)(b) | Article 7, V |
| Our legitimate interest | Article 6(1)(f) | Article 7, IX |
| Our legal obligations | Article 6(1)(c) | Article 7, II |
We do not rely on consent for anything today, because we do nothing that needs it. If that changes, we will ask first, and you will be able to withdraw consent at any time.
Where we rely on a legitimate interest, you can object (section 12). We weighed each of those interests against yours. The data involved is limited to what the purpose needs: an email address, an installation ID and a network address.
If you do not give us an email address, we cannot create an account. If the app does not send the installation ID, the computer's name and its system, it cannot be signed in.
6. Cookies and browser storage
The site and the server set exactly these:
| Name | Kind | Set when | Purpose | Lasts |
|---|---|---|---|---|
__Host-amh_session |
Cookie, set by our server | You sign in to the account area on the site | Keeps you signed in. Scripts cannot read it, it travels only over HTTPS, and it is never sent along with requests that start on other sites. | 30 days, or until you sign out |
allmyhats.mode |
Browser local storage, never sent to us | You pick a theme on the site | Remembers the theme you picked | Until you clear your browser's site data |
Both are needed for something you asked for, so we show no cookie banner. If we ever add anything that is not strictly needed, we will ask for your consent first and list it here.
When you pay or update your payment method, you are on Stripe's pages. Stripe sets its own cookies there, under its own cookie policy.
7. Service providers and other recipients
These companies handle personal data for us. This list names every provider in use on the effective date above.
| Provider | What it does for us | What it handles |
|---|---|---|
| Cloudflare, Inc. | Hosts the site, runs the DNS for allmyhats.com, and routes the mail sent to our @allmyhats.com addresses to our mailbox |
Network addresses and request details of site visitors; the messages you send us while they are being routed |
| Stripe | Takes payments and keeps invoices | Your email address, your account ID, your plan, your payment details and what it collects itself on its payment pages. Stripe is the only one that sees card details. |
We keep this list current. Before any other company starts handling personal data for us, such as the company that hosts our server and database or the one that delivers the emails we send, we add it here.
We also disclose personal data:
- when the law requires it, for example under a court order. We disclose only what the order requires, and we tell you unless the law forbids it;
- if the service changes hands. If another company takes over All My Hats, your data moves with the service under this policy, and we tell you beforehand.
Your AI provider is not on this list. It receives your conversations from your computer, under your own account and your own agreement with it. We are not part of that exchange.
8. International transfers
We are based in Brazil. Our providers operate in the United States and other countries. Your data is therefore handled in Brazil and in the countries where those providers run their systems, which may be outside the country where you live and may protect personal data differently.
Where the law sets conditions for sending personal data abroad, we follow them:
- From the European Union and the EEA to us in Brazil: the European Commission decided in January 2026 that Brazil protects personal data adequately, so this data can come to Brazil without further safeguards.
- From Brazil to providers in other countries: the transfer mechanisms of articles 33 to 36 of the LGPD.
- In every other case covered by the GDPR or the UK GDPR: standard contractual clauses or another mechanism those laws recognize, as set out in our providers' data processing terms.
You can ask us for a copy of the safeguards that apply to your data.
9. How long we keep data
| Data | Kept for |
|---|---|
| Sign-in code record (the address typed, hashed code, hashed challenge) | The code expires after 10 minutes. The record is deleted within 2 hours of the request. |
| Counters behind the limits (network address, fingerprint of the address typed) | Up to 24 hours |
| Count of device replacements | About a day |
| A signed-in device | Until it is signed out or replaced |
| A device that was signed out or replaced | 30 days, then deleted |
| Session on the site | 30 days, or until you sign out |
| Your account, workspace and hats | While the account exists. Deleted within 30 days of a deletion request. An account with no paid plan that has not been signed in to for 24 months is deleted, and we email you 30 days before. |
| Your plan's state and Stripe identifiers | While the account exists |
| Trial record (installation ID and mailbox) | 24 months from the day each record was made, even if the account is deleted earlier |
| Purchase records (invoices and payments, held in our Stripe account) | 5 years from the payment, as tax and accounting rules require |
| Server logs | 6 months |
| Database backups | Up to 30 days. Deleted data can remain in a backup until the backup is overwritten. |
| Messages you send us | 24 months after the last message in the conversation |
When a period ends, we delete the data or make it impossible to link to you. We keep something longer only when a law requires it or while a dispute about it is open.
10. Security
What protects your data today:
- The app talks to our server only over encrypted connections (HTTPS).
- Sign-in codes, challenges, access tokens and session tokens are stored only as one-way hashes. A copy of our database would not contain a usable code or token.
- A sign-in code has 8 digits, lasts 10 minutes, works once, and locks after five wrong attempts. Request limits bound how many guesses anyone can make.
- The pass that unlocks the app is signed by our server, lasts one hour and is tied to one installation.
- Card details never reach our server.
- The session cookie on the site cannot be read by scripts and is refused from other sites' pages.
What you should know:
- No system is perfectly secure, and we hold no security certification and have had no outside audit.
- Whoever can read your mailbox can sign in to your account. Protect the mailbox.
- The app's sign-in on a computer stays valid until you sign out there or replace that device. Sign out of computers you stop using. You can also remove a device from your account page on the site.
- Hat names are stored as you typed them. Do not put secrets in them.
If a security incident puts your data at risk, we tell you and the authorities as the law requires.
11. Children
All My Hats is for adults. You must be 18 or older to have an account. We do not knowingly collect data from children. If you believe a child has given us data, write to [email protected] and we will delete it.
12. Your rights
You can use the rights below wherever you live. Using them costs nothing, and we will never treat you worse for it.
Everyone
You can ask us:
- whether we hold data about you, and for a copy of it;
- to correct data that is wrong. To change the email address of an account, write to us;
- to delete your account and the data that goes with it;
- for your data in a format a computer can read, to take elsewhere;
- to stop or limit a use of your data that rests on our legitimate interest.
A deletion request removes your account, your devices, your sessions, your workspace and your hats. It also cancels a running plan, without a refund beyond what the Terms of Service provide. Two things stay for their periods in section 9: the trial record, and the purchase records the law requires us to keep.
European Union, European Economic Area and United Kingdom
Under the GDPR and the UK GDPR you have the rights of access, rectification, erasure, restriction, data portability and objection, the right not to be subject to decisions based solely on automated processing that significantly affect you, and the right to complain to a supervisory authority (section 14).
Brazil
Under the LGPD (article 18) you have the right to confirmation that we process your data, access, correction, anonymization, blocking or deletion of data that is unnecessary or excessive, portability, deletion of data processed with consent, information about who we share data with, information about the possibility of refusing consent and its consequences, withdrawal of consent, and review of decisions made solely by automated means (article 20). You can also petition the national authority (section 14).
United States, including California
State privacy laws give residents of California and several other states the rights to know what personal information a business collects, to get a copy, to correct it, to delete it, and to opt out of its sale, of its sharing for cross-context behavioral advertising, and of targeted advertising. Some of these laws apply only to businesses above a certain size. We honor these requests from everyone regardless.
- We do not sell personal information, we do not share it for cross-context behavioral advertising, and we have not done either in the past 12 months. There is nothing to opt out of, so a Global Privacy Control signal changes nothing on our site.
- We do not use or disclose sensitive personal information for purposes that would give you a right to limit it.
- The categories we collect, in California's terms: identifiers (email address, account ID, installation ID, network address), commercial information (your plan and its state), and internet or network activity (server logs and the time a device last checked in). Sections 3, 7 and 9 say why we collect each, who receives it and how long we keep it.
- You can make a request through an authorized agent. We will ask the agent for proof of your permission.
- If we refuse a request, you can appeal by replying to our answer. We answer an appeal within 45 days. If the appeal is refused, you can contact your state's attorney general.
13. How to make a request, and how long an answer takes
Write to [email protected] from the email address of your account and say what you want. To be sure the request comes from you, we answer to the account's address and may ask you to confirm from it. We do not ask for identity documents.
- We answer within 30 days.
- A request under Brazilian law for a full copy of your data is answered within 15 days.
- If a request is complex and the law allows more time, we tell you within the first 30 days how long it will take and why.
If we cannot do what you ask, we tell you the reason and what you can do next.
14. Complaints to an authority
Please write to us first so we can try to fix the problem. You can also complain to a data protection authority at any time:
- Brazil: the Autoridade Nacional de Proteção de Dados (ANPD).
- European Union and EEA: the data protection authority of the country where you live or work, or where the problem happened.
- United Kingdom: the Information Commissioner's Office (ICO).
- United States: your state's attorney general. In California, also the California Privacy Protection Agency.
15. Changes to this policy
When what the product collects changes, this policy changes with it. The current version is always on the site, with its effective date at the top. If a change affects how we use data we already hold about you, we email you at least 30 days before it takes effect.
16. Contact
- Privacy requests and questions:
[email protected] - General questions:
[email protected] - Legal notices:
[email protected] - By post: Laporte Technology, Belo Horizonte, MG, Brazil