Privacy at Veesker.
Plain language, no dark patterns. This page explains exactly what data we collect, why we collect it, and how to remove it. Last updated: 2026-05-02.
Who is the data controller
Geraldo Ferreira Viana Júnior (sole founder of Veesker), based in São Paulo, Brazil.
Contact for any privacy request: geraldovianajr@veesker.cloud with subject prefix [PRIVACY].
What data we collect
1. Veesker Cloud waitlist
If you submit your email through the Cloud waitlist on the homepage, we store:
- Email address (the one you typed).
- Source label (defaults to
veesker.cloud). - Hashed truncated IP (SHA-256 of
ip + salt, 16 hex chars) — for abuse triage only, not the raw IP. - User-Agent string truncated to 200 chars.
- Submission timestamp.
Lawful basis: legitimate interest (you opted in by submitting the form to be notified about Veesker Cloud).
Where it lives: a Postgres database hosted on Railway, accessed via the api.veesker.cloud service. Only the founder has access.
Retention: kept until Veesker Cloud reaches General Availability (target H2 2026) plus one notification email about the launch. After that — or any time you request removal — your row is deleted within 7 days.
Sharing: never sold, never shared with marketing partners, never used for anything other than notifying you about Cloud availability and founder pricing.
2. Veesker Community Edition (the desktop app)
The Community IDE is local-first by design. The desktop app does not phone home about your usage, does not collect telemetry, and does not transmit your database credentials, queries, or query results anywhere outside your machine.
The only outbound calls the desktop app makes are:
- Auto-update check — fetches the release manifest from GitHub Releases. No user identifier is sent.
- BYOK AI calls — when you bring your own OpenAI / Anthropic / local-model key and explicitly run an AI action, the prompt and your key go directly to that provider. We are not in the loop.
3. Veesker Cloud (when you opt in, post-launch)
Veesker Cloud is in development (Coming Soon — H2 2026). When it launches, opting in will involve managed AI workflows that may process query metadata to ground responses in your schema. The Cloud tier will ship with its own privacy addendum before GA. This page will be updated and dated when that happens.
Cloud features are strictly opt-in. Community Edition will continue to work fully offline with no Cloud component.
4. Website (veesker.cloud)
- No cookies for tracking. No Google Analytics, no Segment, no Mixpanel, no Hotjar.
- Hosting on Cloudflare Workers — Cloudflare may log request metadata (IP, URL, user-agent) for abuse mitigation per their own privacy policy. Veesker does not store, query, or process those logs.
- No third-party scripts. Only fonts.googleapis.com (Google Fonts) and shields.io badges (GitHub stars), which run client-side without identifiers we attach.
5. Blog
The blog at /blog serves static markdown. Reading a post does not send any identifier to Veesker. The RSS feed is unauthenticated and uncounted.
Your rights
Whether you are in Brazil (LGPD), the EU (GDPR), or anywhere else, you have the right to:
- Access — ask us what data we have about you.
- Correct — fix anything wrong.
- Delete — ask for full removal. Granted within 7 days of receiving the request.
- Object — withdraw your waitlist opt-in at any time.
- Portability — request a copy of your data in JSON.
To exercise any of these rights, email geraldovianajr@veesker.cloud with subject [PRIVACY] and a one-line description of what you want.
No account or login required — just the email you used.
Children
Veesker is a tool for professional Oracle developers. We do not knowingly collect data from anyone under 16. If you believe a minor submitted their email to the waitlist, please email us and we will delete the record immediately.
Security
The waitlist API enforces rate limits, never logs raw IPs, validates email format on submit, and uses TLS end-to-end. The repository is open-source and continuously audited via CodeQL and Dependabot. See /security for the full trust model.
Changes to this policy
If this policy changes materially, we will update the "Last updated" date at the top, post a note in /changelog, and email anyone on the waitlist before the change takes effect.