Privacy

Who operates the service and privacy contact

TalestoKeep.com is operated by Curry Walter, doing business as TalesToKeep. Mailing address: 51708 Kenai Spur Hwy, Nikiski, AK 99635, United States. For privacy questions or requests, email talestokeep@gmail.com with “Privacy Request” in the subject line. We may ask for information needed to verify your identity and locate your account; do not email story content or passwords.

What your archive contains

Your archive can contain profile details, memories, interview transcripts, story drafts and versions, people and places, family relationships, photographs and captions, records, uncertain details, and saved Life Book editions. Account, sharing, payment, and print features also use the information described below.

Stories and photographs may reveal sensitive information about you or other people. Include only material you have permission or another appropriate basis to use, and consider their privacy before sharing or printing it.

On your device

In device mode, archive content is kept in this browser’s storage. It is not automatically an account backup. Clearing site data, using a different browser, losing a device, or browser storage limits can make that copy unavailable.

Download archive and media backups from Account & backups and keep them somewhere private. A downloaded file is outside the app’s access controls.

In an account

When account services are configured, Supabase provides authentication and account-scoped cloud storage for archive content and media. The app keeps an offline copy associated with the signed-in account and syncs supported changes when connected.

Signing out locks that account copy in the app; it does not erase the copy stored on the device. Protect access to the device and browser, especially on a shared computer.

How information is used

The app processes information to operate your archive, save and sync changes, connect related memories and records, create exports and books, recover saved work, and protect account access. It keeps relevant version, usage, permission, payment, and order state to support those features.

Information is disclosed to providers when needed for a feature you choose: Supabase for configured account and cloud-storage services; OpenAI for optional AI and conversational voice; Stripe for payment and billing; and Lulu for requested printing and fulfillment. A selected edition is shared with the recipients you invite. Optional Google Analytics and Meta purchase measurement are separate choices described below. These services have their own privacy terms, linked on this page.

Optional AI and voice

When you choose AI drafting or an AI follow-up, relevant interview text is sent to OpenAI. Starting a conversational voice session sends microphone audio to OpenAI only after you accept the disclosure and explicitly start the session. Completed transcript text is saved in your archive; this app does not intentionally record or save the raw audio.

When you use guided book finishing, relevant book content and your book-finishing prompts, answers, and transcript text are sent to the configured AI provider to provide the requested guidance. The app retains confirmed transcript checkpoints, structured decisions, and quota and accounting records with your account so the same session can be resumed and usage can be reconciled. It does not intentionally retain raw microphone audio.

Browser dictation is a separate optional feature. Your browser may send microphone audio to its speech service; the app uses the returned text and does not save that audio in your archive.

Generated text and transcription can be wrong. Review them before using, sharing, or printing them. Story tools retain source transcripts and prior versions where indicated. Supported AI drafting requests disable provider response storage with store: false; this is not a promise of zero provider retention, and does not describe every voice or technical processing setting.

Sign-in information

Supabase handles email-and-password authentication and recovery. If you choose a configured social sign-in, that provider and Supabase process the sign-in, and your account profile may include your email, display name, avatar URL, and sign-in provider. Apple and Microsoft (Azure) sign-in are not currently available; enabling them requires provider credentials and settings in Supabase. Choosing social sign-in does not grant other people access to your archive.

Payments and membership

Configured commerce features use Stripe for hosted checkout, payments, subscriptions, tax calculation, and provider-hosted billing management. Stripe processes the payment and billing details you provide. The app keeps provider references and purchase, membership, credit, and payment state to reconcile what was purchased. It does not receive your full card number from Stripe Checkout.

Printing

Requested printer-proof preparation sends product and page-count information to Lulu for cover dimensions. When you request printer-file validation, Lulu receives access to the prepared interior and cover files. Requesting shipping options or a quote sends your delivery details, including the recipient’s name, address and phone number, and relevant product information.

A separately confirmed print order sends Lulu the approved files, delivery details, product selection, order references, and a contact email. The app retains proof, quote, payment, and order state for the workflow. Payment does not by itself submit a print order.

Book content, proof files, payment information, and shipping information are sent to the existing print, payment, and shipping providers only when you choose to proceed with proofing, shipping, or a print order. Guided conversation alone does not approve a proof, charge shipping, or submit a print order.

Sharing a selected edition

A shared edition contains the fixed selection of chapter prose, photographs, and captions you review for sharing. Access depends on invitations and recipient permissions; it does not expose the whole archive or automatically include raw transcripts, private record notes, or later edits.

Review the actual edition: privacy labels do not automatically remove personal details from prose. Recipients with suggestion permission can propose revisions for the storyteller to accept. Revoking access cannot recall material someone already read or saved.

Optional product analytics

When configured, Google Analytics loads only after you explicitly allow optional analytics. Google may use cookies or similar browser identifiers and receive device and browser category, and other standard consented Google Analytics technical data.

TalestoKeep sends four product and funnel event types: a start action, best-effort new-account activation, first memory begun, and first memory saved. These events use a fixed TalestoKeep.com site context (https://talestokeep.com/), a generic title and blank referrer, rather than the page you are viewing, and may include approved campaign source, medium, name, and content values. Search terms are not collected. Depending on the connected Google Analytics property’s settings, Google may also process standard technical or automatically collected event data. Event counts are best-effort; first-time activity is recognized within this browser and may be missed or counted again on another browser or after storage is cleared.

If you begin membership or additional hardcover-credit checkout while analytics is allowed and return to billing within 24 hours, the server verifies your payment with Stripe before the browser reports a purchase to Google Analytics. It includes the product category, quantity, currency, price after discounts, tax and shipping separately, and a deduplication identifier derived from the checkout. It uses the same fixed site context and approved campaign values above. No names, email addresses, raw account or payment-provider identifiers, or archive content are sent. Declining or withdrawing analytics consent prevents this reporting. Purchases may be missed if storage is unavailable, a tracker is blocked, payment is delayed, or you do not return; renewals, gifts, finishing services and shipping-only payments are not included. These counts are not a sales ledger or proof of printing or delivery, and do not automatically subtract later refunds.

App events do not include story text, names, photographs, interview answers, email addresses, raw account identifiers, archive scopes, private routes or queries, referrers, or archive contents. Meta Pixel is not included.

Declining does not change the features available to you. You can change your choice below. Withdrawing consent disables collection by an already loaded Google Analytics tracker.

Optional advertising measurement

When configured, a separate advertising choice lets you allow purchase measurement through Meta’s Conversions API. Optional Google Analytics consent does not grant this permission. Declining does not change your ability to use the app or buy a book credit.

After you consent, we store a random browser identifier and, when present on a public campaign page, a Facebook ad-click identifier for up to 90 days. If you start checkout while consent is active and return within 24 hours, the server verifies payment with Stripe before sending Meta the purchase time, amount including applicable tax, currency, a deduplication identifier, and whether you bought an annual membership or an additional hardcover credit. Meta also receives these browser identifiers and your browser’s user-agent information. The page context is always the public pricing URL; we do not send private pages, referrers, stories, photographs, names, email addresses, or raw account identifiers.

This measurement does not load Meta Pixel, read archive content, or report shipping payments, membership renewals, or print submissions as these purchases. Counts may miss purchases when consent is declined, storage is unavailable, payment is delayed, or the customer does not return. Purchase counts are not net revenue or proof of printing or delivery.

You can withdraw consent below. Withdrawal clears the advertising identifiers and pending checkout measurement in this browser and stops future reports; it cannot recall data already sent to Meta. Clearing browser data resets your choices.

Offline caching and technical requests

The service worker caches the app shell, supported public pages, and assets for offline use. It excludes private media, sharing, billing, and print API responses from that cache. Archive and media storage used by the app is separate from this page cache.

The manual Life Book keeps its existing offline shell behavior. Guided book finishing always requires a network connection and is never served from the page cache, so an offline browser cannot show a stale finishing session.

Hosting and service providers may process technical request information, including request logs, under their own policies and retention schedules.

Security, backups, and retention

The app uses account-scoped access controls and permission checks, but no system can promise absolute security or uninterrupted access. Keep your credentials, invitation links, exported books, and backups private.

Device-only archive data remains in your browser until you remove it. Account archive data is kept while the account is active and, after a verified deletion request, is deleted or de-identified unless needed for a legal obligation, transaction records, security, fraud prevention, dispute resolution, or another lawful purpose. We retain payment, tax, and order records as needed for legal and accounting obligations. Technical logs, backups, and information held by service providers follow the applicable provider retention and backup cycles; copies already exported, printed, or saved by recipients are outside our control. The 90-day limit for advertising identifiers and 24-hour attribution window described above are specific exceptions, not a general retention period.

Privacy rights and requests

Depending on where you live and which laws apply, you may have the right to request access to, correction of, deletion of, or a copy of personal information, to opt out of certain advertising disclosures, or to appeal a decision about a request. To make a request, email talestokeep@gmail.com with “Privacy Request” in the subject line. We will verify and respond within the time required by applicable law. You can also withdraw optional analytics or advertising-measurement consent using the controls on this page. We do not deny service or discriminate because you exercise a privacy right.

Provider privacy policies

These providers explain their own information handling:

• Supabase privacy policy
• Google privacy policy
• Apple privacy policy
• Microsoft privacy statement
• OpenAI privacy policy
• Stripe privacy policy
• Meta privacy policy
• Lulu privacy policy

Questions and updates

For privacy questions or requests, email talestokeep@gmail.com or write to the mailing address above. We may update this notice as the service changes; review the effective date above.

Gifts and personal finishing help

Gift buyers see purchase and redemption status, not the recipient’s stories or archive. Claim links are private bearer invitations; do not publish them. We retain a digest rather than the usable claim token. Gift messages composed on the gift page are not sent to us.

Finishing requests record the chosen edition, requested help, and contact window. An assigned assistant sees only the edition you explicitly share and can suggest changes; the permission ends when the service completes or is canceled, and you may revoke it earlier. Payment and service audit records support delivery and reconciliation. Existing access, export, deletion and legally required transaction-retention rules continue to apply.

Optional product analytics records only general start/request actions for these offers. Gift claims and new gift/service payments are not added to Meta advertising measurement.