GazetaSecurity and trust
Secure because
it's simple.
No account, no password and no server storing what you read. See how that works.
Updated October 7, 2026
How we protect you
- No account or password: there's no login to leak.
- On the device: what you read, save and set up stays on your phone, not on a server of ours.
- Secure connections: the site and the app use HTTPS everywhere.
- Restricted access: site statistics are in a password-protected dashboard, and only the developer has access.
Who processes data
Services Gazeta uses and what goes through each one. None of them receives what you read in the app.
| Service | Purpose | What goes through it | Where |
|---|---|---|---|
| Apple | iCloud, App Store, maps and Apple Intelligence | iPhone: backup in the person's own iCloud; summaries run on the device | Global |
| Android backup and translation | Android: backup in the person's own Google account; language pack | Global | |
| TelemetryDeck | App statistics | iPhone: anonymous usage counts, without identifying the person | European Union |
| Vercel | Website hosting | Serves the pages of appgazeta.com | USA |
| Upstash | Website statistics | Site counts, with a random code per browser and no IP | Brazil (São Paulo) |
| Resend | Contact form | Emails what the person writes in the form | Brazil (São Paulo) |
| Cloudflare | Domain and email | Site addresses and forwarding for contato@appgazeta.com | Global |
Data processing (LGPD)
The party responsible for the data (data controller) is Gazeta's developer, Natã Monteiro Reis. Anonymous statistics rely on the legitimate interest of understanding what works, without identifying anyone. To request access, correction or deletion, write to contato@appgazeta.com. Everything about data is in the Privacy Policy.
Found a vulnerability?
If you found a security vulnerability in the app or the site, write to contato@appgazeta.com with the subject "Security". We appreciate the report, reply personally and fix it as soon as possible. Please don't disclose the issue before it's fixed.
The same details are in security.txt.