Privacy Policy

1. What browser encryption protects

The complete saved biodata payload is encrypted with AES-256-GCM. This includes names, birth details, religion and community details, education, work, income, family information, contact details, written sections, optional fields, field-pack answers, and the biodata profile photo.

A random data key protects the payload. For a guest, that key is created automatically and kept only in the current browser tab, so no privacy passphrase is requested. Registered users use a separate privacy passphrase and recovery key so saved biodatas can be unlocked again later. Neither type of decryption key is submitted to our server.

2. Information we can still process

We retain the minimum operational information needed to run the service: account name and email for registered users, encrypted key envelopes for registered-user vaults, temporary guest identifiers, record identifiers, selected template, selected optional-pack identifiers, typography preferences, creation/update time, subscription and payment records, coupons or referrals, security logs, and basic device/request information used for fraud and abuse prevention.

Payment providers receive information necessary to process a payment. They do not receive your decrypted biodata from the privacy vault.

3. Admin access and support

Admin screens show operational metadata such as record ID, account, template, privacy state, and dates. They do not render encrypted biodata contents or biodata photos. Our support team cannot read, recover, correct, or export an encrypted biodata for you.

Existing records created before strict privacy are converted by their owner. During conversion, the browser encrypts the record first; readable database columns and the old uploaded photo are removed only after the encrypted payload is saved successfully.

5. Sharing and comparisons

Server-rendered public biodata links and WhatsApp profile links are disabled in strict privacy mode. Download the PDF after unlocking and share that file directly with people you choose. Server-side biodata comparisons are also disabled. Legacy manual comparison details are moved into encrypted owner-controlled payloads during privacy conversion.

6. Security limits

Browser encryption protects stored database contents from ordinary admin access and database disclosure. It cannot protect information after you unlock it from a compromised device, malicious browser extension, malware, someone with access to your unlocked screen, or a PDF you choose to share. Because the website supplies the browser code, no web service can promise protection from a malicious change to that code. We use access controls, code review, secure transport, and security headers to reduce these risks.

7. Retention, deletion, and legal requests

Guest biodata is temporary and is scheduled for deletion after 24 hours of inactivity. Opening the guest preview, editing, starting checkout, or completing payment refreshes this short window so the current output can finish. The browser-tab key is not recoverable after that tab session ends. Unpaid internal guest identifiers are removed when no temporary biodata or checkout record remains. A random pseudonymous linkage may remain with payment, fraud-prevention, accounting, dispute, backup, or legally required records, but it does not contain a readable copy of deleted biodata contents.

8. Contact and changes

We may update this policy when the service or law changes. Material changes will be communicated through the website or account email. Privacy questions can be sent to contact@biomatrimony.com.