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. A password-based account can confirm its email address through a link sent by email. Confirmation is optional, except to earn or unlock an invitation reward. Plynox stores a hash of the single-use link token, which expires after 24 hours, and the date the address was confirmed.
- Subscription data: plan status, billing interval, and Stripe customer, subscription, price, checkout, and event references. Card details are handled by Stripe. If an account receives bonus Pro time, as an invitation reward or as a gift from the Creator, or buys a 7-day Creator Pass, Plynox stores when that time ends and a history of each grant: its type, its length, and its start and end dates. For a pass, the grant also keeps its Stripe checkout reference. When you open a checkout, the country your connection comes from, as our hosting provider reports it, is saved with that checkout at Stripe, with whether the checkout was opened inside the TikTok, Instagram, Facebook or another app's browser.
- Invitation records: when an account is created from an invite link, a referral record links the inviting account and the invited account and holds its status (pending, rewarded, or not eligible) with the reason for that status. To prevent the same person from being rewarded repeatedly, Plynox compares keyed hashes of the email address, of the network address, and of a device cookie of the two accounts. The raw IP address and the cookie value are not stored. Network and device hashes are stored only for accounts that take part in the invitation programme: accounts created from an invite link, and accounts that asked for their own invite link. For these accounts they are recorded when the account is created from an invite link, when you ask for your invite link and each time Plynox shows it to you afterwards, when you confirm your email address, and each time a video export of the account completes. Plynox keeps up to 8 of each kind per account. When an invitation is decided, a copy of the hashes of both accounts is saved in the referral record. These hashes are used only to apply the invitation rules.
- 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, why a failed export ended (cancelled, page in the background, memory, or other), what the Save button did with the file (shared, downloaded, opened, cancelled, or failed), 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, Export pressed, free allowance exhausted, upgrade prompt viewed, upgrade action clicked, payment form shown or not loaded in the upgrade prompt, checkout created, the button you tap under “Where is this video going?” after an export, interest in a long horizontal version of a game, a tap on “Open YouTube upload” under a finished video, and Score Predictor tournament matches opened. 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. Messages you send to the Creator and the replies you receive are stored with your account as one conversation, together with whether each side has read them.
- Content reports: if you report content or send a copyright notice, the notice you send (where the content appears and why you report it), your name and email address, and the decision taken. Plynox uses them to handle the notice and answer it, and keeps them as long as needed for that and for any dispute about it. Your name and email address are not shared with the uploader unless the law requires it.
- Announcement email records: for each announcement email addressed to your account, whether and when it was sent, a random identifier used in your personal link, and, once that link has been opened, the dates of the first and last opening and the number of openings. Your email address is not copied into these records.
- How you found Plynox: if you answer the optional question at signup or on the apps page, your answer, the account or place you name, and, only if you accepted Audience analytics, the campaign tags (UTM) of the link that brought you to Plynox, kept in your browser for up to 30 days and then saved with your account. Plynox uses them only to see where it is shared.
- Cancellation answers: if you answer the optional question when you cancel Creator Pro or withdraw, your answer is saved in your conversation with the Creator and sent to Stripe with the cancellation.
- Checkout answers: if you answer the optional question after leaving a checkout, your answer and the plan you chose are saved in your conversation with the Creator.
- 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 messages and diagnose failures;
- to handle content reports and copyright notices;
- to grant invitation rewards and gifts and to prevent repeated or self-awarded rewards;
- to announce new games, modes, and features by email and measure interest in those announcements.
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. Taps on the Continue card of the apps page are kept only as a daily count per game, with nothing about the account.
If you tick Send me tips and offers by email (at signup, on the apps page or on your dashboard), or Email me new games, video ideas, when my free exports run out, and Creator Pro offers (after an export), Plynox stores when you did and may send a few product emails, each at most once per account: when one free export remains, when the free exports are used, when an account has no export three days after signup, and when a Creator Pro checkout expires unfinished. Without that choice, they are not sent. If you had a Creator Pro plan, Plynox may also send you, as a former customer, a What's new email 30 days and 90 days after the plan ended. Each of these emails includes an unsubscribe link, and Plynox stores which of them were sent and your choices.
If you have a yearly Creator Pro plan, Plynox emails you about two months before each renewal, with its date and price and how to stop it. This notice is part of the contract and is sent whatever your email choices.
Plynox may also send announcement emails about new games, modes, and features to account holders who ticked Send me tips and offers or Email me new games, video ideas, when my free exports run out, and Creator Pro offers, or who bought a plan or a pass. Each announcement email includes an unsubscribe link, and one unsubscribe choice stops both the announcement emails and the product emails described above. An announcement email can contain a personal link to a page of Plynox. Plynox records that this link was opened, when, and how many times, with your account, to measure interest in the announcement. To see whether an announcement was useful, Plynox also checks whether the account started a game or exported a video in the 7 days after the link was first opened, and whether it unsubscribed in the 7 days after the email was sent. Announcement emails contain no tracking pixel, and Plynox does not track whether an email itself was opened or read.
Plynox also sends emails tied to something you did or received: the email confirmation link, when you ask for it or create a password-based account from an invite link; the link to your current game page, when you ask for it with Email me this link (in an app whose browser cannot export, the address you type is used only to send that one email and is not stored); a confirmation when you withdraw from Creator Pro or a pass; the day before your 7-day Creator Pass ends, a reminder that it ends, with an unsubscribe link; a notice when an invitation reward adds extra video exports or bonus Pro time to your account, or when a gift adds bonus Pro time; and a notice when the Creator replies to your message, sent once and not again until you open your messages. A message you send to the Creator may be forwarded to the Creator by email with your name and email address.
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 play a game without an account or 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 from the referrer, the source named in the address, and whether the page opened inside an app, 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.
Without any choice, Plynox counts how many times a video export is refused because a browser cannot encode video or its sound (for example inside the TikTok or Instagram app), how many times a video caption is copied, and, on the pages where you play without an account, how many runs are started and how many times Export is pressed. These are daily counts per game page, with no cookie, identifier, or browser details. They measure the use and the failures of 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, and for the product and announcement emails described in section 3;
- 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.
When you press Export in Musical Balls without an account, the music file you chose is kept in this browser for up to 24 hours so you can export it after signing up. It is never uploaded to Plynox.
Opening an invite link stores the invite code in a cookie for up to 30 days. Opening an invite link, or asking for your own invite link while signed in, also sets a device cookie that holds a random identifier for up to one year. Once an account takes part in the invitation programme, this cookie is also set in any other browser where Plynox shows that account its invite link (on the dashboard and after an export). It is used only for the invitation rules described in section 2, and it is not set for people who have not opened an invite link and whose account has not asked for its invite link.
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, product-event, and announcement email 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.
Your conversation with the Creator, the bonus Pro time history, and the network and device hashes recorded for the account are deleted with the account. Referral records are designed to remain after account deletion with the account link removed: they keep their status and the keyed hashes saved when the invitation was decided, so that deleting and recreating an account does not reset the reward limits.
8. Your choices
- update account information from account settings;
- change optional measurements through Cookie settings;
- stop product and announcement emails with the unsubscribe link at the end of each of those emails;
- 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.