Your data, explained.

This policy explains how ShouldI at shouldi.fyi handles information. The AI, account and payment sections apply when you use those features, including an integration preview. Describing a feature here does not mean it is publicly available. Contact the ShouldI team at support@shouldi.fyi about your information.

Coin flips and device storage

Coin tosses happen in your browser. Your question does not affect the random outcome. On-page questions, results and round statistics reset when you refresh; signed-in History is separate. We remember your selected coin on your device. An explicit page transfer or sign-in redirect may temporarily preserve your draft in session storage for up to 10 minutes so you can continue it.

Google sign-in

Google handles authentication; we do not receive your Google password. We use the verified Google account identifier for your account, session and credits, and may store the verified profile image URL for your avatar. We do not store Google access tokens, your Google name or email in your account profile. Loading the Google sign-in interface or avatar sends a request to Google.

AI questions and private history

An AI request sends your question, optional context and candidate answers to Cloudflare to run TypeSafe’s Jev model. Coin-only inputs are not sent to the AI service. Avoid including unnecessary sensitive information or another person’s private information.

While signed in, questions, context, choices, AI results and coin tosses are saved automatically to your private History. Anonymous activity is not imported when you sign in. Deleting a round or clearing History removes its question and result content. Limited account/round identifiers and deletion timestamps remain to prevent delayed saves from restoring deleted content. Credit and payment records are separate.

Trial protection and essential storage

Anonymous AI trials use a signed cookie, Cloudflare Turnstile, a FingerprintJS browser identifier and IP-based rate checks. Browser characteristics help produce the identifier; our server stores keyed digests and usage counters rather than the raw fingerprint attributes. A fingerprint is not proof of a unique person or machine. These checks limit repeated trials and abusive requests. Clearing cookies does not necessarily reset server-side usage records.

Credits, payments and operations

We store credit grants, reservations, usage, subscription status and transaction evidence for access, reconciliation, support and abuse prevention. The credit ledger uses a keyed request digest instead of your question text. Signed-in History separately contains your saved inputs and results.

When checkout is available, Waffo processes payment information. We retain order and payment references, amounts, status and verified provider event data needed to reconcile credits and subscriptions. Do not send card details in a question or support message. A checkout marked Test mode uses test payments.

Cloudflare hosts the site and server records and may process request information such as IP addresses for delivery and security. Budget and service-balance alerts may be sent to a restricted operator Feishu group; these alerts do not need your question or result content. If you email support, we process the message and information you provide to handle your request. Providers may process data in countries outside your own, under their respective service terms.

How long information is kept

Sign-in sessions expire after 30 days. Expired login and short-term rate-limit records are cleaned up periodically. The anonymous trial cookie lasts up to 400 days. Settled request digests are removed after 30 days during scheduled cleanup; unresolved requests keep evidence while under review.

Saved History remains until deleted or removed through eligible account closure. Trial counters, account identifiers and financial, refund and anti-abuse records are not deleted by clearing History or browser storage. These records currently have no general automatic deletion period. We assess retention and deletion requests against outstanding transactions, security needs and applicable obligations; we do not promise that closing an account erases every record. Provider logs and backups have their own retention practices.

Sharing and analytics

Share images are created in your browser. Your question is excluded unless you choose to include it; optional context is not included. Downloading an image does not publish it. If you share it with another service, that service’s privacy practices apply. Analytics is described below.

Microsoft Clarity analytics

On eligible public pages of shouldi.fyi, we use Microsoft Clarity to understand how the site is used, through usage statistics, heatmaps and masked session recordings. This can include clicks, scrolling, page layout, device/browser information and request information such as IP addresses. Microsoft processes this data for analytics and, as described in its privacy statement, to improve its products and services.

Clarity may use cookies and similar technologies to measure visits and interactions according to its configuration and applicable consent requirements. This version does not display an analytics consent prompt or send a consent choice on your behalf. Where consent is required and has not been provided, Clarity features may be limited.

We apply page-wide content masking and do not send custom account identifiers, questions or AI results as analytics events. Clarity is not loaded on local/test sites, History, authentication endpoints, unknown routes or visits with URL query parameters or fragments. Masking protects page content, not usage metadata. Read the Microsoft Privacy Statement and Clarity privacy information for provider practices and retention. Contact support@shouldi.fyi with privacy questions.

Your choices and requests

You can use the public coin tool without signing in, delete saved History, clear device storage or contact support@shouldi.fyi about access, correction, deletion or account closure. We may ask you to verify account ownership. Accounts with subscriptions, payment records or pending charges require review; contacting support is a request, not confirmation that deletion has happened.

We will update this notice when our practices change and revise the date above. Read our Terms of Service for credit, subscription and cancellation rules, or visit Help for practical guidance.