This notice has two halves because Pressfox has two roles. For your account, your team and this website, we decide what is processed and are the controller. For the data you send us to render into reports, you decide and we act on your instructions as the processor; that half is governed by the data processing agreement.
Who we are
Pressfox is a product of IT Solid Solutions (CARLOS A. GIRALT TORRIENTE TECNOLOGIA DA INFORMACAO LTDA, CNPJ 47.281.371/0001-52), Avenida Prefeito Osmar Cunha, 416, Florianópolis-SC, 88015-100, Brazil. It is the controller for the data described in Part A. Contact: hello@pressfox.io, subject "Privacy request".
The person responsible for data protection (the encarregado under the LGPD) is Carlos A. Giralt Torriente. Reach him at hello@pressfox.io, subject "Privacy request".
Our representative in the European Union (Art. 27 GDPR) is being appointed; it will be named here.
Part A. Pressfox as controller
Where the data comes from
- You: your email address when you sign up, your name and what you enter in the app.
- Your team: a member who invites you gives us your email address.
- Google: your name, email address and Google account id, if you sign in with Google.
- Paddle: the status of your subscription and payments. We never receive card numbers.
- Your systems: payloads sent through the API. That is Customer Data, covered by Part B.
What we process and why
| Data | Purpose | Legal basis |
|---|---|---|
| Email address, name, sign-in method, workspace membership and role | Create and secure your account, send sign-in codes and invitations | Contract (Art. 6(1)(b)) |
| Sign-ups not yet confirmed: the email address and a hash of the code | Check that the address is yours before an account exists | Steps before a contract |
| Security check on the sign-in and sign-up pages: IP address and signals from your browser, processed by Cloudflare Turnstile | Tell people from automated abuse before we send a sign-in code | Legitimate interest (security) |
| Sessions: device, browser and network, sign-in time | Keep you signed in, list your sessions, alert you to a new device | Contract; legitimate interest (security) |
| Billing identity: company name, billing address, VAT ID, plan, invoices | Charge for the service through Paddle, keep accounting records | Contract; legal obligation (tax law) |
| Audit log: sign-ins, role changes, key creation and revocation, publishes, deletions, with IP address and user agent | Security, accountability to workspace admins | Legitimate interest (security) |
| Server logs: request ids, timestamps, IP address, endpoint, status, timing; never payload content | Operate and secure the service, investigate incidents | Legitimate interest (operations) |
| Error reports in Sentry, with payload content scrubbed | Fix defects | Legitimate interest |
| Text you write to the AI features of the app, such as a request to the designer assistant | Answer that request | Contract |
| Support correspondence | Answer you | Contract |
| Usage and incident emails | Tell you about limits, incidents and material changes | Contract; legitimate interest |
We do not sell personal data, we do not use your content to train AI models, and we make no decisions about you by automated means alone.
How long we keep it
| Data | Kept for |
|---|---|
| Account data | Life of the account, then 30 days |
| Sign-ups never confirmed | Deleted after 24 hours (checked every hour) |
| Sessions | End after 7 days without use, and after 30 days at most |
| Audit log | 1 year, 2 years on Pro and Enterprise. An encrypted copy is locked for the same period and cannot be changed or erased early; we keep it to establish, exercise or defend legal claims (Art. 17(3)(e) GDPR) |
| Server logs | 30 days |
| Error reports (Sentry) | 90 days |
| Text sent to AI features | Not kept by us after the answer; the provider's retention is on the subprocessors page |
| Billing and accounting records | As tax law requires, up to 10 years |
| Support correspondence | 3 years |
| Database backups | Point-in-time recovery for about 4 weeks; a deleted workspace's encryption key leaves the backups within 35 days after its purge. A deleted workspace can be restored for 30 days before its data and encryption key are destroyed |
| Reports (Customer Data, Part B) | Paid plans: while the subscription is active, and 30 days after it ends. Free: 7 days. Enterprise: as agreed in the contract. The Customer can set a shorter time for the workspace or for one report. Each report keeps the end it was created with; moving between paid plans never shortens it. Test reports: 24 hours on every plan |
| Report inputs (the payload and images fetched from your URLs) | Deleted when the report is ready, or 24 hours after a failed render |
This website and cookies
pressfox.io is a static site. It sets no cookies and loads no third-party scripts, fonts or pixels. If we add analytics, they will be cookieless: aggregate page counts with no identifier stored on your device and no cross-site tracking, which is why there is no cookie banner. The app at app.pressfox.io sets two strictly necessary cookies: a session cookie and a CSRF token, both required to keep you signed in and to protect forms; neither needs consent. If you sign in with Google, Google sets cookies on its own domain under its own notice. The sign-in and sign-up pages also load Cloudflare Turnstile, a check that tells people from bots; Cloudflare uses what it reads only for that check, not for advertising. Hosted report pages set no cookies, except a password-gate cookie scoped to the report's hostname when a report is password protected.
AI features
Some features use AI: drafting a template's translations, translating the report text fields a template marks, short summaries in reports, the designer assistant, and building a draft template from a PDF you upload. They send text only, never images: the template's text, the marked fields of that one report, your message to the assistant, or the text of the PDF. The text is processed by Anthropic in the United States. It is not used to train AI models. Template translations are frozen when a version is published, so printing a report does not send template text to a model. AI features are off for health workspaces.
Who receives data
Our subprocessors: Railway (hosting, the database and its backups, EU West), Cloudflare (network, storage in the EU jurisdiction, and the security check on sign-in), Paddle (payments, as an independent controller for payment data), Google (sign-in, if you choose it), Resend (email), Sentry (error monitoring), Anthropic (AI features, when used). Mail you send to us passes through Cloudflare Email Routing to our mailbox. Authorities when the law requires. No one else.
Transfers
Your data is stored in the EU. IT Solid Solutions operates the service from Brazil, and some providers are US companies; text sent to the AI features is processed by Anthropic in the United States. Each transfer rests on the European Commission's Standard Contractual Clauses, or on an adequacy decision where one applies, as listed per provider on the subprocessors page.
Marketing
We send no marketing email without your consent. Today we send none at all. If we start, it will be opt-in, and every email will have a link to stop with one click. Service emails about your account, usage, incidents and changes to these documents are not marketing.
Security
We protect data with encryption in transit and at rest, workspace isolation, limited access and an audit log. The security page describes the measures. If a breach puts your personal data at risk, we tell you and the authorities where the law requires it.
Children
Accounts are for adults acting for an organisation. Pressfox is not directed at children, and we do not knowingly collect children's data for accounts. A customer may include data about minors in its reports, for example a clinic, as the controller of that data; Part B and the DPA cover that.
Your rights
Access, rectification, erasure, restriction, portability and objection, under Articles 15 to 21 GDPR; withdrawal of consent where consent is the basis; a complaint to the supervisory authority where you live or work. Write to hello@pressfox.io, subject "Privacy request"; we answer within one month. Workspace owners can export and delete their workspace from the app without asking us.
Brazil (LGPD)
IT Solid Solutions is established in Brazil, so the Lei Geral de Proteção de Dados (Law 13.709/2018) also applies. The legal bases above correspond to the performance of a contract (Art. 7, V), compliance with a legal obligation (Art. 7, II) and legitimate interest (Art. 7, IX). You have the rights in Art. 18: confirmation and access, correction, anonymisation, blocking or deletion of unnecessary data, portability, information about sharing, and revocation of consent. Requests go to Carlos A. Giralt Torriente, the person responsible for data protection, at hello@pressfox.io. We confirm whether we process your data, in a simplified form, at once; a complete answer follows within 15 days of your request (Art. 19). You may also complain to the Autoridade Nacional de Proteção de Dados (ANPD).
United States
We do not sell personal information, and we do not share it for cross-context behavioural advertising. We show no ads and use no advertising trackers.
Part B. Pressfox as processor
Everything inside a payload, a template, an asset or a rendered report is your data. Patient names in a visit summary, vessel details in a survey, a customer's address on a statement: you are the controller, you choose whether to send it, and we process it only to validate, render, store and deliver the report as your instructions and plan define. The DPA sets out the subject matter, duration, security measures, subprocessor conditions, breach notification within 48 hours, assistance with data subject requests, deletion at the end, and audit information. If you are a person whose data appears in a report and you want it changed or removed, contact the organisation that issued the report; we will help them do it.
If you open or receive a report
Reports on Pressfox are issued by our customers. The organisation that issued the report is the controller of the data in it and of the data below; we process it on their behalf. To use your rights, contact that organisation. If you cannot reach them, write to us and we will pass your request on.
- Reports sent by email: your email address, and when you first opened the link.
- Views: a daily count of views per report, with no identifier for who viewed it.
- Password-protected reports: a cookie that remembers you entered the password, scoped to the report's hostname. Report pages set no other cookies.
- Server logs: requests to report pages that reach our servers are logged with the IP address and kept 30 days, for security and operations.
Changes to this notice
We will post changes here with a new date and version, and email workspace owners about material ones.
Version history
| Version | Changes |
|---|---|
| 13 October 2026 | Retention table: database backups by point-in-time recovery, with the window in which deleted data leaves them, replacing the earlier description of daily backups; the audit log by plan, with its locked encrypted copy. |
| 13 October 2026 | Reports are kept while the subscription is active and 30 days after it ends (Free: 7 days), replacing the per-plan windows; the customer can set a shorter time. |
| 10 October 2026 | Named the registered company and the person responsible for data protection. Added where data comes from, a complete retention table, AI features, marketing, security and breach notification, children, LGPD response times, United States, and a section for people who open or receive a report. |