Privacy Policy

1. Introduction & Scope

OopsBase ("we", "our", or "us") provides a sovereign cloud backend suite comprising dedicated PostgreSQL database provisioning, REST & GraphQL APIs, storage volumes, serverless edge functions, DNS management, and automated cloud backups.

This Privacy Policy explains how we collect, process, store, and safeguard information when you use the OopsBase platform, our website (oopsbase.com), and the OopsBase Console (console.oopsbase.com).

2. Information We Collect

A. Account & Profile Information

When you create an account on OopsBase, we collect your name, email address, password hash (salted using bcrypt/Argon2), and billing metadata. We never store raw plain-text passwords or full payment card numbers.

B. Tenant Project Data

All project artifacts—including PostgreSQL tables, row data, storage files, Edge Function scripts, and GoTrue authentication registries—are held in strictly isolated tenant environments. You retain complete ownership and sovereignty over your application databases.

C. Oopslytics Client Telemetry & Logs

When using Oopslytics for frontend and backend crash reporting, logs and diagnostics are stored exclusively within your own dedicated project database (_oopslytics schema). Telemetry is never shared across tenants or accessed by third-party aggregators.

3. Google API User Data Policy & Drive Backups

OopsBase provides an optional Google Drive integration that enables project owners to schedule automated, encrypted backups of their databases, schemas, and storage volumes.

A. Scopes Requested

• https://www.googleapis.com/auth/drive.file: Used strictly to create and manage the dedicated "OopsBase Backups" folder in your personal or workspace Google Drive and upload project backup archives. OopsBase never reads, modifies, or accesses any other files outside those created by our platform.
• https://www.googleapis.com/auth/userinfo.email: Used to verify and display the connected Google account email inside your project's Backup Settings.
• https://www.googleapis.com/auth/userinfo.profile: Used to display your Google profile name in connection status cards.

B. Limited Use Disclosure

Specifically:

• We do not transfer or disclose Google user data to third parties, unless necessary to provide or improve backup functionality, comply with applicable law, or as part of a merger.
• We do not use Google user data for serving advertisements.
• We do not permit humans to read your data unless you provide explicit consent to investigate a critical technical issue, or as required by law.
• OAuth refresh tokens and access tokens are stored securely in PostgreSQL using AES-256 encryption at rest.

4. Data Retention & Deletion

You have absolute control over your data retention:

• Account Deletion: You can delete your projects or account at any time. Deletion immediately purges all associated Docker volumes, databases, and metadata.
• Google Drive Disconnect: Disconnecting Google Drive immediately revokes access tokens via Google OAuth token endpoints and purges credentials from the OopsBase control plane.
• Oopslytics Logs Purge: Clicking "Clear" in Oopslytics performs an instant database TRUNCATE that deallocates all disk pages and TOAST records immediately.

5. Security Measures

We employ multi-layer security controls including automated TLS certificates (via Caddy and ACME), WireGuard cryptographic tenant isolation, strict role-based access control (RBAC), and continuous quota monitoring.

6. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or your data rights, please contact our data protection team:

Email: privacy@oopsbase.com / support@oopsbase.com
Website: https://oopsbase.com