Privacy Policy

Last updated: July 20, 2026

This policy covers the sqlanvil.com website and SQLAnvil Cloud (app.sqlanvil.com), operated by Ivan Histand (“SQLAnvil”, “we”). The short version: we collect what's needed to run your workflows and nothing more, we never see your database password, we never copy your table data, and we never sell anything about you.

1. What we collect

• Account information. When you sign in with GitHub we receive your username, display name, email address, and avatar from the OAuth profile.
• Project configuration. The repositories you connect, project settings, workflow schedules, and connection metadata.
• Run records. For each run: per-action metadata (target, type, status, timing), the compiled SQL, and — on failure — the warehouse error text, plus a tail of the run log. The sensitive fields (compiled SQL and error text) are scrubbed 30 days after a run finishes; the lightweight metadata is kept as run history. Details: Data handling.
• Warehouse authorization. Where a provider supports OAuth (e.g. Supabase), we store an encrypted, revocable refresh token — never your database password. Per-run access tokens are short-lived and destroyed with the run.
• Server logs. Our hosting providers keep standard request logs (IP address, user agent, timestamps) for security and operations.

2. What we never collect

• Database passwords or service-role keys — the platform is designed so we can't hold them.
• Your table data. We store the SQL text and error text of runs, not query results or rows from your warehouse. (Note that SQL and error text can contain data you inline — see the hygiene guidance in Data handling.)
• Advertising or cross-site tracking data. The website sets no advertising cookies and runs no third-party trackers; the app uses cookies only to keep you signed in.

3. How we use information

Solely to provide and secure the service: authenticate you, run your workflows, show run history, debug failures you ask the platform to surface, and send service notices. There is no support team browsing your data — the service is fully self-service — and we do not sell or rent personal information, full stop.

4. Where data lives

Control-plane data is stored in Supabase (Postgres), encrypted at rest and protected by row-level security so a project's runs are readable only by its owner. Runs execute on Google Cloud (us-east1). The website and dashboard are hosted on Vercel. The GitHub integration operates through a GitHub App you install and can uninstall at any time. These providers act as our infrastructure sub-processors.

5. Retention and deletion

• Compiled SQL and error text: scrubbed 30 days after the run finishes.
• Run metadata and project configuration: kept while the project exists; deleting a project removes its runs.
• Account data: kept while your account is active. To delete your account and its data entirely, email sqlanvil@badgeretl.com from your account email — we'll confirm and complete deletion within 30 days.
• Warehouse authorization tokens: deleted when you disconnect, revoke, or delete the project.

6. Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal information. Whatever applies, the practical answer is the same: email sqlanvil@badgeretl.com and we'll honor the request.

7. Children

The service is not directed to children and may not be used by anyone under 16.

8. Changes

If this policy changes materially we'll post the update here and change the date above; for significant changes affecting active accounts we'll make reasonable efforts to notify you in the dashboard.

9. Contact

Privacy questions or requests: sqlanvil@badgeretl.com.