Privacy Policy

This Privacy Policy explains how DBBackup ("DBBackup," "we," "our," or "us") collects, uses, discloses, stores, retains, and protects information in connection with the DBBackup website, applications, APIs, and related services (collectively, the "Service").

This Policy should be read together with our Terms of Service. Capitalized terms not defined here have the meaning given to them in the Terms of Service.

DBBackup is intended for professional and business use, is available worldwide, and is designed to help customers automate, store, and restore PostgreSQL database backups.

1. Scope of This Policy

1.1 Who This Policy Covers

This Policy applies to:

• individuals who create an Account and use the Service ("you," "User");
• individuals whose personal data may be contained within a customer's own database and, as a result, within a Backup created through the Service.

1.2 Two Different Roles We Play

For the personal data described in Section 1.1(a) (your own Account and usage data), DBBackup acts as a data controller: we decide why and how that data is processed.

For Customer Data described in Section 1.1(b) (the contents of the databases you back up, which may include personal data about your own end users), DBBackup acts as a data processor (or sub-processor): you, the customer, control what is stored, and we process it solely to provide the Service, under your instructions. We do not access, read, analyze, or use the content of your backups for any purpose other than storing and, when you request it, restoring them.

1.3 Worldwide Service

DBBackup is available to customers in multiple countries. Because privacy laws differ by jurisdiction, some rights described in Section 9 apply only to residents of certain regions (for example, the EU/UK GDPR and California's CCPA/CPRA), as noted.

2. Information We Collect

2.1 Account Information

When you register and use the Service, we collect:

• your email address;
• your password, stored only as a bcrypt hash — we never store or have access to your plaintext password;
• your display name (if provided);
• your subscription plan and billing status;
• two-factor authentication status (whether TOTP-based 2FA is enabled) and, if enabled, an encrypted TOTP secret;
• your admin status, if applicable (internal accounts only).

2.2 Payment Information

DBBackup does not collect, process, or store your full payment card details. Payments are handled entirely by Stripe through Stripe's own hosted checkout and billing-portal pages. We receive and store only a Stripe customer identifier, which lets us associate your Account with your subscription — we never receive or store your card number, CVV, or full payment credentials.

2.3 Database Connection Information

To provide the Service, you provide database connection information (host, credentials, and related configuration) necessary for DBBackup to connect to your database and create backups. This connection information is encrypted at rest before storage — see Section 5 for exactly how.

2.4 Backup Content ("Customer Data")

The core of the Service involves creating and storing Backups — copies of your database's contents, generated according to your configuration. This may include any personal data that exists within your own database, about your own end users, employees, or other individuals. This content is encrypted at rest (see Section 5) and is not accessed, read, or analyzed by DBBackup except as strictly necessary to provide the Service (creating, storing, and restoring backups) or as required by law.

2.5 Session and Device Information

We collect information about your login sessions, including:

• IP address at login and at subsequent activity — at login, this IP is also used to derive an approximate country via Cloudflare's IP geolocation, shown in the new sign-in notification email described in Section 6.1; this derived country value is not stored;
• a parsed device/browser identifier derived from your User-Agent string;
• session creation and last-active timestamps;
• a refresh-token identifier used to track and allow you to revoke individual sessions (visible to you under Settings → Active Sessions);
• a long-lived device-recognition token, stored only as a one-way hash, that lets us recognize a browser you've successfully signed into before (visible to you under Settings → Recognized Devices, where you can forget a device at any time). This token exists solely to detect sign-ins from a device we don't recognize yet, so we can ask for extra confirmation and notify you — see Section 3 and Section 10.1. It is not used for advertising, analytics, or tracking your activity anywhere else.

2.6 Usage and Operational Information

We collect information generated by your use of the Service, including:

• backup job history: status, file size, timing, and (on failure) error messages;
• storage usage per month;
• notification preferences;
• API key metadata (name, scope, prefix, expiration, last-used timestamp and IP — never the raw key itself, which is shown to you only once at creation and stored by us only as a one-way hash);
• audit log entries for security-relevant events on your Account (e.g. login, password change, plan changes).

2.7 Information We Do Not Collect

We do not use any third-party analytics, advertising, or tracking tools (such as Google Analytics, Meta Pixel, Hotjar, Mixpanel, or similar) anywhere in the Service. We do not build advertising profiles. We do not sell personal data.

3. How We Use Information

We use the information described in Section 2 to:

• create and manage your Account;
• authenticate you and secure your Account (including fraud and abuse detection);
• provide the core Service: scheduling, running, storing, and restoring backups;
• process payments and manage your subscription (via Stripe);
• send transactional and security-related communications (Section 6);
• enforce plan limits, storage quotas, and retention policies;
• investigate and respond to security incidents, abuse, or violations of our Terms of Service;
• comply with legal obligations;
• improve the reliability, performance, and security of the Service.

We do not use your Account data or Backup content to train artificial intelligence or machine learning models. DBBackup has no AI/LLM integrations of any kind — no user data, backup content, or connection metadata is ever transmitted to any AI service.

4. Sub-processors and Third-Party Services

To provide the Service, we share limited data with the following sub-processors. We do not permit any of them to use your data for their own independent purposes.

• Supabase — hosts our application database (account records, metadata, audit logs). Data involved: account data, operational metadata.
• Railway — hosts our backend application. Data involved: all data passing through the Service at runtime.
• Cloudflare R2 — stores encrypted backup files. Data involved: encrypted Backup content.
• Cloudflare Turnstile — bot/abuse protection on login and signup. Data involved: limited technical/browser signals; no personal profiling.
• Stripe — payment processing and subscription billing. Data involved: billing contact info, payment method (held by Stripe, not us).
• Resend — sends transactional email (verification, backup notifications, billing alerts). Data involved: your email address and the content of the relevant notification.
• Vercel — hosts our website and dashboard frontend. Data involved: standard web request data (no additional personal data beyond what's needed to serve the page).

We may update this list as our infrastructure evolves; material changes will be reflected in an updated version of this Policy.

5. How We Protect Your Data

5.1 Encryption at Rest

Database connection strings and Backup file contents are encrypted at rest using envelope encryption:

• Each user is assigned a unique, randomly generated data encryption key ("DEK") on first use, used to encrypt their database connection strings.
• Each individual backup is separately encrypted with its own randomly generated DEK, distinct from your connection-string DEK and from every other backup — so a compromise of one backup's key does not expose any other backup.
• Every DEK — whether for connection strings or an individual backup — is itself encrypted ("wrapped") using a master key and stored only in its wrapped (encrypted) form; the unwrapped DEK is never persisted.
• Connection strings and backup files are encrypted using their respective unwrapped DEK, which is only ever reconstructed in memory at the moment it's needed.
• The underlying encryption mechanism is AES-256-GCM, an authenticated encryption algorithm that provides both confidentiality and tamper detection in a single operation.

This means each customer's data is encrypted with a distinct key, and each individual backup is further isolated by its own distinct key, so a compromise of one user's key — or even one single backup's key — does not expose any other user's or backup's data.

5.2 Passwords

Account passwords are hashed using bcrypt before storage. We never store or have access to your plaintext password.

5.3 Payment Data

We never receive or store full payment card numbers, CVV codes, or equivalent sensitive payment credentials — this is handled entirely by Stripe.

5.4 Access Controls

Our database uses row-level security enabled on all tables, and our backend accesses the database exclusively through a restricted service-level credential, never a broadly-scoped key. Administrative actions taken by DBBackup staff on customer accounts are separately audit-logged.

5.5 No Absolute Security Guarantee

No internet-connected service can guarantee absolute security. While we implement commercially reasonable technical and organizational safeguards, we cannot eliminate all risk of unauthorized access, data loss, or security incidents. See the Terms of Service for the corresponding allocation of risk and liability.

6. Communications We Send

6.1 Transactional and Security Emails

We send emails that are necessary to operate your Account and the Service, including: email verification, backup success/failure notifications, storage quota warnings, payment failure notices, connection-paused notices, backup reports, free-plan time-limit warnings, and account deletion confirmations. These are transactional/relationship messages, not marketing, and are not subject to unsubscribe requirements under applicable law (such as CAN-SPAM) — however, we provide in-app Notification Preferences that let you turn off several of these (backup success, backup failure, free-plan warnings) even though not legally required to. Security-critical emails (verification, password/2FA changes, new sign-in/new-device alerts, billing receipts) always remain on and cannot be disabled, to protect your Account. New sign-in alerts are sent whenever your Account is accessed from a device we don't recognize yet, and include a self-service link to immediately sign out every device on your Account if you don't recognize the activity.

6.2 No Marketing Email (Currently)

As of this Policy's effective date, DBBackup does not send marketing or promotional email campaigns. If this changes in the future, any such email will include a clear opt-out mechanism as required by applicable law, and will be clearly distinguished from transactional communications.

7. Data Retention and Deletion

7.1 Backup Retention

Backups are retained on a rolling, count-based basis determined by your subscription plan (the oldest backup for a given connection is automatically deleted once the plan's retention count is exceeded). Current plan retention counts and manual-backup frequency limits are described on our pricing page and may change from time to time.

7.2 Free Plan Data Handling

If you use a Free plan, the following applies based on your account's cumulative time on a free plan:

• Days 0–30: normal Free-plan retention applies.
• Days 31–60: retention is reduced to 1 backup per connection; older backups beyond that are actively deleted (both the stored file and its record).
• Day 61 onward: no new backups (manual or scheduled) can be created. Your existing backup and dashboard access remain available — nothing further is deleted at this stage.

7.3 Account Deletion

You can request deletion of your Account at any time from Settings. Deletion is a two-step process:

• Your Account enters a 30-day grace period, during which it is deactivated but not yet purged, in case you change your mind.
• If not restored within that window, your Account, connections, backups, and associated data are permanently and irreversibly purged, including the underlying files stored in Cloudflare R2.

If your Account is restored (by you, within the grace period, or in limited cases by our support team), full access is returned and no further action is needed.

7.4 Operational and Security Records

Certain records — audit logs, security logs, and billing records — may be retained for a longer period than your primary Account data where necessary to investigate security incidents, prevent fraud, resolve disputes, or comply with legal obligations, even after your Account is deleted.

7.5 Backups Are Not a Permanent Archive

DBBackup does not guarantee indefinite preservation of any data. You are responsible for exporting or otherwise preserving any information you wish to retain beyond your plan's retention window or beyond the life of your Account.

8. International Data Transfers and Hosting Location

8.1 Where Your Data Is Hosted

All of DBBackup's infrastructure is currently hosted in the western United States:

• Our application database (Supabase) is hosted in the US (N. California / us-west-1 region).
• Backup files (Cloudflare R2) are stored in the Western North America (WNAM) region.
• Our backend application (Railway) runs in San Francisco (sfo region).

8.2 International Transfers

Because the Service is available worldwide but our infrastructure is located in the United States, using the Service from outside the US necessarily involves an international transfer of your data to the US. Where required (for example, for users in the EU/UK), we rely on the standard contractual safeguards and data protection commitments already maintained by our infrastructure providers (Supabase, Cloudflare, Railway) as part of their own compliance frameworks, in addition to the technical safeguards described in Section 5.

If you have specific data-residency requirements, please contact us at support@infracherry.com before relying on the Service for that use case, as we do not currently offer region-selectable hosting.

9. Your Privacy Rights

9.1 Rights for All Users

Regardless of location, you can, through your Account settings or by contacting us:

• access and review the personal data associated with your Account;
• correct inaccurate Account information (via Settings);
• delete your Account and associated data (Section 7.3);
• manage your notification preferences;
• revoke individual login sessions or API keys.

9.2 Additional Rights for EU/UK/EEA Users (GDPR)

If the GDPR or UK GDPR applies to you, you additionally have the right to: request a portable copy of your personal data; object to or restrict certain processing; and lodge a complaint with your local data protection supervisory authority. Because the Service does not currently include a self-service data export tool, portability and access requests beyond what's visible in your Account should be directed to support@infracherry.com; we will respond within the timeframe required by applicable law.

9.3 Additional Rights for California Residents (CCPA/CPRA)

If you are a California resident, you have the right to know what personal information we collect, to request its deletion, and to non-discrimination for exercising these rights. DBBackup does not sell or share personal information as those terms are defined under the CCPA/CPRA.

9.4 Verifying Your Identity

To protect your Account, we may need to verify your identity before fulfilling certain requests (particularly those submitted by email rather than through your logged-in Account).

9.5 How to Exercise These Rights

Email support@infracherry.com with your request. This is currently our only dedicated contact channel for privacy-related requests.

10. Cookies and Similar Technologies

10.1 What We Use

DBBackup uses only the technical cookies/tokens necessary to operate the Service:

• an httpOnly authentication cookie that keeps you logged in;
• a token issued by Cloudflare Turnstile, used solely to distinguish humans from bots during login and signup;
• an httpOnly device-recognition cookie, stored for up to a year, used solely to recognize a browser you've previously signed into successfully. Its only purpose is account security and fraud prevention — detecting a sign-in from an unrecognized device so we can ask for extra confirmation and notify you (Section 2.5, Section 3). We do not read it, or any other cookie described here, for analytics, advertising, or behavioral tracking of any kind — see Section 10.2, which remains fully accurate with this cookie included.

10.2 What We Don't Use

We do not use advertising cookies, cross-site tracking cookies, or any third-party analytics cookies. We do not build a profile of your browsing behavior across other websites. This applies equally to every cookie listed in Section 10.1, including the security-purpose device-recognition cookie — none of them are ever repurposed for analytics, advertising, or tracking.

11. Children's Privacy

The Service is intended for professional and business use by individuals at least 18 years of age. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, contact us at support@infracherry.com and we will take appropriate steps to delete it.

12. Changes to This Policy

We may update this Policy from time to time to reflect changes in our practices, infrastructure, or legal requirements. Material changes will be communicated in accordance with the notice provisions in our Terms of Service (typically by email and/or an in-app notice) before they take effect. The "Last Updated" date at the top of this Policy reflects the most recent revision.

13. Contact Us

If you have questions about this Privacy Policy or how we handle your data, contact us at:

support@infracherry.com

This is currently our only published contact channel; it covers general support, privacy, and security inquiries alike. If we establish dedicated privacy@ or security@ addresses in the future, this Policy will be updated to reflect them.

This Privacy Policy works together with our Terms of Service. In the event of any inconsistency between the two regarding privacy or data handling, this Privacy Policy controls.