1. Overview
This policy describes the personal data processed when you use Plynox and the choices available in the current Service. It does not claim certification or compliance with a particular legal framework.
2. Data processed by the Service
- Account data: name, email address, profile image, authentication records, and a password hash for password-based accounts. If you choose Google sign-in, Plynox stores the account connection data returned through that sign-in flow. If you use a referral link, the Service also stores a referral code and the server-derived inviter account link. That inviter link is removed if the inviter account is deleted.
- Subscription data: plan status, billing interval, and Stripe customer, subscription, price, checkout, and event references. Card details are handled by Stripe.
- Content and settings: custom marble images and sounds, crowd audio, nation skins, maps, folders, lineups, and other settings you choose to save. Depending on the feature, this data is stored in your browser or in account-linked database and private Blob records.
- Run and export records: account ID, app, run counts, export claim identifiers, export status, whether a credit was used, and the account-wide used and remaining export allowance. These records do not contain the exported video, filename, marble names, or commenter names.
- Low-cardinality product events: game run started or completed, free allowance exhausted, upgrade prompt viewed, upgrade action clicked, and checkout created. Events may include an allowlisted app, source, and reason. Plynox does not accept free-form product-event payloads through this tracking route.
- Feedback and support: ratings, messages, and the context you submit through feedback or support features.
- Security data: limited request metadata used for rate limiting, authentication, abuse prevention, and safe error logging.
3. How data is used
- to create and secure accounts;
- to provide games, saved content, and video export features;
- to apply the account-wide free export allowance;
- to provide subscriptions and billing through Stripe;
- to measure product operation and the account conversion funnel;
- to respond to feedback and diagnose failures.
Product events are first-party operational records. They are not sent to optional Vercel audience analytics, and the current implementation does not send them to PostHog.
4. Optional public-page measurements
Five optional choices are off by default. Audience analytics counts public page views and broad arrival sources in Plynox's database and enables Vercel Web Analytics. Navigation interactions count clicks to public game pages. Signup interest counts clicks to the signup page. Upgrade interest counts clicks to pricing. Page performance counts broad initial load-time bands after prior consent. These counts do not identify visitors or prove completed signups or subscriptions.
Plynox stores optional first-party measurements as daily counts by allowlisted public page and event category. It does not store a visitor identifier, IP address, email, full URL, URL query, fragment, or referrer. Broad arrival source groups are derived in the browser and only the category is counted. Vercel Web Analytics receives events only when Audience analytics is enabled, only for allowlisted public pages, after query strings and fragments have been removed. Authentication, account, application, admin, and API pages are excluded.
You can choose Accept all, Essential only, or customize each optional purpose. You can change your choice here at any time. The choice cookie expires after 180 days. Use Cookie settings on this Privacy Policy page to review it. Essential account, billing, and security records continue where required to provide the Service.
5. Service providers
Data is shared as needed with providers used by the selected feature:
- Stripe for subscriptions and payments;
- Google when you choose Google sign-in;
- Vercel for hosting, private Blob storage, runtime operation, and optional public-page audience analytics after acceptance;
- the configured email provider for account, security, support, and billing messages;
- asset delivery services when the product requests public flags or proxies an image URL used by a feature.
6. Browser storage
Plynox uses authentication and security cookies, the optional measurement choice cookie, referral attribution, and feature preferences. Game settings and media may also be stored in local storage, session storage, cookies, or IndexedDB. Clearing site data removes browser-held records on that device but does not delete account data stored by the Service.
7. Account deletion and retained records
The account deletion flow removes the account and cascades deletion to account-linked authentication, content, usage, export allowance, export-attempt, and product-event records. It also attempts to remove the account's private Blob assets. Browser storage on other devices is not cleared automatically.
Some billing audit events and export feedback are designed to remain after account deletion with the account link removed. Stripe and other providers may keep their own records under their policies and obligations.
8. Your choices
- update account information from account settings;
- change optional measurements through Cookie settings;
- delete the account through the authenticated account flow;
- contact privacy@plynox.app about a privacy request.
9. Security
Current controls include password hashing, HTTPS in production, authenticated file routes, access checks, rate limiting, Stripe webhook signature verification, and restricted error logging. No online system can guarantee absolute security.
10. Changes and contact
This policy may be updated when the Service changes. The date above will be updated when the public policy changes. Questions can be sent to privacy@plynox.app. See also the Terms of Service.