Back to AstraFlow Studio
Legal Documentation

Privacy Policy

How AstraFlow Studio collects, accesses, encrypts, and protects your account information, database metadata, and Google user data.

01

Introduction, App Identity & Contact

This Privacy Policy describes how AstraFlow Studio (accessible at https://astraflowstudio.vercel.app) collects, accesses, uses, stores, and protects information when you visit our website, create an account, connect databases, or authorize optional Google Sign-In and Google Drive backup integrations.

Effective Date: November 20, 2026. For any privacy questions, data deletion requests, or Google OAuth inquiries, please contact us at vidhuraneethika000@gmail.com.

02

Google User Data Accessed & Purpose

AstraFlow Studio integrates with Google OAuth 2.0 and Google APIs solely to support user authentication and user-configured database backups to your own Google Drive. We request only the permissions needed for the feature you choose to enable:

Google Sign-In

Authentication

Online Access · Tokens Not Stored
Exact Google Scopes
openidemailprofile
Data Accessed

Verified Google email address, display name, and profile picture URL via oauth2/v3/userinfo.

Core Purpose & Token Handling

Authenticates you, creates or links your AstraFlow Studio account, and displays your workspace profile. Uses access_type=online; the Google access token is used once in-memory and never stored.

Automated Google Drive Backups

Optional · User-Enabled

Offline Access · AES-256-GCM Encrypted
Exact Google Scopes
https://www.googleapis.com/auth/drivehttps://www.googleapis.com/auth/userinfo.email
Data Accessed

Connected Google account email (userinfo.email), Drive folder hierarchy (application/vnd.google-apps.folder, including Shared Drives), and AstraFlow-created backup folders and snapshots.

Core Purpose & Token Handling

Lets you browse and create destination backup folders, upload scheduled or manual snapshots, stream downloads, and delete AstraFlow-created backups on request. Uses access_type=offline with AES-256-GCM encrypted token storage.

Specifically, when you connect Google Drive for database backups, AstraFlow Studio uses your granted permissions solely to:

  • Identify the connected Google account: Retrieve your Google account email via userinfo.email so workspace members can see which Google Drive account is linked.
  • List and search Drive folders: Query folders (mimeType = 'application/vnd.google-apps.folder', including Shared Drives if accessible to you) so you can pick a destination parent folder for your backups.
  • Create destination backup folders: Create folders you explicitly request in the folder picker and a dedicated per-database subfolder inside your selected destination folder.
  • Upload database backup files: Upload exported database backup snapshots (.sql, .json, .csv, or .zip) to your chosen Google Drive folder on manual trigger or your configured schedule (hourly, daily, weekly, or monthly).
  • Download your backups on request: Stream a previously uploaded AstraFlow Studio backup file from Google Drive to an authorized workspace member when you click Download.
  • Delete AstraFlow-created backup files on request: Delete only the specific backup file or database backup subfolder created by AstraFlow Studio when an authorized workspace member deletes a snapshot run or disables a backup schedule with Drive cleanup (which requires fresh Google re-authorization).

AstraFlow Studio never reads, scans, indexes, analyzes, or modifies unrelated personal files, documents, photos, or folders in your Google Drive.

03

Google API Services User Data Policy (Limited Use Disclosure)

Mandatory Google API Services Disclosure

AstraFlow Studio's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In strict compliance with Google's Limited Use requirements:

  • We limit our use of Google user data strictly to providing or improving user-facing authentication and database backup features prominently described in AstraFlow Studio.
  • We do not transfer or disclose Google user data to third parties except as necessary to provide the requested backup/sign-in functionality, for security purposes, or to comply with applicable law.
  • We never use Google user data or Google Drive file contents for advertising, ad targeting, data brokering, creditworthiness, or training generalized artificial intelligence or machine learning models.
  • Human access to Google user data does not occur unless we obtain your explicit affirmative consent for support debugging, it is necessary for security or abuse prevention, or it is required by applicable law.
04

Other Information We Collect

Beyond optional Google integrations, AstraFlow Studio processes the following categories of information required to run the database studio:

  • Account & Workspace Data: Your name, email address, securely hashed password (when using email/password authentication), UI preferences, workspace names, role-based access control (RBAC) memberships, and workspace invitations.
  • Database Connection & Schema Metadata: Connection labels, database engine types (PostgreSQL, MySQL, MongoDB), host/port details, encrypted connection credentials, uploaded database files (.sql, .json, .jsonl, .csv), schema snapshots, ER diagram layouts, schema comparisons, migration execution logs, and workspace audit logs.
  • Essential Session & Security Cookies: We use strictly necessary functional cookies—an HTTP-only signed session JWT cookie (astraflow_session), an active workspace selector cookie (astraflow_workspace), and a short-lived CSRF state cookie during OAuth flows (astraflow_google_oauth_state). We do not use advertising or cross-site tracking cookies.
  • Session Security Metadata: Basic IP address and user-agent strings recorded on active login sessions and rate-limiting checks to detect unauthorized access and protect against abuse.
05

Data Storage, Encryption & Security

We apply defense-in-depth technical safeguards to minimize stored data and protect sensitive credentials:

  • Google Sign-In Tokens Are Not Stored: Access tokens issued during Google Sign-In are used strictly in-memory during the OAuth callback to retrieve your verified profile and are immediately discarded.
  • AES-256-GCM Encryption at Rest for Drive Tokens & DB Secrets: When you connect Google Drive for scheduled backups, your OAuth access and refresh tokens—along with any database connection credentials you save—are stored server-side in encrypted form using AES-256-GCM authenticated encryption with a unique 12-byte random initialization vector (IV) and 16-byte authentication tag per record.
  • No Permanent Server Storage of Google Drive Backup Files: Backup file payloads generated by scheduled or manual backups are not permanently stored on AstraFlow Studio servers. During execution, backup archives are staged in an isolated ephemeral temporary directory, uploaded directly to your Google Drive, and immediately deleted from our server upon completion or failure. Backup downloads stream directly from Google Drive to your browser. Only lightweight run metadata (file name, byte size, Drive file ID/link, schema hash, timestamps, and status) is kept in your workspace backup history.
  • Transport & Application Security: All traffic uses HTTPS/TLS encryption in transit, HTTP-only signed session cookies, workspace role-based access control (RBAC), and Server-Side Request Forgery (SSRF) protections.
06

Data Sharing & Third-Party Disclosures

AstraFlow Studio never sells, rents, trades, or shares your personal information, database credentials, or Google user data with third-party advertisers, marketing networks, or data brokers.

We transmit data externally only in the following strictly limited circumstances:

  • User-Initiated Google Integrations: Communicating with Google OAuth and Google Drive APIs when you choose to sign in with Google or enable Google Drive backups.
  • Essential Infrastructure Providers: Hosting and managed database infrastructure providers (such as Vercel and cloud PostgreSQL hosting) strictly needed to operate AstraFlow Studio under confidentiality and security obligations.
  • Legal Compliance & Safety: If required by applicable law, subpoena, or valid court order, or to protect against fraud, abuse, or security threats.
07

Data Retention, Revoking Access & Account Deletion

You remain in full control of your Google permissions and AstraFlow Studio account data at all times:

  • Disconnect Google Drive In-App: Workspace administrators can disconnect Google Drive at any time from Dashboard → Auto Drive Backups. Disconnecting immediately and permanently deletes all stored encrypted Google Drive OAuth tokens from our database.
  • Revoke Access via Google Account Permissions: You can revoke AstraFlow Studio's access to your Google Account and Google Drive at any time from your Google Account Permissions page (https://myaccount.google.com/permissions). Revoking permissions immediately invalidates all issued OAuth tokens.
  • Request Account & Data Deletion: To delete your AstraFlow Studio account, owned workspaces, encrypted database credentials, session records, and associated metadata, email vidhuraneethika000@gmail.com from your registered email address. Verified deletion requests are completed within 30 days. Backup files previously uploaded to your Google Drive remain solely in your Google Drive account under your direct control.
08

Children's Privacy

AstraFlow Studio is a developer and database administration platform and is not directed to individuals under the age of 13 (or the applicable age of digital consent in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided personal data to us, please contact vidhuraneethika000@gmail.com so we can promptly delete it.

09

Changes to This Policy & Contact Us

We may update this Privacy Policy periodically to reflect improvements to AstraFlow Studio or changes in legal or Google API requirements. When we make changes, we will update the Effective Date at the top of this page. Your continued use of the service after any update indicates acknowledgment of the revised policy.

If you have questions or requests regarding this Privacy Policy or our data practices, contact us at vidhuraneethika000@gmail.com or review our Terms of Service.