SaaSWish

SaaSWish / Legal & trust

Privacy Policy

This draft explains the data handled by SaaSWish. Operator/controller identity and privacy contact: [TO BE PROVIDED BY OPERATOR].

Data we process and why

Account email, password hash, organization membership, authentication settings and API-key metadata support account access and security. Prompts, repository content, session messages, events, workspace files, designs, memory and code indexes support the engineering tasks you request.

Usage, model cost and credit ledger records support metering and billing. Stripe handles card payment processing. Audit records can include actor email, IP address, user agent, action and result for security and accountability. Connected integrations process the information required to perform your requested workflows.

Proposed legal bases for operator-controlled processing are contract performance, legitimate interests in security and service operation, and applicable legal obligations. Confirm the applicable basis and controller details before adoption.

Providers and disclosures

See Sub-processors for infrastructure, inference, payment, search, repository and optional embedding providers. Customer-connected integrations are used only when connected. We do not claim a particular provider region or transfer agreement without operator confirmation.

Retention and backups

Organization admins can set retention_days in Settings → Security & audit to remove inactive sessions. An unset value keeps sessions until deletion. Audit records default to 365 days. Usage and billing records support invoicing and accounting.

The Cloudflare deployment’s Litestream configuration retains database backups in R2 for up to 7 days (168 hours). Deleted data may remain in those backups until rotation. Workspace storage is separate from database backups; the operator must define any additional storage and legal-retention schedule.

Export and delete your data

In Settings → Account security, choose Export my data to download JSON via authenticated GET /api/privacy/export; credential hashes and secret values are excluded.

Delete my account uses POST /api/privacy/delete-account, with password and MFA verification where applicable. Transfer ownership first if you are the only owner of an organization with other members. Deletion removes your account, sessions, machines, memory and keys, and sole-member organizations. Audit records are pseudonymized by removing email, IP and user agent.

For access, correction, restriction, objection or other rights requests, contact the operator’s privacy contact [TO BE PROVIDED BY OPERATOR]. Customers acting as controllers manage requests relating to their uploaded data. You may complain to your competent supervisory authority.

Security and breach notice

See Security for technical controls. The operator will notify the affected customer/controller without undue delay and within 72 hours of becoming aware of a personal data breach. This commitment requires an operator incident-response process.