Privacy
What Amanikah stores, and what you control
Last updated 16 November 2026. This page describes the site as it works today — including waitlist mode and sandbox billing.
Server-stored requests
Waitlist, contact, and safety forms submit to Amanikah’s platform API. Accepted submissions receive a unique reference and are stored for operator review. Notifications are emailed when a transactional provider is configured; otherwise they remain in the operator outbox and are not silently discarded. Clearing browser data does not delete server records already accepted.
Production accounts
Accounts created at /account/register.html are stored in Amanikah’s member database after email verification. You can edit your private profile, withdraw consent, or delete your production account from your account. Deletion deactivates the account, clears the session, and replaces identifying profile fields. Operator audit records of the deletion action may remain.
Membership demo
Routes such as /register, /login, and /dashboard run in explicit DEMO MODE. Demo account data stays in this browser’s local storage. Demo records are never automatically migrated into production accounts.
Quiz and #SimpleNikah drafts
Nikah Priorities answers and most pledge drafts stay in this browser unless you consent to carry a sanitized referral into waitlist signup. Unlisted #SimpleNikah links are stored as preference-only payloads on the server. Revoking a link on the server makes the public page unavailable (HTTP 410). Downloads or copies already saved elsewhere cannot be recalled.
Voice introductions
Marketing-page and demo voice notes remain browser-only. When the authenticated Family Studio is enabled, a verified adult can separately choose to upload one private voice recording to server-managed media storage outside the public website directory. Recordings are accessible only to their owner and verified relatives who accept an invitation expressly granting voice access. Recordings can be replaced or deleted; account deletion and consent withdrawal also trigger private-media removal. Family member blocking and permission revocation immediately prevent future access. Access is not the same as a guarantee that recipients cannot record what they hear.
Voice upload stores the audio, its type, duration and upload time. We do not perform voice cloning or infer honesty, sincerity, religious observance or emotion. Voice Rishta is not a public member-discovery feature while matchmaking remains disabled. A precise backup-retention period for removed files remains an operational decision that must be published before broad launch.
Billing
Sandbox orders store a browser reference, the service name, the fee, and payment state. Card numbers are rejected and are not stored. Live card capture stays off until services are deliverable. A sandbox invoice is not a tax invoice and is not real revenue.
Categories of information (summary)
- Waitlist / tickets: name, email, city, preferences or message text, source/referral, timestamps — purpose: operator review and support/safety.
- Production accounts: email, password hash, profile fields you enter, consent flags — purpose: authenticated membership.
- Private Family Studio: invited registered-member identifiers, permission scopes, acceptance/revocation/block records and private voice media only when used — purpose: consent-controlled participation.
- AI Family Assistant: per-request topic, language and optional note only when you actively enable AI for that request; usage timestamps for rate limits.
- Demo membership: fictional local records only on your device.
- Share links: preference-only payloads for unlisted #SimpleNikah links.
- Sandbox billing: order metadata without card numbers.
- Funnel analytics: event names and non-private props (source, reference ids) — not matrimonial note or profile body text.
Operator decision still open: exact retention windows for waitlist notes, ticket bodies, and deletion audit rows should be confirmed before claiming a specific number of days.
Family tools and optional AI
The production Family Studio, when deployed, stores invitations, the limited fields you select for sharing, each recipients acceptance or decline, revocation and blocking state. Neither a family invitation nor payment gives anyone your private profile without your permission. Members may report abusive voice content for authorized human review.
Guided conversation questions work without an AI vendor. If an administrator enables AI and you individually opt in to a request, the selected discussion topic, language and optional note you type are sent to the configured OpenAI Responses API. Profile fields, identity documents, audio and other relatives data are not added automatically. Do not include another persons private details in an optional note. AI answers are advisory text, not religious rulings, suitability predictions or verified claims. Provider processing is governed by the providers applicable terms and privacy practices. If the API key is absent, the service gives a clear unavailable response instead of silently sending data elsewhere.
Analytics
Quiz and #SimpleNikah events may be stored locally. A network beacon is sent only if an analytics endpoint is configured and you have allowed analytics. Private matrimonial profile content is not sent to marketing analytics.
Fonts and pages
Loading a page requests that page, its stylesheet, its script, and images from this site. Typefaces load from Google Fonts.
Questions
Write on the contact page or use the safety report for urgent concerns. Account deletion and consent controls are on your account.