PRIVACY NOTICE
Plain language about
what is collected.
This notice covers the free public launch. It is written to be read, not to hide behind defined terms. It does not claim a certification or a data-residency guarantee that does not exist.
Free Early Access notice. Commercial terms and a production privacy program must be reviewed before any future paid operation.
1. Scope of this notice
This notice describes the SubSync Guard Free Early Access web application, its browser CSV audit, its connected workspace features, and the feedback, referral, and privacy-safe analytics features that support the public launch.
The controller of a workspace is the organization that created it. SubSync Guard processes workspace data on behalf of that organization and provides export and deletion controls to the workspace owner.
2. Data we process
Account data: email address, authentication identifiers, session metadata, and workspace membership.
Workspace data: workspace name, role assignments, invitations, connection status, findings, review notes, and audit preferences.
Billing metadata: Stripe customer and subscription identifiers, status, plan, quantities, and period dates for connected customer accounts. The connected Stripe key is stored encrypted and is never displayed again after submission. Platform billing is disabled during Free Early Access, so no card is requested or charged.
Entitlement metadata: application user or organization identifiers, plan, access state, and expiry dates supplied through a signed snapshot. Do not include names, payment details, or free-form profile data in the connector.
Alert destinations: an email address, Slack webhook URL, or allowlisted custom webhook URL. Destinations are masked in the interface after saving.
Feedback data: a 1–5 rating, feedback category, written message, and optional testimonial or attribution consent with a display name and company. Feedback is private by default and visible only to the submitting user and the platform operator.
Referral data: an opaque workspace referral code and the fact that a referred account activated it after creating a workspace. The link contains no workspace name, findings, customer data, or email address.
Product analytics: an allowlisted event name, page path, small non-sensitive scalar properties, and a daily salted visitor hash derived from network and browser metadata. Raw IP addresses, user agents, account identifiers, emails, API keys, and customer records are not stored in the analytics table. Do Not Track is respected.
Technical logs: function errors and operational metadata needed to run and secure the service. Logs are designed not to contain connector secrets or full snapshot bodies.
3. Why we process it
To authenticate users and enforce workspace permissions.
To compare billing and entitlement states and produce advisory findings.
To deliver alerts that a workspace administrator explicitly configures.
To provide exports, deletion controls, feedback review, referral activation counts, and support for the workspace.
To measure whether the public launch is understandable and usable through aggregate, privacy-safe product events.
To secure the service, investigate abuse, and diagnose failures.
We do not sell personal data, use it for advertising, or train a model on workspace records.
4. Storage and providers
The application is hosted on Cloudflare Pages. Authentication, database, and Edge Functions run on Supabase. Stripe provides read-only customer billing APIs; platform checkout is disabled during Free Early Access. Email alert delivery, when configured, uses Resend.
These providers process data under their own terms and security programs. The free launch does not claim a specific data-residency guarantee. Workspace owners should not store regulated data in the free environment.
Connector secrets are encrypted with AES-256-GCM under a server-side key. Card data is not processed by SubSync Guard.
6. Retention
Workspace records remain until the workspace owner deletes them or the workspace. Findings and snapshots can be erased by scope. Invitations expire after seven days and can be revoked sooner.
Feedback remains until the workspace is deleted, the submitting user requests removal, or the operator archives it. Archiving changes an internal status; it does not silently delete negative feedback.
Sanitized product events contain no direct account identifiers and are kept only for launch measurement and abuse prevention. Infrastructure logs are retained according to the hosting provider’s operational settings. The free launch does not publish a fixed log-retention period because the deployment configuration is operator-controlled.
7. Your choices and rights
Workspace owners can export findings, snapshot metadata, and sync runs as JSON, and can erase audit data from Settings.
An authenticated user can request removal of their feedback or membership by contacting the workspace owner or the operator. Account deletion can be requested through the support channel.
Depending on your jurisdiction, you may have rights to access, correct, delete, restrict, or object to processing, and to lodge a complaint with a supervisory authority. Use the contact channel to make a request. Identity verification may be required.
8. Security
The security model is documented on the Security page, including the controls that are implemented and the verification that remains pending. No service can guarantee absolute security.
Do not send secrets, invitation tokens, or real customer records through a public issue.
9. Changes and contact
This notice may change as the product moves from Free Early Access to a future commercial release. Material changes will be reflected in the changelog and in the effective date on this page. No future paid plan will be activated without an explicit opt-in.
For privacy questions, open a GitHub issue that does not contain personal data, or use the repository’s private security advisory channel if the matter is sensitive.
Privacy questions: the public issue tracker. Do not include personal data. For sensitive matters, use the private advisory channel described on the security page.