Privacy Policy
This Privacy Policy explains how Subto.One (the "Service") collects, uses, and shares information. The description below is derived from an analysis of the application's source code and reflects the default behavior of the repository as provided.
Contact
For privacy inquiries or data removal requests contact: support@subto.one.
Information Collected
- Account info: Google sign-in profile (uid, email, displayName, photoURL, lastLogin, createdAt) stored in Firestore.
- Scan results: Runtime analysis, Lighthouse scores, JavaScript errors, API-check outputs, and optional base64-encoded video snapshots stored in-memory and optionally persisted.
- Uploads: Team-chat attachments are stored in a dedicated private Google Cloud Storage bucket when
GCS_PRIVATE_UPLOAD_BUCKETis configured. Each attachment has a random access token, expires after 24 hours, and is removed by a periodic cleanup task. Code Surgeon upload buffers are assembled in server memory for analysis; file content may be sent to the OpenRouter-compatible AI endpoint used by the service. Upload analytics record bounded file paths, sizes, and counts, not file content. - API key metadata: API key validation queries Firestore to map keys to user IDs; keys are compared using constant-time checks.
How We Use Data
- To run scans and return results to users.
- To validate API keys and enforce rate limits.
- To generate AI analyses, create patched ZIP downloads, and provide the web UI features.
- To send data to third-party services when those integrations are configured (e.g., VirusTotal, Google PageSpeed, Mozilla Observatory, OpenRouter).
Retention
- In-memory scan data: retained up to 24 hours (server cleanup runs hourly).
- Code Surgeon upload buffers are held in process memory while an analysis is run; the configured AI provider may apply its own retention terms to content it receives.
- Team-chat attachment links expire after 24 hours. A cleanup task runs hourly to delete expired objects; actual erasure may be delayed by storage-provider retention or soft-delete settings.
- Team-chat attachment uploads are unavailable unless a dedicated private
GCS_PRIVATE_UPLOAD_BUCKETis configured.
Security
The server applies security headers, validates Code Surgeon file paths, types, and sizes, and serves team-chat attachments through private token-verified routes when private storage is configured. API key checks use constant-time comparisons where the key lookup path supports them.
Your Choices
To request account or data removal, contact support@subto.one. Avoid uploading sensitive regulated data unless you control retention and storage.
Data Subject Rights
Subject to applicable law, you may have the right to:
- Request access to personal data we hold about you;
- Request rectification of inaccurate or incomplete personal data;
- Request deletion (the "right to be forgotten") where retention is not required by law;
- Request portability of your personal data in a commonly used, machine-readable format;
- Object to processing based on our legitimate interests where applicable; and
- Lodge a complaint with your local supervisory authority if you believe your rights have been breached.
To exercise any of these rights please contact support@subto.one. We will verify identity and respond within applicable statutory timeframes.
Automated Decision-Making & AI
The Service includes optional AI analysis features that generate recommendations and suggested code changes. These outputs are generated by deterministic heuristics and optionally by third-party AI providers when configured. Decisions that have legal or similarly significant effects are not made solely on automated processing in the default configuration. Users should review AI-generated suggestions carefully and exercise professional judgment before applying changes.
Cookies & Client-Side Storage
The front-end may use local storage, session storage, or cookies for session management and UI state. These client-side storage mechanisms do not contain sensitive secrets or API keys. If you deploy additional analytics or tracking, document those separately.
International Data Transfers
Because the Service may call third-party APIs and because hosts/operators may run infrastructure in different regions, personal data may be transferred to and processed in jurisdictions other than your own. When transfers occur, the operator will take reasonable measures (contractual safeguards, data processing agreements) to protect transferred data.
Retention and Deletion Procedures
Team-chat attachment access expires after 24 hours and expired objects are removed by an hourly cleanup task. Storage-provider retention or soft-delete settings may delay final erasure. Code Surgeon content may be processed by the AI provider configured for the service, under that provider's applicable terms. To request account or data removal, contact support@subto.one and include identifying details (account email, scan ID) to expedite verification.
Security Practices
We implement reasonable organizational and technical measures to protect personal data. These measures include strict Content Security Policy headers, HSTS, input validation, file type and size restrictions, and temporary storage purging. Operators are responsible for securing deployment secrets and production infrastructure (TLS certificates, secret managers, firewall rules, and access control).
Contact & Data Protection Officer
For privacy matters contact: support@subto.one. If your deployment requires a designated Data Protection Officer (DPO), provide the DPO contact information here.
Revision History
This document is maintained alongside the repository. Substantial policy changes will include an updated "Last updated" date and summary of changes.