Last updated: September 8, 2026
It explains what data stackin processes, why, who it is shared with, and how you exercise your rights. It is a plain summary of how the system works today — it is not legal advice.
The controller is Fernando Celmer, CNPJ 68.849.750/0001-76, in Florianópolis, Brazil. Data protection officer: dpo@stackin.io. Write to that address for any request about your data — it is the data subject channel, answered within 15 days.
We collect what is needed for you to use the platform and to meet the fiscal rules for issuing invoices.
the .pfx file and its password, needed to sign the invoice — stored encrypted, never in plain text.Legal obligation, for the fields fiscal law requires. Performance of a contract, to keep your account, issue your invoices and bill for the service. Legitimate interest, for security, fraud prevention and diagnosing failures. We do not sell your data and do not share it for third-party marketing.
Only with those the service needs to work, and each one processes the data on our instructions.
us-east-1), United States.All of stackin's infrastructure runs in the United States: the application and the digital certificate in Amazon Web Services' us-east-1 region, and the database on a Hostinger server in the Boston data center. Stripe, Sentry and Google also process data outside Brazil. Those transfers rely on the contractual clauses and safeguards those providers offer, under article 33 of the LGPD. Brazilian law does not require this data to stay in the country — what it requires is that fiscal records be kept for the minimum period, which holds wherever the server is.
You can connect a third-party application — such as the ChatGPT plugin — to your account through OAuth. You always authorize the connection, it has a limited scope (read, issue, cancel), and the application then acts on behalf of your company within that scope. We never share your password or your certificate with it. You can revoke access at any time in the platform, and revocation takes effect immediately.
Your browser stores your session token and your theme preference locally — without them you would have to sign in on every page. Those are necessary and do not depend on consent. Beyond those, we use Google Ads and Google Analytics to measure how many visits from our ads become signups and how the pages are used. Those cookies are only written if you accept: the Google tag loads with consent denied by default, and the notice on your first visit gives Accept and Reject the same weight. Refusing limits nothing on the platform, and you can change your mind by clearing the site's data — the notice comes back.
Account data for as long as the account exists. Invoices and your company's records for at least five years after issuance, the retention period Brazilian fiscal law requires — including after you close the account. Access logs for six months, under the Brazilian Internet Act. The digital certificate is deleted as soon as you remove it.
The certificate sits in private storage, never publicly reachable, and its password is encrypted before being saved. Your login password is never stored in plain text, only a one-way hash. Traffic is always over HTTPS. Documents, names and tax ids are masked in error logs before they leave the application.
The LGPD gives you confirmation and access, correction, anonymization or deletion, portability, information about sharing, and the right to withdraw consent. You can edit your name and email on the My account page, and close the account there — that anonymizes your login data. For anything else, write to dpo@stackin.io. Invoices and companies remain, unlinked from your personal data, because the law requires those records to be kept.
If an incident poses a relevant risk to your data, we notify you and the Brazilian data protection authority, with what is known about what happened and what we did about it.
We may update this document as the product evolves. The date at the top marks the last revision, and relevant changes are announced in the platform.
| Data | Why we collect it |
|---|---|
| Name and email | Sign-in and account identity |
| Company tax id, registrations and address | Required to issue an invoice |
| Digital certificate and password | Electronic signature of the invoice |
| Recipient's name and tax id | Required by fiscal law |
| Access and error logs | Security, diagnostics and abuse prevention |
| Billing data | Processed by Stripe; we never store the card |