Updated October 25, 2026 · Version 2026-10-25.1 · Development preview

This notice describes the current build, not a future feature list. Real membership remains closed. The owner personally handles support, privacy and safety correspondence at support@haanni.com without additional staff or 24/7 coverage. The operator is Sukhjinder Sidhu, operating Haanni Dating App. Business mailing address: 6310 Shiplett Boulevard, Burke, VA 22015, United States. A complete rights-request and response process must be established before launch. The app is not represented as certified or approved by a government or privacy regulator.

1. Browser demo

Fictional demo edits, photos, preferences, likes, blocks, matches, messages, sample replies, reports and support requests stay in this browser’s local storage. No real member or staffed team receives them. Use sample details. Reset all demo data in Settings clears this application storage in that browser. Copies you export or store elsewhere remain under your control.

2. Account data

Email sign-in is provided by an external authentication service. It processes your email, password credentials and confirmation or recovery requests. Haanni derives a hashed account key from the verified sign-in identity. It stores your chosen name, date of birth, city, country, gender, self-declared Sikh Punjabi identity, relationship intention, bio, interests, profile answers, optional languages/values/timeline, opening questions, date drafts you save or send, photos, pause state, policy version, consent version and server-recorded acceptance times. It can also store preferences, likes, passes, blocks, unmatch records, messages, reports and support requests when available. The platform may separately process sign-in and technical request logs.

Haanni does not request a street address, exact GPS position, contacts, microphone or Social Security number. Optional live identity verification collects documents and selfies through Stripe’s hosted page, as explained below; never submit them in your profile or by email. Photo selection uses the device system picker. The current app does not use the microphone or collect precise GPS data. The native preview re-encodes selected profile pictures before uploading. Avoid including unnecessary sensitive details in photos, bios, messages or reports.

Owner email alerts

The owner can opt into general notices for new reports, support requests and full account-deletion requests. The verified owner sign-in email is shared with Resend through the existing email service. Notices contain a category and a sign-in link, not member names, account references, request text, photos, ID documents or credentials. Notices are limited to one per category per 10-minute window and are not emergency monitoring. Delivery records include the recipient, preference version, general message, provider reference, timestamps and delivery status. These are owner operational records, separate from the underlying member request, and are removed if the owner deletes that owner profile. Failed sends require retry review; receipt and review are distinct. The owner can disable notices in Review inbox → Email alerts.

Owner review records

The owner can review saved safety reports, support requests and full account-deletion requests in a private inbox. Review records contain the request reference, status, review times, reviewer reference and factual notes, with up to 50 recent review entries per request. Full deletion details can include the sign-in provider and its account identifier so the owner can remove the correct login. These records do not automatically send an email, remove a login identity or impose a moderation sanction. Review notes linked to a member’s submitted support requests or reports are removed with that member’s profile; full-deletion handling records remain separately to track and verify completion, subject to applicable privacy and preservation requests.

Support requests

If you email the owner, your email address, message, reference numbers and voluntarily supplied attachments are received in the designated Gmail mailbox, separately from the app database. The owner uses that correspondence to handle your request and necessary follow-up. Account deletion and the in-app export do not automatically erase or export that mailbox. Request removal or access to related correspondence by email, subject to identity checks and lawful retention exceptions. The owner has not configured an automatic mailbox retention period. Do not send passwords, ID documents, financial details or intimate images.

3. Sensitive data

Your Sikh identity and Punjabi community declaration may reveal religion or ethnic origin. Gender, partner preferences and messages may reveal intimate or other sensitive information. Before saving a private profile, a separate unchecked consent asks permission to store and use the sensitive profile details you submit to maintain eligibility, apply your chosen matching preferences, and show permitted profile information to eligible members after activation. Those purposes do not include advertising, data brokerage or identity-document processing.

Decline consent by not submitting a profile. Withdraw it using Settings → Delete Haanni account, which removes the profile and associated application records as described below. Pausing is not withdrawal. Live document and selfie checks have a separate, initially unchecked consent described below. Additional purposes require updated disclosures and any required consent. Profile is private while membership is pending.

4. Data use

Information supports the profile and features you request, age eligibility, preferences, authorized communications, blocks, safety records and account controls. Your date of birth, consent records and sign-in email are not included in member-facing profiles. After activation, eligible members may see your name, calculated age, city, country, self-declared community, gender, intentions, bio, interests, approved photos and optional public answers. Messages are available to authorized mutual-match participants. These controls do not prevent a recipient from taking a screenshot or retaining information already received.

The current discovery system applies explicit preferences and shared interests; it does not make a background-risk determination or guarantee compatibility. No invented compatibility percentage or automated eligibility based on inferred religion or ancestry is provided.

5. Data sharing

Private application records and photos use Cloudflare-backed storage through the Sites hosting platform. Authentication and hosting providers handle information needed to operate their services and may have their own policies for technical logs. Demo AI-generated portraits are served by Haanni’s hosting and do not depict real members. The owner personally manages support and safety correspondence, without additional staff, and may need access for authorized support, security and reported concerns. No continuous moderation or automated safety response is promised.

Information may need to be disclosed when legally required, to respond to valid legal process, or to address an immediate safety concern, subject to applicable safeguards. There is no claim that messages are end-to-end encrypted. The application has no advertising SDK, third-party analytics SDK or data-broker integration, and does not implement sale of profile information, targeted advertising or cross-context advertising sharing. Hosting/technical processing is distinct from displaying profiles to members.

6. Photo security

Uploaded profile photos are resized and re-encoded in the browser before application storage to strip source metadata. Profile-photo endpoints require authentication and authorization. Photo upload does not prove identity or age. Stripe Identity is configured for controlled testing. Signed live webhook delivery has passed; only the owner pilot may start live checks while launch review continues. Stripe compares the ID portrait with a captured selfie. This does not automatically approve or compare dating-profile photos. No criminal background checks are performed.

Access controls and private storage reduce risk but cannot make a service breach-proof. Protect your sign-in account and avoid sharing financial or unnecessary sensitive information. Security incidents require investigation and any notices required by applicable law; the owner manages the app personally and does not promise continuous coverage or a security certification that does not exist.

7. Data retention

Apart from the billing policy below, the preview currently has no automated inactivity purge or fixed retention schedule: records can remain until removed by you through supported controls or by the operator. The absence of a schedule is a launch gap, not permission to retain information forever. A public launch requires documented limits for profiles, messages, reports, consent records and provider backups, including legally required preservation exceptions.

Delete Haanni account removes your profile, uploaded application photos, preferences, verification record, associated interaction records and messages from application storage. Your own reports and support requests are deleted by that action. Reports submitted by someone else may retain information about you in their record. Provider logs/backups and copies already retained by recipients are separate and are not erased by this button. Exported files on your devices are not deleted. Do not rely on account deletion to preserve evidence you may later need.

8. Your rights

Use Profile to change editable details, Preferences to change discovery, Export my data for your saved records and Delete Haanni account for deletion. A birth-date correction requires support review. Depending on your location and which laws apply to the actual operator, additional rights may include confirmation of processing, access, correction, deletion, portability, withdrawing consent, limiting sensitive-data use, opting out of sale/sharing/targeted advertising, authorized-agent requests and appeals. Applicable laws may provide deadlines and exceptions; this notice does not reduce them or declare that every state law applies to every business.

Email support@haanni.com for access, correction, deletion, sensitive-consent withdrawal, authorized-agent requests or an appeal, including if you cannot sign in. Include only the details needed to identify your request; do not send passwords or government ID documents. In-app Contact / appeal saves a signed-in request but does not forward request details by email; owner alerts are optional: email its reference for review. The owner personally handles requests without additional staff or continuous monitoring. This does not extend any applicable legal deadline. Proportionate identity/agent verification, response tracking, appeals and non-retaliation procedures still need to be completed for launch. No one is charged a fee by this preview for its self-service privacy controls.

Privacy requests

Email the owner with the right you want to exercise, enough account information to locate the record, and an existing reference if available. You may ask an authorized representative to contact the owner; authorization and proportionate identity checks may be needed. Do not provide another person’s account credentials. If a request is declined, you may reply with “Privacy appeal” and explain why you disagree. Applicable law determines required reasons, response deadlines, extensions and regulator complaint information. Owner-only operation does not extend those deadlines. No account is needed to send an email, and you need not agree to marketing to request privacy help.

The app currently implements no sale of personal data, targeted advertising or cross-context advertising sharing. It has no automated Global Privacy Control processing mechanism; this does not represent an implementation of statutory opt-out controls. Before any new advertising or data-sharing use, the operator must assess the required opt-outs, notices, browser signals and consent. No state-specific privacy certification or universal exemption is claimed.

9. Children & transfers

Haanni is for adults aged 18 or over; do not submit a child’s profile or permit a child to use an account. Suspected minors and child-safety concerns should be reported without reproducing illegal material. The adult-only label does not remove any legal duty if the operator learns it has a child’s data.

Worldwide community design is not a claim of worldwide legal clearance. Hosting may involve processing outside your home country. Before real membership is offered in a region, the operator must identify applicable privacy duties and transfer safeguards, including any required additional notices. These terms are not blanket consent to unrestricted international transfers.

10. Cookies & contact

The app uses local storage for its demo; platform sign-in and hosting may use essential cookies. The app adds no marketing tracker. Adding advertising, analytics or other optional processing requires updated disclosures and any required controls; a banner alone would not establish compliance. Material updates carry a new version and appropriate notice/consent. Contact the owner at support@haanni.com. Operator: Sukhjinder Sidhu, operating Haanni Dating App. Business mailing address: 6310 Shiplett Boulevard, Burke, VA 22015, United States. Use sample information during this development preview.

ID & selfie checks

Current status: Live Stripe Identity is limited to an owner-only pilot with separate consent. Other members cannot start live checks. Real membership and live payments remain closed. Use fictional information in sandbox checks; never upload a real ID there.

When enabled, Haanni uses Stripe Identity to check that your government ID is valid, that its portrait matches your captured selfie, and that the legal name and date of birth match your saved profile and the 18+ requirement. Stripe performs automated document and facial matching. A mismatch needs review; a successful check does not establish religion, ancestry, character, criminal history or safety.

Stripe receives the document images, document number and extracted details, facial images, and device and fraud signals needed for its verification service. Depending on the document and flow, these can include name, date of birth, address and other identifying details. Stripe processes facial features to compare your selfie with the ID photo. Read Stripe’s privacy policy and the notices presented in its verification flow. Any optional permission Stripe requests to improve its technology is separate from Haanni’s consent.

Haanni sends Stripe a private hashed account reference and verification settings. It retrieves verification outcomes and legal name and date of birth for comparison. Application records retain a Stripe session reference, consent version and time, checks, status, timestamps and a hashed binding to your saved name and birth date. Haanni does not copy Stripe’s ID images, ID numbers or facial templates into its application storage or show them to other members. The owner’s authorized Stripe dashboard access can expose verification details for support and review.

Choice & review

Before a live check, you must separately agree to document and selfie processing, including facial matching. You can decline and use the fictional demo. Email support@haanni.com to request a correction, review or a verification option without facial matching. An alternative is not currently automated or guaranteed available; the owner must arrange an appropriate process before requiring biometric checks in a region where an alternative is required. Do not email ID documents. You will not be activated while required eligibility checks are unresolved.

Verification retention & deletion

Haanni keeps verification references, consent receipts, hashes and outcomes with your account until account deletion or an applicable retention restriction. No automatic inactivity purge is currently configured. Stripe retains verification data on Haanni’s behalf until redaction is requested; the current integration does not automatically redact it immediately after a successful check. This retention arrangement must be reviewed for each launch region before enabling collection.

Delete Haanni account requests Stripe redaction before removing the application’s live verification record. Stripe redaction is asynchronous. If verification is still processing or Stripe cannot confirm the redaction request, deletion stops and tells you to retry or contact support; do not assume deletion completed. You may also email support to request access, consent withdrawal or redaction. Stripe may retain information for its own purposes or legal obligations under its privacy policy; contact Stripe support about those separate records and any optional technology-improvement consent. Removing a profile photo alone does not delete Stripe verification data.

Billing

Owner-pilot billing disclosure updated October 26, 2026 · Version haanni-live-billing-2026-10-26.3. Public paid membership remains closed. Live owner checkout is available only when the approved owner-pilot setting and readiness checks are enabled. If separately activated, Stripe hosts the US$1/month owner-pilot payment form and billing portal. A separate monthly-renewal agreement is required. Haanni does not collect or store full card numbers or card security codes.

Haanni sends Stripe a private hashed account reference and the fixed membership price. It does not include your profile photos, ID images, community declaration, birth date, biography or messages as billing metadata. Stripe processes the payment and billing details entered directly in its forms under Stripe's Privacy Policy.

Haanni stores provider customer, checkout and subscription references; the price and billing period; subscription, payment-confirmation and cancellation states; renewal-consent version and timestamp; and event/reconciliation references and timestamps. These records support membership eligibility, cancellation, dispute handling and reconciliation. Account export includes the live subscription state, live billing account record and retained billing evidence.

Account deletion removes the active membership record after provider cancellation checks; a separate essential billing archive and renewal-consent evidence survive profile deletion for the retention period. Provider customer references, consent receipts, event records and reconciliation or hold records can remain separately, and Stripe maintains its own records. Haanni retains essential billing and renewal-consent evidence for 10 years after the latest of the end of the subscription or billing relationship, the relevant billing activity, and the relevant tax return due date or actual filing date. This is Haanni’s chosen retention policy, not a statement that Virginia requires every billing record to be kept for 10 years. An audit, dispute, court order, unfiled return, or other applicable preservation duty may require longer retention. Billing disputes place the app’s retained evidence on hold until reviewed. Email support@haanni.com to request access, correction or deletion; requests require identity checks and consideration of applicable recordkeeping and preservation duties. Do not send payment credentials with a request. The owner reviews records for secure deletion after the retention period. The app does not run an automatic scheduled purge: its owner-only cleanup requires completed filing-date review, a closed billing relationship, expiry of the 10-year period and no preservation hold. Stripe’s separate retention is governed by its own obligations and policies. This billing policy does not extend the retention of profiles, messages, photos or identity documents.

Public first name and name corrections

Your public profile uses your saved first name, not a separate nickname or custom display name. Only members who meet the live identity, photo and payment requirements enter real discovery. Live verification compares your saved legal names with the provider result. After a successful live name match, Haanni records a private verification lock and prevents ordinary edits to the legal-name fields. This lock is included in your export and removed with profile deletion. A misspelling can be reported through Request a name correction; describe the correction without uploading or emailing identity documents. The owner must review the existing verification record or arrange secure re-verification before changing verified details. A support request alone does not change your verified name.

Sign-in security

Haanni uses its own dedicated Supabase authentication project, separate from Sidhu Market. Supabase processes your email, password and selected sign-in provider identity to authenticate you and send confirmation or recovery messages. Passwords are handled by the authentication service; Haanni does not store plaintext passwords. Essential access and refresh cookies are Secure, HttpOnly and SameSite=Lax; a short-lived PKCE cookie binds confirmation and social sign-in to the browser that started the flow. A hashed-token revocation record is stored in the app’s private storage. No login token is stored in browser local storage.

Social sign-in options are only active after the provider is configured. Signing in does not establish age, religion, ancestry or government-ID verification, and does not activate a subscription. Platform and email/social accounts are separate identities in this build; an identical email address does not automatically merge their profiles.

In web Settings, Deactivate profile hides discovery and pauses member interactions while preserving profile data; it does not cancel billing or withdraw consent. Delete profile and sign out permanently removes app profile, photos and interaction data and signs out the current browser session. The separate login remains, so you can sign in with the same email to create a fresh profile. Request full account deletion is available in web and native Settings. It removes application profile data, revokes recorded sessions and blocks sign-in while the owner completes removal of the managed login identity. Keep the request reference and email support@haanni.com for progress; a request is not completed login deletion. Provider records and essential billing records remain subject to the retention and preservation limits described here. Signing out revokes the current app session. Password recovery invalidates existing Haanni email/social app sessions after a successful change.

Native mobile preview

The native iOS and Android preview stores sign-in and refresh tokens in device-protected storage (iOS Keychain or Android encrypted storage), separate from fictional demo progress. The browser uses secure HttpOnly cookies. No real account tokens are written to ordinary local storage. Fictional demo likes, filters and sample conversations are saved locally; native demo profile edits and selected photos last for the app session. This demo is for fictional test information.

Both web Settings and native Settings provide Request full account deletion. On confirmation, application profile data is removed and a private request records the hashed account key, provider user identifier, reference, request time and status so the owner can remove the separate authentication identity. Identity deletion remains manual and is not complete merely because a request was accepted. The app revokes its recorded sessions when this request is submitted. The owner must complete the authentication deletion, confirm the result and apply lawful retention exceptions. Requests are saved in the owner inbox. Optional general owner alerts do not include request details or confirm review.

Notifications currently refresh only while the app is open. No push token, advertising identifier or contact list is collected by the current native preview. Store privacy declarations must be updated if these features change.

Web payment testing

The checkout demo uses a fixed fictional card ending 4242 and stores only a simulated subscription state in your browser. It does not collect a card number or contact a payment provider. The optional Stripe sandbox checkout sends a private hashed account reference and the selected test membership price to Stripe. It does not send your community declaration, date of birth, profile photos, bio or messages. Stripe hosts the test card form and processes the payment information you enter there. Use Stripe test payment data only; public live charges remain disabled; any owner-only paid pilot is separate and requires express payment consent.

For connected Stripe testing, Haanni stores test customer, checkout and subscription identifiers, the price/period, confirmation and cancellation states, webhook event references and renewal-consent time. Full card numbers and security codes are not accepted or stored by Haanni. These test billing records may remain after profile deletion to reconcile cancelled subscriptions and provide a request reference. They are not evidence that real payment or live membership occurred. Account export includes the test subscription state. Before any live billing is enabled, the owner must publish current payment-provider, retention, cancellation and refund information and verify the live integration.

Live photo-review pilot

After live ID checks pass, the owner can separately submit their current profile photos for a manual review alongside the Stripe verification record. Haanni records the photo-set fingerprint, session reference, submission consent time, revision, decision, reason and reviewer. This pilot explicitly records a review of the owner’s own account; it is not an independent review or automated face comparison. These records are included in account export and removed with the application profile. A photo change invalidates the prior photo approval. Live pilot updates are in-app only; no live-review approval email or text is currently sent. Approval does not activate paid membership.

Prepared live billing

Owner-only checkout requires completed payment setup, published billing disclosures and separate owner-pilot activation. When an owner-only paid pilot is enabled, Stripe hosts checkout and receives a private hashed account reference, the fixed membership price and the payment/contact details you enter on Stripe. Haanni stores customer, checkout and subscription references, price, billing period, payment and cancellation status, webhook references and the separate monthly-renewal consent receipt. It does not send your religion, birth date, profile photos, ID images, bio or messages in payment metadata, and does not store full card numbers or security codes.

Only a validated signed live payment event and current identity/photo eligibility can activate membership. Returning from checkout alone cannot activate it. Profile deletion checks for and cancels live subscriptions before removing application profile data. Minimal provider customer references and event records may remain to reconcile later payment events and handle support; no fixed automated financial-record purge is configured yet. Contact support for billing data access or deletion, subject to applicable retention obligations. Stripe may retain payment records under its own privacy policy. Live billing requires the operator’s current legal identity/contact details, applicable tax assessment, refund/cancellation disclosures and verified delivery before it can be enabled.

Account-deletion confirmation email

For full account deletion, the verified registered email is temporarily retained to send a completion receipt through Resend after the owner records removal of the separate login. The receipt confirms removal, explains retained billing records and includes the request reference; it contains no profile photos, messages or ID details. The address and queued message are cleared after the email provider accepts the receipt. Unsent addresses expire after 30 days and are cleared when the request or delivery record is next accessed; there is no scheduled cleanup. Minimal completion and email delivery status remain with the deletion request. Email delivery is not guaranteed. For an older request without a saved address, the owner must check the registered email against the original login record before sending.

Profile-only deletion email

After successful profile-only deletion, a transactional confirmation is sent through Resend to your verified registered email. It explains that your profile is no longer discoverable and that your login remains available for a fresh profile. Email preferences for optional review updates do not disable this requested transaction receipt. No name, photos, messages or ID details are included. The recipient and queued message are removed after provider acceptance. Unsent contact data expires after 23 hours and is cleared when its delivery record is next accessed; cleanup is not scheduled. Minimal delivery status remains until replaced by another profile-deletion receipt or removed on full-account deletion. You can check delivery or retry a failed receipt after signing in under Settings. Email delivery is not guaranteed.

Deactivation confirmation email

When you deactivate a saved profile, a transactional confirmation is sent through Resend to your verified registered email. It explains that discovery and messaging are paused, saved profile data remains, and reactivation is available subject to current requirements. It also explains that deactivation does not cancel subscriptions. Optional review-email preferences do not disable this receipt. No profile or ID details are included. Recipient and queued message are cleared after provider acceptance; unsent contact data expires after 23 hours and is cleared on next access, without scheduled cleanup. The latest minimal delivery record remains until replaced by another deactivation or removed with profile deletion. Reactivating cancels unsent receipts. You can check delivery or retry a failed receipt in Settings. Delivery is not guaranteed.