Your stories. Your information.

01 / WHAT WE SAVE

The information behind your profile.

The current service saves a salted password hash when login is set up, login-session records, short-lived failed-login attempt counters, your signup name, email, phone number, story content and activity, buddy voice preference and name, account access credential, hashed password-reset credentials, queued recovery-email metadata, subscription/request status, and signup time. It also records the terms version you accept, when you accept it, story review decisions and reasons, and host queue notes.

We also store guide preferences, review-notification history and read state, and queued review-email delivery metadata. When Stripe billing is enabled, we store customer, checkout and subscription identifiers, confirmation-event IDs, and checkout retry metadata. Billing dates, card summaries and invoice links are retrieved from Stripe. The site’s application database does not store payment-card numbers. Hosting and payment providers may process technical or transaction information under their own practices.

02 / HOW IT’S USED

To run your account and review stories.

We use this information to maintain your profile, save your preferences, review whether stories fit the service, manage subscriptions, and respond to support requests. Hosts can access submitted stories and account details for review and administration.

Email login uses a browser cookie containing a random login-session credential; the server stores a hash of that credential. Logging out revokes that session. Existing private profile links remain access credentials and may be saved in browser local storage to help existing users set up login. Anyone with a private link can use the profile. Logging out or clearing browser storage does not delete server records or invalidate your original private link. Changing or resetting a password, or confirming a new login email, invalidates old private links. Settings also record verified contact values and pending email/phone verification metadata.

03 / OTHER SERVICES

What happens beyond this site.

When enabled, Stripe handles checkout and subscription payments and receives information needed for those functions, including your email. When verification delivery is configured, the email provider receives destination addresses and verification/security messages and story-review notices stating the approval or decline status and, for declined stories, the review reason, for verified addresses; a connected text provider receives the phone number and verification request. Pages load the typeface from Google Fonts. Opening a call-room link connects you to the configured room provider, which may receive connection information and anything you share in that room.

Planned AI story review: when enabled, an AI provider will receive the submitted story's title, text, and selected activity to check whether the story fits that activity. The provider will return a category assessment and a short explanation that Tell ’Em uses to approve, reject, or refer the story for human review. Story text includes any personal information you choose to put in it. Category review does not verify whether a story is true. AI story review is not yet enabled in the current application; stories are currently reviewed by a host.

The current application does not implement AI calling or send your story library to an AI voice service. Before enabling AI review or calling, we will update this notice with the selected providers and applicable data-handling details. Do not submit sensitive personal information or private details about others that are unnecessary for your story.

04 / YOUR CHOICES

Edit, remove, or ask for help.

You can edit or delete individual stories in your profile. Cancelling a subscription retains your profile and saved settings so you can continue editing. To request deletion of your account or other personal information, contact support; ownership verification may be required.

There is no automatic account-deletion tool or fixed backup-deletion timetable in the current build. Subscription cancellation and clearing browser storage do not erase server records. Information required for legal obligations or payment records may need separate handling.

This notice describes the current application. Contact support about privacy questions, access concerns, or requests concerning your information.