Privacy policy
In short
- What we keep: your sign-in email and account ID, and what you choose to enter: memories, recipes, practices, dates, preferences, photos and recordings, including private unfinished drafts and selected photos or recordings kept so you can recover them.
- Who sees it: you. Others only if you create a share link, invite a relative to a memory, or add it to a shared family home. The operator and infrastructure providers may access records to run, support or secure the service; this is not end-to-end encryption.
- Who helps run it: Cloudflare (hosting, database, files and the sign-in gateway), Amazon Cognito (sign-in), Google (only if you sign in with Google), Resend (invitations and optional weekly emails; it gets email addresses, the invitation link and permission, and update counts, not your stories or media), Prokerala (only Panchanga you ask for: location, date and settings) and Cloudflare Workers AI (only recordings you choose to transcribe). Data may be processed outside your country.
- Your control: edit, back up or delete your records in the app. Trash keeps items for 30 days before cleanup; permanent deletion removes them from active storage.
- Questions or deletion requests: abhishek.shankar@gmail.com
The full policy below explains each feature in detail.
Personal story and recipe text has a separate private recovery slot per account, including unfinished fields, editing context and a retry identifier. Connected checkpoints use the existing private database. Device checkpoints use authenticated encryption with an account-specific key returned only while signed in; browser storage contains encrypted text and revision metadata, not the key. Recovery requires reconnecting and signing in, and is offered explicitly after current ownership and revision checks. Nothing is published or shared automatically, or included in backups, search, family updates or emails. Wait for private-save or device-save confirmation before leaving; edits before confirmation and cleared or evicted browser storage can still be lost. Recovery text has no automatic expiry. Discard and confirmed publication clear it; deleting all personal memories clears recovery text and rotates its key while retaining a revision tombstone against stale writes. This is not end-to-end encryption against the service operator. Photos and recordings use their separate recovery controls.
Offline family text edits now also checkpoint an encrypted copy on this browser: stories, replies, questions, profiles, recipes and traditions, up to 1 MB total. The decryption key stays in Satpatha’s private database and the signed-in page’s memory, not browser storage. After a crash, reconnect and sign in as the same account; current family/edit permissions and draft revisions are checked before recovery. Nothing is published automatically. Confirmed server saves or discard remove the matching device copy. Clearing site data, private-browsing expiry, device failure, storage limits, revoked access or a newer revision can prevent recovery. Wait for the device-save confirmation. This supersedes the earlier offline-text limitation, not the media limitations; it is not end-to-end encryption or an offline cold-launch guarantee. Encrypted abandoned device copies have no automatic expiry.
Personal-vault selected-media recovery keeps one separate private selection per signed-in account in the existing database, up to four photos/recordings and 1.5 MB including metadata, with a 50 MB service-wide cap for personal selections. It retains prepared media bytes, upload retry identifiers, unfinished-recording markers and, after a confirmed memory save, that memory’s ID. It does not retain unsaved title, story or recipe text. Explicit recovery opens the original active owned memory, or a blank new editor for selections made before a memory was saved. Nothing is published, attached, transcribed or shared automatically. The same confirmed-checkpoint and incomplete-audio limitations described below apply. Recovery is excluded from personal/shared backups, search, updates and emails, is not end-to-end encrypted and has no automatic expiry. Clear/discard and confirmed upload request cleanup; permanent deletion of its associated memory removes recovery, and personal-vault delete-all also removes unattached recovery. This extends recovery beyond the shared-home editor; previous shared-home-only limitations are superseded for personal media selection.
Selected shared-home photos and recordings have separate private recovery per account and saved memory, stored in the existing database, not browser storage. Photos are resized before recovery storage. Recovery is limited to 1.5 MB per memory (including metadata), 6 MB per account and 50 MB across the service; larger selections can still be uploaded explicitly but may not be recoverable. Active recordings attempt cumulative checkpoints about every five seconds when the browser emits audio data; the last seconds, offline or unconfirmed changes and some incomplete audio formats may not survive or play. Wait for confirmation and preview recovered audio. Only the same signed-in account with current permission to edit that memory can recover it. Nothing is attached, shared or transcribed automatically. Recovery bytes are excluded from family backups, search, updates and emails. Clearing the selection or confirmed upload requests cleanup; permanent memory/home deletion cascades recovery removal. Otherwise there is no automatic expiry. Revision markers prevent stale tabs from recreating discarded media. This recovery is not end-to-end encrypted.
Family questions and shared family profiles also have separate private draft slots per account/home. Question drafts retain the unfinished question and chosen audience. Profile drafts retain the name, family role, about text and original editing context. The same account/current-permission checks, explicit recovery/discard, confirmed-publication cleanup, no automatic expiry and exclusion from shared backups/search/updates/emails apply. Profile drafts do not verify identity or link a profile to a sign-in account.
Recipe and tradition drafts use the same private recovery protections as story drafts, but a separate slot per account and family home. This slot also stores unfinished ingredients, steps, notes, linked-memory IDs, recipe/tradition kind and version-group ID. Saving a version draft does not replace your story draft. Recovery, discard, current-access checks, no automatic expiry and exclusion from shared backups/search/updates/emails apply to both slots.
Effective October 27, 2026. Satpatha is operated by Abhishek Shankar. Contact abhishek.shankar@gmail.com for privacy, account or deletion requests.
Private family-story drafts: while connected, the story editor saves one current text draft per account and family home to Satpatha’s existing private database. It includes the title, text, reply or edit context, chosen audience and retry identifier, not photos or recordings. Draft recovery requires the same signed-in account and current contribution permissions; other relatives and family owners cannot retrieve your draft through the app. Drafts are not published automatically or included in shared backups, search, updates or emails. Recover or discard a draft in the editor. Publishing clears its recoverable text after confirmation; permanent home removal also removes drafts. Otherwise there is no automatic expiry. An empty revision marker remains after discard to prevent stale tabs from restoring deleted text. Wait for the saved confirmation before closing: offline or unconfirmed changes may not survive. Drafts are not end-to-end encrypted.
Optional weekly family emails are off until you opt in for your own verified sign-in email. We store your preference, email language, consent revision, summary cursor, attempt/delivery status and a random unsubscribe token that can only stop these emails. Resend receives your recipient email and counts of currently accessible new memories, replies, photos and recordings contributed by relatives, not family names, titles, text or media. The same free-only reservation limits and suppression list apply to invitations and summaries together. Summaries are attempted no more than once in seven days per account, with at most 40 due accounts checked each day; free limits can delay or prevent sending. Empty summaries are not sent. Ambiguous attempts are not automatically retried. Turning off or revoking access prevents future eligible dispatches, not an email already dispatched. Summaries do not mark updates as read. The email unsubscribe link does not require sign-in, does not change family membership and only acts after confirmation. Shared backups do not include email preferences. No one is automatically subscribed.
Shared-family recovery: removing a memory, reply, photo or recording moves it to private trash rather than deleting its bytes. Trashing a parent hides its replies and files too. Trash remains until an owner permanently removes it or the lead owner removes the home, and counts toward existing storage limits; there is no automatic expiry. Contributors can recover their own items only while their role and current audience allow it; owners manage all. Permanent removal cannot be undone and also removes the item’s saved history. The last 20 prior title/text versions per memory and 20 prior captions or reviewed transcripts per file are stored with replacement attribution and timestamps. History is limited to authorized contributors and owners and checked against both current and historical audiences. Recovery never restores membership or audience grants, and blocks stale changes or access wider than the saved version. Shared backups contain active records only, not trash or edit history. Profile, relationship and audience-setting changes do not have version history.
YouTube videos
Satpatha uses YouTube API Services to read public uploads and check whether they can be embedded. The hourly server refresh sends channel and video IDs to YouTube. It does not send your Satpatha identity, family records or viewing choices. After you agree to show YouTube videos, your browser requests thumbnails from YouTube. Tapping Play loads YouTube’s embedded player, which may show ads and receive connection or playback information under the Google Privacy Policy. Satpatha remembers your choice in this browser. Use “Hide YouTube videos on this browser” to withdraw it.
Information used by the service
Signing in supplies an account identifier and email address. If you choose Google, we request basic identity information, including your email and profile, to authenticate you through Amazon Cognito and Cloudflare Access. Satpatha does not request access to your Gmail, contacts or Google Drive.
Satpatha stores the information you choose to enter, such as family memories, recipes, practice records, dates, preferences, photos and recordings. Family and religious information can be sensitive; include only information you have permission to store.
Use and access
Selective family sharing: existing memories default to everyone in their home. New memories, questions and recipe versions can instead name accepted relatives. Owners always retain management and backup access; the memory’s original contributor keeps access while still a member. Replies, media, transcripts, search, updates and person-memory links use the parent memory’s audience and current membership. Widening a selected audience requires confirmation; changes cannot recall copies already viewed or saved. Accepted relatives’ sign-in emails are shown to contributors choosing an audience. Profiles and family relationships remain home-wide; do not put a restricted story into a public-to-home profile or a separate wider-audience memory.
Owner backups include selected memories but not audience account grants. Restoring preserves selected status as owners-only until relatives are explicitly chosen again. Older backups without audience status retain their original everyone-in-home behavior. Deleting a parent preserves the surviving replies’ audience rather than widening it. The selected audience is not end-to-end encryption against owners or the service operator.
Family conversations: replies to a memory, recipe or tradition share that home’s audience and existing contributor/owner permissions. Attached photos and recordings share the memory’s conversation. Replies are separately attributed and do not overwrite the original. They count toward the home’s story limit and appear in family updates, search, timelines and encrypted backups. Deleting the original retains replies as standalone records; removing a reply also removes its own files. No conversation email is sent automatically.
The family welcome stores your optional self-selected profile and whether you have finished the welcome, per account and home. This choice is private to you, does not verify identity or grant permissions, and is not included in family backups. You can remove the selection in the welcome controls. Deleting a profile clears its selection; permanently removing a home removes its welcome records.
Invitation emails: creating a family invitation sends its recipient email, your sign-in email, permission and invitation link to Resend when free sending is available. Memory titles, stories, photos and recordings are not sent in the email. Resend publishes a standard 30-day retention period for email content, metadata and delivery events. Sending is capped; if unavailable, you can copy the invitation link yourself. We keep request reservations and signed delivery-event identifiers for up to 32 days, cleaned on later activity, and hashed recipient suppression records to avoid sending again after a bounce, spam complaint or suppression. These hashes are pseudonymous, not anonymous. See Resend’s privacy policy.
Family invitations: you can grant a specific sign-in email viewer or editor access to one memory and its attachments, not your whole vault. We store that email, permission, invitation expiry and accepted account identifier to enforce access. Unaccepted invitation links expire after seven days; accepted access continues until the owner revokes it or the memory becomes unavailable. Editors may change the title and text, but cannot manage access or delete the memory. Revocation stops future authorized requests, not copies someone has already saved. Public share links are separate and must be revoked separately. Permanently deleting the memory removes its invitation records.
Shared family homes are separate from personal vaults. Only stories and files deliberately added to a home become available to its accepted members. Owners manage membership and all contributions; contributors manage their own contributions while they have that role; viewers can read. Sign-in email is shown as the author. Removing access or leaving does not remove previously shared contributions. Closing a home retains its records and membership; reopening restores non-revoked memberships. The owner can permanently remove a home and everyone’s contributions. Personal backup and personal-vault deletion do not include shared homes; use the home’s separate removal controls. Shared records are not accepted as religious knowledge. Home invitations use the same bounded free email provider, payload and manual fallback described above.
We use this information to sign you in, save and retrieve your records, provide features you request, and operate and secure the service. Saved records are associated with your authenticated account. If you create a share link, someone holding that link can access the shared memory until the link expires or is revoked. Service administration and infrastructure providers may require access to operate, support or secure the service.
Shared family profiles contain names, optional relationships and notes supplied by home members, not automatically inferred identities or sign-in accounts. Every accepted member can read them. Owners manage all profiles; contributors manage profiles they create and links on their own contributions. A story-to-person link includes its attachments; individual files may also be linked. Removing a profile removes its links, not stories or files. Profiles and links are included in the home’s separate encrypted backup and are restored with fresh IDs and no access grants.
Ask your family stores questions and explicitly linked replies inside the shared home under the same member permissions. Replies may include text, photos, recordings and reviewed transcripts. Questions and replies count toward the existing home limits and are included in encrypted home backups. Removing a question does not remove its replies. There are no automatic external question messages or reminders.
Since your last visit shows active stories, questions, replies, photos and recordings available in your shared home. Mark as read saves only your account-to-item read markers so they persist across devices. Other family members cannot see those markers. Existing items start unread; opening or editing an item does not automatically change read status. Markers are excluded from family backups and removed when their item or home is permanently deleted. No email summary is sent.
Our family story displays the existing shared home’s people, contributions and media by recorded sharing dates, with explicit person links and year filters. It does not infer event dates or relationships. Accepted members can prepare a printable book of their current filtered view, including saved transcripts and attribution; audio itself is not embedded in paper/PDF output. Preparation refreshes authorized home records, uses the same private file endpoints, and sends no content to a new provider. Printed and saved copies cannot be recalled after revocation; keep them private.
How we’re connected stores only family-supplied parent, partner and sibling connections between shared profiles, with certainty, optional notes, creator account and timestamps. All accepted home members can read them; owners manage all connections, contributors only their own, and viewers cannot change them. No ancestry or additional relationships are inferred. Uncertain connections remain labelled, and recorded-by-family is not independent verification. Removing a profile removes its connections; stories remain. Connections are included in the home’s encrypted backup, restored under the restoring owner with fresh profile references and no access grants. No new provider receives this information.
Shared traditions and recipes are family-authored story versions with ingredients or materials, steps, notes and explicit references to related home memories. Each version keeps its own author and existing home permissions, media and person links. They are optional testimony, not universal religious rules. They count toward existing story limits and are included in encrypted home backups. Restore remaps related memories to fresh IDs; deleted references remain unavailable. No new provider is used.
Family stewardship has one lead owner and up to four accepted co-owners. Co-owners can manage shared contributions, ordinary invitations and encrypted backups; only the lead can offer ownership, remove other co-owners, close or permanently delete the home. Stewardship offers to already accepted relatives store recipient and proposer emails, account identifiers, type, expiry and acceptance/cancellation timestamps. Offers appear inside the home, expire after seven days and grant nothing until the named signed-in relative accepts. An accepted transfer makes that relative lead and the former lead a co-owner in one transaction; other pending offers are canceled. The lead cannot leave or remove themselves without an accepted transfer. A co-owner may step down; any separate ordinary membership remains until separately revoked. There is no inactivity or death inference, new email service, paid upgrade or automatic succession. Backups never include ownership grants or offers.
Find in our family searches only the selected shared home’s active saved stories, structured recipes/traditions, profiles, photo captions and saved Hindi/English transcripts. It uses literal word matching and explicit people links, not generated answers, translation or new transcription. Contributor filters use story attribution for stories and their attachments; profiles have no contributor attribution. Search requests go in a private POST body, not the page URL, and the application does not save search history or a separate search index. Responses are not cached; home access is rechecked after reads and again before opening a result. Existing downloaded or previously displayed copies cannot be recalled. No new provider receives the content.
Infrastructure and browser storage
Cloudflare hosts the application, database, file storage and access gateway. Amazon Web Services provides Cognito authentication. Google processes sign-in when you select Google. These providers process connection and security information, such as IP addresses and authentication events, under their own terms and privacy policies. Data may be processed outside your country.
Authentication uses cookies. Satpatha also uses browser storage for preferences and local app state. Clearing browser storage does not by itself delete records saved to your account. Sign out when using a shared device.
Owners can separately download a password-encrypted backup of an active shared home’s stories, original attribution, photos, recordings and saved transcripts. Encryption and decryption happen in your browser; the password is not sent to Satpatha or stored by the app. Keep it separately: a forgotten backup password cannot be recovered. This protects downloaded backups, not the existing server-side family vault. Older unencrypted ZIP backups remain restorable and must still be kept safe. Hidden/deleted stories are excluded. Reopen a closed home before backing it up. Restore creates a new private home with fresh IDs and imported attribution, never memberships, permissions or invitation links. Files return to existing storage without external processing. An interrupted restore may leave a partial home; review its report and retain the original backup.
Your choices and deletion
Optional audio transcription: when you choose Transcribe, Satpatha sends only the selected recording to Cloudflare Workers AI for Hindi or English transcription. The generated text stays a preview until you choose to save it; the original recording is not changed. A saved transcript becomes the recording’s caption and is included in backups or memory share links you explicitly create. For shared family homes, only the owner or a contributor managing their own story can request and save transcription; saved text is readable by everyone with access to that home and is not part of personal backups. Shared and personal recordings use the same free-only provider and daily limits, with no paid fallback. Account identifiers and daily request counters enforce the free allowance; previous UTC-day counters are removed on a later transcription request. Provider processing is subject to Cloudflare’s terms and privacy policies.
Optional Panchanga: only after your explicit consent, Satpatha sends the coordinates, date, language and calculation settings you choose to Prokerala. Your account identity, birth details and family records are not sent. Responses are cached in server memory for up to one hour; inputs are not saved to your family account. Hashed account identifiers and request counters enforce daily limits and are removed on a later request after the day ends. The provider processes requests under its privacy policy and terms; infrastructure may also process connection metadata.
You can edit or delete records and revoke share links using the available app controls. Items moved to Trash can remain there for 30 days before cleanup; permanent deletion removes records from active app storage. Provider security logs and retained infrastructure copies can follow separate retention schedules. Contact us to request account deletion or help accessing or deleting your information. Revoking Google access stops future Google authorization but does not automatically remove existing Satpatha records.
Anonymous credit reservations (time and credit count only) enforce the shared rolling 32-day free allowance. Expired reservations are removed on a later fresh request; an anonymous legacy total marker is retained to prevent importing old usage twice.
Changes
We will update this page when the service’s data practices change. The effective date identifies the current version.