Privacy Policy

Information you provide

Account information includes your email address, sign-in provider identifiers, account and session identifiers, and any display details you choose. Clerk provides sign-in and account management. We use account identifiers to associate saved work and access permissions with your account.

Content can include card messages, names you enter, photos, drawings, selected image areas, prompts, generated images or code, game settings, saved versions and publishing choices. Photos can show people and background details. Only submit information and images you have permission to use, and avoid sensitive details that are not needed for your card.

We also receive support messages, feedback you submit, consent and review choices, plan or access status, and payment or promo records where applicable. Promo records identify the campaign and account, and a card where relevant. Promo benefits may apply to a card or an account as described in the offer; redeeming a promo does not by itself create a Plus subscription.

Device storage and automatically collected information

Your browser may keep drafts, original images, selections, settings and game progress in local storage, session storage or IndexedDB. Some editing and image preparation happen on your device. Saving to your account, sharing, or requesting an AI feature can send relevant content to our servers. Choosing a file is not a promise that all later operations will stay on your device.

Our systems and hosting providers process connection and operational information, such as IP addresses, browser and device information, request times, page addresses, status codes and security events. AI usage records can include request identifiers, model names, usage counts and cost estimates. First-party card-loading diagnostics record limited stage, status, build and request-correlation information rather than card contents. Other operational and support records can contain information you provide.

We use Google Analytics to measure website visits and usage. Analytics can process public page categories and event labels, browser and device details, and cookie or similar identifiers. Our application limits the page and event information it sends rather than sending private card contents or raw share-link tokens as analytics labels. Browser settings and blocking tools can limit some processing. Blocking storage can also affect sign-in or draft recovery.

We also use first-party measurements to understand card creation, publication, recipient opens and play, and whether recipients choose Make a card and later publish a new card. These measurements use a random identifier in session storage and coded identifiers for cards and creator accounts. Measurement events exclude card contents, photos, descriptions, email addresses, share-link tokens and full page addresses. We do not forward these events to Google Analytics or other external analytics services.

If you choose Make a card from a shared card while signed in, or sign in afterwards in the same tab, we may connect earlier activity in that tab to the adult creator account. This connection measures new-card publication for up to seven days from the first recorded card open, or from the click if the open was not recorded. Closing the tab before sign-in or blocking storage can prevent the connection. Once connected, an eligible publication on another device can count during the remaining window.

How we use information

We use information to operate sign-in and account access; prepare, generate, save and display cards; carry out your sharing choices; remember work and settings; provide support; investigate failures; prevent abuse; manage access, payment and promo records; and meet legal obligations.

We use usage measurements and feedback to understand and improve the product. Feedback reports may include the description and reproduction details you approve, including prompts, generated code or interaction history where the report explains this. Do not include private details that are unnecessary to investigate the issue. Approved reports may be copied to our private GitHub issue system when that integration is enabled.

Photos, drawings and AI requests

Some tools process an image locally. When you request an AI feature, the selected image or crop, your prompt, relevant card context and generated results may be sent to our servers and AI service providers to perform the request and applicable safety checks. For example, requesting an AI character or coloring outline can involve image processing outside your device. Review the input and the feature notice before requesting a conversion.

Different AI operations process different inputs. A text safety check does not mean an image has been reviewed for safety. Automated checks and your own review cannot eliminate every risk.

AI service providers may process or retain information for security, abuse monitoring and other purposes under the terms and settings that apply to the service. Application deletion and removal from your account do not necessarily delete provider records at the same time.

Service providers and other disclosures

We use service providers for authentication, website hosting, application storage, AI processing, analytics, transactional email and support. These include Clerk, Vercel, Railway, Microsoft Azure AI services, OpenAI and Google Analytics. Some AI tools may use Anthropic where configured. Transactional email, feedback and issue-management providers receive information needed for their functions, including approved reproduction details when you choose to send a report. We provide information to these providers as needed for the functions described in this policy.

Clerk Billing manages subscriptions, and Stripe processes payment details. Our application can keep transaction identifiers, payment status, amount, currency and the associated account or card. Payment fields are handled through the payment provider.

We may disclose information to comply with law or valid legal requests, address fraud or safety risks, enforce our terms, protect rights, or complete a business transfer subject to applicable protections. Authorized personnel may access information for these purposes and to operate or support the service.

Sharing a card

Account-saved work is not a published card merely because you saved it. When you choose Share or publish, the playable card and its included messages, images and other content become accessible to people with the link or QR code. Recipients do not need your account or a Plus subscription. They can pass the link on, take screenshots or save copies. A link is an access mechanism, not a guarantee that only your intended recipient will see it.

For the photo-piece sharing flow, the whole kept photo, including its background, is included after explicit confirmation. For new or explicitly republished shares under the saved-card policy, we keep the photo with your saved card until you delete the card. Unshare stops future service-link access and retains your private saved copy. Earlier seven-day shares keep their original expiry unless you explicitly republish before expiry. Unpublished generated images need a current safety approval. For eligible shared cards, we retain approval bound to the exact safety-checked published image, subject to revocation and deletion. Changed images need fresh checks. These rules do not erase separate local files, recipient copies or provider records.

Unshare stops subsequent access through the live service link. It cannot erase a page already loaded, downloaded copies, screenshots or previews cached by messaging services. Published cards can expose a preview image or descriptive text to a messaging service when a link is shared; photo-piece links use a generic preview instead of a photo thumbnail.

Retention and deletion

Account records, saved cards, versions and publishing records are kept to provide your account and cards until deletion or another applicable retention rule applies. Local browser copies can remain until removed or evicted by the browser. Free access, Plus access and promo redemption do not by themselves establish a separate guaranteed storage period or backup service.

The account-data deletion process first restricts account and published-link access, then schedules an application-data purge after a 90-day waiting period. It applies to the associated application account group and its saved work, which can include data from other experiences using that same account group. Individual deletion actions can have a different scope. Removing the sign-in account alone is not the same as removing all application data; contact us for a complete account-data request and to confirm its scope.

Provider records, operational logs, feedback, backups and records retained for security or legal obligations have separate retention and deletion arrangements. Deletion from the active application does not guarantee immediate deletion of every copy. Contact us to ask about records that are not covered by an available deletion control.

We schedule first-party measurement events for deletion after 30 days and coded card identifiers for deletion 30 days after their last public lookup. Active visit-to-account connections last up to seven days. Periodic cleanup can delay removal of expired records. These periods apply to active measurement records; backups have separate retention arrangements.

Your choices and rights

Use available editing, deletion and Unshare controls, or contact support@yourstoplay.com to request access, a copy, correction, deletion or help stopping further collection. We may need to verify your identity and authority before acting. We explain the scope of a request and any information that must be retained under applicable law.

Depending on where you live and which laws apply, you may have additional rights, including portability, restrictions or objections to processing, and rights to opt out of sale or sharing. California rights can include knowing, deleting and correcting information, limiting certain uses of sensitive information and exercising rights without unlawful discrimination. Contact us to make a request.

First-party browser observations and visit-to-account connections are skipped when Global Privacy Control or Do Not Track is enabled, or session storage is unavailable. Server publication totals are counted separately. These controls do not turn off separate Google Analytics or operational diagnostics.

Information about children and recipients

Accounts are for adults to operate. Adults may include information about other people in cards, and recipients may be children. Include only information you have permission to use and that is needed for the card. Where applicable law requires direct notice or verifiable parental consent, account sign-in, acceptance of the Terms of Use and upload permission do not replace those requirements.

A parent or guardian may contact support@yourstoplay.com to review information about their child, request deletion or stop further collection or use, subject to verification and applicable law. We do not require a child to provide more information than is reasonably necessary for an activity. If you believe information about a child was provided without required permission, contact us so we can investigate and address it.

Recipient measurements can occur when a child opens or plays a card without an account. Coded identifiers do not establish a recipient’s age or parental permission.

Security, international processing and updates

We use administrative and technical safeguards intended to protect information, but cannot guarantee perfect security. The service and its providers may process information in the United States and other countries with different privacy laws. Do not submit unnecessary sensitive information.

We will identify the effective date of the approved policy and provide notice of material changes where required. Privacy questions and requests can be sent to support@yourstoplay.com.