Privacy Policy

Last updated: October 23, 2026

Language: This document is provided in both English and Bengali (বাংলা) for accessibility. In the event of any conflict, ambiguity, or discrepancy between the two versions, the English version shall control.

Introduction

Panosia Connect (“we,” “our,” or “us”) is a trust-first community for marriage introductions, with a marketplace for wedding and family services. It is operated by Panosia LLC. This Privacy Policy explains what personal information we collect, how we use and share it, and the choices you have. It applies to all users of connect.panosia.com and our related services.

Matrimonial profiles contain sensitive personal information — religion, family background, photos, and more. Service listings and booking requests can also hold personal details, such as your name, contact details, address and event dates. We take that responsibility seriously. We collect only what we need, give you granular control over your own data, and never sell your information to third parties.

By creating an account or using our platform, you agree to the practices described in this policy. If you have questions, contact us at connect@panosia.com.

Information We Collect

Profile Information

Information you provide when creating or updating your matrimonial profile:

• Personal details: name, date of birth, gender, location
• Contact information: email address, phone number, city, state, country
• Personal background: religion, nationality, height, marital status, mother tongue, languages
• Professional and educational background
• Family details, interests, and personal description
• Photos: profile photo, cover photo, and gallery images
• Candidate status (whether you are actively seeking a marriage partner)
• Verification references you list, and how each one is related to you (for example, family member or employer). The relation is shown next to that reference on your profile.

Note: Religion, ethnicity, and health-related information are classified as special category (sensitive) personal data under GDPR and equivalent laws. We process them only with your explicit consent, given when you choose to enter this information.

Account & Settings

• Authentication credentials and login information
• Field-level privacy settings for each profile field
• Platform role assignments (matchmaker, verifier, manager, admin)
• Notification and theme preferences

Network & Sharing Activity

• Connection requests and access permissions you have granted or received
• Community matchmaker introductions you have made or received
• Biodata PDF exports and network sharing activity
• Peer vouching and endorsements

Direct Messages

Panosia Connect offers two ways to message another member, both gated on having an approved ID verification:

• In-app chat: Available only between two members who have both completed approved ID verification. We collect and store the content, sender, and timestamps of messages sent through chat, along with read status for each conversation. Messages are visible only to you and the other participant in that conversation — not to community matchmakers, verifiers, or other members. See Retention Periods below for how long chat messages are kept, and our Safety & Trust page for how an open safety report can affect message deletion.
• One-time message relay: A single message you send is delivered to the recipient by email. It does not create a stored, ongoing conversation on our platform.

Services Marketplace

If you offer or book a service (such as a photographer, venue, caterer, or officiant) through Panosia Connect, we collect:

• Listings you create: title, description, categories, photos, the items you offer (with their photos, descriptions, units and prices) and how you group them, service area and the cities you serve, links, availability, and, for in-person services, an exact meeting address.
• Bookings: the requests you send or receive, the items and quantities in them (with a copy of each item's name, unit, price and photo as it was when requested), the dates and times, whether you chose pickup or delivery and the delivery fee, any notes and answers to a provider's booking questions, the notes you and the other person keep on a booking (we also keep earlier saved versions of each note for 90 days after the booking ends, longer if the booking is under a report) and any agreements either of you adds to the booking's history, price offers, reschedules, cancellations, and completion or no-show records.
• Reviews: the rating and review a seeker leaves after a completed booking.
• Peer feedback: after a completed booking, a provider can privately answer whether they would work with the seeker again, optionally choosing tags such as being on time, clear communication or respectful. A provider can also skip the question; a skip records only that the provider answered, and is not counted or treated as an opinion. Once given, an answer cannot be changed. Either person can also write a short, optional recommendation about the other, which is shown only if the person written about approves it; we notify that person in the app when one is waiting. We also keep your choice of whether to share your "would work with again" summary with providers.
• Listing claims: if you ask to claim a "Listed by Panosia" listing, the business email, phone number, WhatsApp number, website, and note you give us as proof. Our team receives these details, including by email at our support address, to verify your claim.

Published listings, including their title, description, prices and photos, your public name and ID-verified status, can be found by search engines and may appear in search results and AI answer tools. Copies may remain in their caches for a while after you unpublish a listing; we cannot control that.

Booking notes and answers may include personal details you choose to share, including sensitive ones such as religious practice. You control what you write. Please do not put medical or mental-health details in a booking. The provider who receives your booking details is responsible for how they use them, and you are responsible for having the right to share any information about a child.

"Listed by Panosia" Business Listings

To help members find services while local businesses join, our team may create a listing for a business or independent provider who has not joined Panosia Connect yet, using information the business has made public, such as its own website. These listings are marked "Listed by Panosia" and cannot be booked. If your business has been listed and you want the information corrected or removed, contact connect@panosia.com and we will act on your request. If you claim the listing and we approve the claim, it becomes part of your own account and is handled like any other listing under this policy.

Verification Information

• Self-service ID verification: Your government ID and selfie are sent directly to our verification vendor (Didit) for document authenticity, liveness, and face-match checks. We receive only the vendor's decision summary and four details read from your document: your name, date of birth, gender and country. When Didit's check passes, we use them to fill in any empty fields of your profile, and our team then reviews your ID. We never overwrite what you entered, you can edit your profile at any time, and our verification team can see the details next to your profile when reviewing and may ask you about differences. We do not keep your document number or address. The document images and biometric identifiers (facial geometry) are never stored on our servers and are processed solely by Didit under their privacy policy.
• Camera and microphone: If you allow it, the app or your browser uses your camera when you take a profile photo or selfie, and for the self-service ID check (photo ID, selfie and face scan). The ID check runs on Didit's page, which may also ask for your microphone. We don't record or keep a live camera or microphone feed; we keep only the photos you choose to upload.
• Digital background check: Supporting documents you submit for education and employment verification.
• In-person verification: Available on request. If you ask for it, we collect the contact details and city you give us so we can arrange the check. The verifier only confirms who you are; we do not publish personal identity details from a verification, and a verification report shows the result only.
• Payment records for verification services: transaction amount, status, and Stripe reference — never your full card details.

Safety & Moderation

• Reports you submit about another member, including any supporting evidence you choose to provide
• Members you block, and when you blocked them. Your block list isn't visible to other members, and our team can see it when needed to investigate a report or provide support. We use it to stop contact between you and the members you block; we don't tell a member that you blocked them, though they may notice they can no longer contact you
• Reports submitted about you by other members, and the resulting review outcome
• Account status history (for example, active, restricted, or suspended) and the reason recorded for any such change
• Listings you submit, which our team reviews, and the reports and claims filed about them. We may email the contents of a report or claim to our own team to act on it

Cookies & Browser Storage

We use minimal, essential browser storage to operate the platform:

• Session cookies: Issued by Supabase to maintain your authenticated session. These are strictly necessary and cannot be disabled without logging you out.
• Local and session storage: Used to remember your theme (light/dark), language and AI consent choices, whether you dismissed the app-install prompt, a referral code if you arrived through a referral link (sent to us when you sign up), your service-booking cart and pending actions such as a shortlist you started while signed out, and what you told us brought you to Panosia Connect (kept on your device and used only to open the right page after setup). A one-time flag also stops us from reapplying your city to the Services search more than once per visit. None of this is profile data; apart from the referral code, none of it is sent to us.
• Service worker cache: Your browser may cache profile images and static assets for performance. No personal data is written to this cache beyond what you have already chosen to make visible.
• Push notification service worker: If you enable push notifications, your browser registers a separate service worker — provided by our push notification vendor, OneSignal, and independent of the caching service worker above — and stores your subscription status locally. This is installed only if you opt in, and is removed if you disable push notifications or deny/revoke browser notification permission.

We do not use advertising cookies, tracking pixels, or any third-party cookies. Our analytics provider (Umami) is cookieless — it does not place any cookie or persistent identifier in your browser.

Do Not Track: We respect the Do Not Track (DNT) browser signal. Since we do not use cross-site tracking, DNT has no practical effect on our data collection but we honour the spirit of the signal.

Technical & Usage Data

• IP address, device type, browser, and session identifiers
• Pages visited, features used, and interaction patterns (via Umami; see Third-Party Service Providers below)
• Performance and error logs used to maintain service reliability

How We Use Your Information

We use your information only for purposes consistent with this policy:

• Providing the platform: Creating and displaying your profile, enabling discovery, managing connections, and facilitating community matchmaking introductions. Every member who has finished setup can appear in Discover, whatever their role (candidate, connector, or someone using the platform for services), whether or not they have verified their ID. You can hide your profile from Discover at any time with the "Hide from Discover" setting in Settings.
• Privacy controls: Enforcing the field-level privacy settings you choose so your information is shared only as you intend.
• Verification services: Processing identity and background verification requests when you initiate them.
• Biodata generation: Producing PDF biodata documents for traditional family sharing.
• Services marketplace: Showing listings, handling booking requests between providers and seekers, notifying both people when a booking changes, showing reviews and a provider's reliability record (see below), and reviewing listing claims.
• Communications: Sending transactional emails (verification status, access requests, account status, service booking updates, listing review decisions, and moderation notifications), in-platform notifications, and — if you opt in — push notifications in your browser or in our iOS app for the same categories of events. We do not send marketing or promotional emails or push notifications unless you explicitly opt in. You may unsubscribe from non-essential notifications, or disable push notifications entirely, at any time via your account settings.
• Safety & trust: Detecting fraud, investigating reports, moderating content, and enforcing our Terms of Service.
• Service improvement: Analysing usage patterns, mostly in aggregate, to improve features. Our analytics are pseudonymous (see Umami Analytics below); our team matches them to an account only for support and moderation.
• Legal compliance: Meeting our obligations under applicable law.

Automated Decision-Making

We do not make any automated decisions — including profiling — that produce legal or similarly significant effects on you. Discovery and search results are ranked by relevance filters you configure (gender, location, etc.), not by any AI scoring of compatibility or suitability. No automated system decides whether you can access the platform or interact with other users. For the self-service ID check, Didit's automated result is a recommendation only: a member of our team reviews every check before your verification is approved or rejected. When Didit's check passes, we also use the details read from your ID to fill in any empty profile fields; this does not change your verification status, and you can edit those fields at any time. If we ever allow an automated result to decide on its own, we will update this policy before doing so, and you will be able to ask for a person to review the decision.

Legal Basis (GDPR)

We process personal data on the following legal bases:

• Contract performance (Article 6(1)(b)): Operating your account, providing discovery, verification, biodata, and Services marketplace features.
• Legitimate interests (Article 6(1)(f)): Platform safety, fraud detection, pseudonymous usage analytics, sending transactional notifications, and showing "Listed by Panosia" business listings compiled from information the business has made public.
• Consent (Article 6(1)(a) and Article 9(2)(a)): Processing special category data (religion, ethnicity, health information), including religious practice you choose to put in a service booking (for example a halal or women-only request), and AI biodata import. You may withdraw consent at any time.
• Explicit consent for biometric data (Article 9(2)(a)): The self-service ID check uses your selfie for face matching, which is biometric data. You agree to it when you start the check. If you don't want that, you can verify by video call with our team instead, which uses no biometric matching.
• Legal obligation (Article 6(1)(c)): Complying with court orders, legal process, and regulatory requirements.

Information Sharing and Disclosure

We do not sell, rent, or trade your personal information. We share data only in the circumstances described below.

Within the Platform

What other users see depends entirely on the privacy settings you configure:

• Public fields are visible to registered users and appear in discovery. A limited, anonymous selection of public fields can also appear to visitors who are not signed in, as described in Anonymous preview on our public pages below.
• Privately shared fields are visible only to users whose access requests you have accepted.
• Hidden fields are visible only to you.
• Exception — your name: Your first and last name are the one field where "Privately Shared" and "Hidden" do not mean fully invisible. If you set either name field to one of these levels, other users still see an initial (e.g. "J." for "John") in place of the full name, so profile cards and search results remain recognizable without exposing your full identity. This exception applies only to registered users and only to your name — every other field set to "Privately Shared" or "Hidden" remains fully invisible to users without the corresponding access. On our public pages, an initial is shown only if that name field is set to Public.
• Community matchmakers and verifiers see only information you have made publicly available or explicitly shared with them.
• Platform administrators may access profiles for safety and trust purposes — including reviewing reports, verification, and technical support.
• Direct messages you exchange with another member through in-app chat are visible only to the two of you. This is separate from the profile-level access described above and does not extend to community matchmakers, verifiers, or platform administrators.
• Services marketplace:
  • When you send a booking request, the provider receives the details you include, such as your name, contact details, event date, location and any notes. The provider is responsible for how they use those details after they receive them, within the limits in our Terms of Service. We cannot control what a provider does with details you share, so share only what the booking needs.
  • A published listing is visible to everyone, including people who are not signed in, along with the provider's name (subject to your name privacy setting), public profile photo, ID-verified status, and city or country if you have made them public.
  • A provider's public record also shows their overall rating, number of completed bookings, response rate and typical response time, and their cancellations and no-shows over the last year. Our team may remove a cancellation or no-show from this record after reviewing a dispute.
  • Reviews are public and show the reviewer's first name (subject to their name privacy setting) and last initial.
  • A provider's "would work with them again" answers about a seeker are private. The seeker sees only how many there are and the most common tags, never who answered or on which booking. A provider receiving a new request from that seeker sees this summary (and some of the approved recommendations a provider wrote about them) only if the seeker has switched sharing on and has at least two such answers; sharing is off by default and can be turned off at any time. These answers are never shown on the matrimony profile, in discovery or matching, or used in any automated decision, and we do not use them to restrict accounts.
  • After a completed booking, a provider cannot read the seeker's review of that booking until they have answered or skipped the "would work with them again" question, or the time to do so has ended. Skipping has no other effect.
  • A recommendation is visible only to the person who wrote it, the person it is about, and our team, until the person it is about chooses to show it. They decide on the version they have read; if the writer edits it in the meantime, they are asked to read it again. A shown recommendation about a provider appears as a testimonial on all of that provider's listings, with a date and the label "A customer", without the writer's name; only the most recent ones are shown, and none while the booking is under review. The provider may still be able to tell who wrote it from the booking or the words used. It is separate from, and not counted in, the star rating and reviews, which a provider cannot hide. A shown recommendation about a seeker is visible only to providers receiving a request from that seeker, and only while the seeker shares. The writer can see whether it is waiting, shown or hidden, can edit it (an edit sends it back for approval) and can withdraw it, which deletes it, unless our team has removed it or the booking is under review. A recommendation that is hidden stays hidden for that booking; the writer can only withdraw it.
  • Our team can read recommendations on a booking for safety reviews and can remove them, recording the reason. Our moderation tools do not show the private "would work with them again" answers; they can be reached only by technical staff where needed to operate, secure or support the service.
  • Booking details, notes and answers are visible only to the two people on the booking, and to our team for support and safety reviews. Each person's booking note is visible to the other person on the booking. Text you add to a booking's history as an agreement is permanent: neither person can edit or delete it, and both can see it. A provider's exact meeting address is shared only with the seeker, and only once a booking is confirmed.
• For Managed Profiles (see below), the guardian who manages the profile can generate a private link to share that profile's photo — either the blurred or the original version — with a specific recipient of their choosing, including someone who does not have a Panosia account.

Anonymous preview on our public pages

To show visitors what our community looks like, our public pages (such as the homepage) may display a small selection of current candidates, chosen at random and refreshed every few minutes, to people who are not signed in. We never show names, photos, or contact details. Each card can show initials, age, country, occupation, marital status, and gender, and only for fields that the member has set to Public. A blurred stand-in image is shown instead of any photo. These pages also show overall member counts and how recently someone joined. If you do not want to appear, set the relevant fields to "Privately Shared" or "Hidden", or switch off your candidate status in your settings.

Third-Party Service Providers

We share data with the following vendors solely to operate the service:

• Supabase: Database, authentication, and file storage infrastructure.
• Stripe: Payment processing for verification services. We receive only payment status and a transaction reference — never your card details.
• Didit (ID verification vendor): Receives your government ID and selfie for the self-service ID check. Documents and biometric data are not stored on our servers.
• Resend: Transactional email delivery.
• OneSignal: Push notification delivery, in your browser or in our iOS app, only if you opt in. We share only an opaque internal account identifier — never your name, email, or profile content — so a notification can be targeted to your browser or device. As with any push provider, OneSignal's own SDK also receives, as an inherent part of how push delivery works, your browser's push subscription details and IP address, or, in our iOS app, your device's push token, device model, operating system version and IP address. You can disable push notifications at any time from your account settings, by denying or revoking notification permission in your browser, or by turning off notifications for Panosia Connect in your iPhone's Settings. In our iOS app, notifications are delivered through Apple's Push Notification service.
• Google Gemini: Optional AI-assisted biodata import, with your explicit prior consent (see AI-Powered Features below).
• Umami Analytics: Privacy-focused, cookieless usage analytics. When you're signed in, we send Umami a one-way code made from your account ID, a numeric ID that only our team can match to your account (used for support and moderation), and your member role and gender, along with the pages you visit and the features you use. We don't send your name, email, phone or profile content. Page addresses recorded by analytics can include the filters you used, such as the city of a Services search (which may start as the city on your profile).
• Cloudflare: Content delivery, DDoS protection, and edge hosting. IP addresses may be processed for network security purposes.

All service providers operate under data processing agreements and are prohibited from using your data for any purpose other than providing their service to us.

Third-Party Links

Our platform may contain links to external websites (e.g. community resources, legal references). We are not responsible for the privacy practices of those sites and encourage you to read their privacy policies before submitting any personal information.

Legal Requirements

We may disclose information when required by law, court order, or valid legal process. See the Law Enforcement Requests section for our full protocol.

Business Transfers

If Panosia LLC is involved in a merger, acquisition, or asset sale, your information may be transferred. We will notify you before your data becomes subject to a materially different privacy policy.

Your Privacy Controls

Every profile field has its own visibility setting. You can change these at any time from your profile settings.

Field-Level Visibility

• Public: Visible to registered users and appears in discovery search. Selected public fields can also appear in the anonymous preview on our public pages.
• Privately Shared: Visible only to users whose access requests you have accepted.
• Hidden: Visible only to you.

Exception for your name: Setting your first or last name to "Privately Shared" or "Hidden" does not fully hide it from other registered users — they will see an initial (e.g. "J." for "John") in place of the full name. No other field has this exception; every other field set to "Privately Shared" or "Hidden" is fully invisible to users without the corresponding access.

More than 25 individual profile fields can be configured independently, including photos, contact details, education, and family information.

Other Controls

• Discover visibility: Use the "Hide from Discover" setting to keep your profile out of Discover. Your candidate status separately records whether you are looking for a marriage partner.
• Access request management: Accept or decline requests from other users to view your private fields.
• Biodata export: Choose which fields appear in your PDF biodata before generating or sharing it.
• Reporting: Report a member for a safety or trust concern; our team reviews reports and can restrict an account's access where warranted (see our Safety & Trust page).
• Account deactivation: Temporarily hide your profile from all discovery and sharing without deleting your account.
• Account deletion: Permanently delete your account and all associated data from your account settings under Settings → Account → Delete Account. Deletion is irreversible.
• AI consent: Revoke your consent to AI biodata processing at any time from the import screen.
• Notification preferences: Manage which transactional notifications you receive, and independently enable or disable browser push notifications, from your account settings.

Data Security

We implement appropriate technical and organisational measures to protect your information against unauthorised access, loss, or misuse:

• Encryption in transit: All data transmitted between your browser and our servers is protected by TLS 1.2 or higher.
• Database security: Row Level Security (RLS) policies in PostgreSQL ensure each user can access only the data they are authorised to see.
• Server-side privacy filtering: Profile data is served through access-controlled database functions, not direct table queries.
• Role-based access control: Platform staff have the minimum access necessary for their role.
• Secure storage: Encrypted file storage with automated backups.
• API key security: Sensitive API keys (email, verification vendor) are held in server-side Edge Functions, never exposed to the client.

No system is completely secure. If you believe your account has been compromised, contact us immediately at connect@panosia.com.

Data Breach Notification

In the event of a personal data breach that poses a risk to your rights and freedoms, we will notify the relevant supervisory authority within 72 hours of becoming aware of it (as required by GDPR Article 33). If the breach is likely to result in high risk to you personally, we will also notify you directly without undue delay, describing the nature of the breach, the data affected, and the steps we are taking to mitigate harm.

Data Retention & Deletion

We retain your data only for as long as necessary for the purposes described in this policy.

Retention Periods

• Active accounts: Data is retained while your account is active.
• Inactive accounts: Automatically deleted after 2 years of complete inactivity.
• Deactivated accounts: Profile hidden from discovery; data retained for 6 months to allow reactivation.
• Deleted accounts: When you delete your account, we immediately erase your profile details and photos, your login email, phone and sign-in links, your Services listings that have never been booked, and your listing claims, and we end your open booking requests and upcoming bookings. A few records are kept as described in this list: bookings and reviews you share with other members, safety reports, and financial records. If we close an account for breaking our Terms, we may keep the information needed to enforce that decision and protect the community, as the law allows.
• Verification documents: Deleted immediately after verification is completed. For self-service ID verification, your selfie, document images and facial geometry are retained only by our vendor per their policy, never on our servers. We keep Didit's result summary (check results, face-match similarity score, document type, and the name, date of birth, gender and country read from your ID) with your verification record, including for checks that were declined or rejected. We keep it while your account exists and delete it when you delete your account.
• Trust badges: Retained for 3 years for authenticity purposes.
• Safety reports: Retained for 3 years for community protection.
• Services listings, bookings and reviews: A listing is kept until you delete it or your account. Bookings and reviews are a shared history with the other person, so deleting your account does not remove them from the other person's account; your name on them is replaced with "Panosia member", the notes in your own notes box are erased (and their earlier saved versions too, unless the booking is under an open report, when they are kept for our Trust & Safety team and then removed 90 days after the booking ends), but the message and answers you sent with a booking request, and anything you added to a booking's history as an agreement, stay on the booking for the other person, and a listing with past bookings is hidden and loses its exact address. A review removed by our team, or a cancellation or no-show removed from a provider's record, is kept with the reason for our Trust & Safety records.
• Peer feedback: A recommendation is kept while it is shown, until its writer withdraws it or either person deletes their account. Recommendations that are not shown (still awaiting a decision, hidden by the person written about, or removed by our team, in which case the reason is kept with it) are deleted after a limited time. When either the writer or the person written about deletes their account, their recommendations are deleted; if the booking is under an open report, the recommendation is instead hidden and then deleted by the same rule once the report is closed. Private "would work with them again" answers, and records of a skip, about a seeker are kept until that seeker deletes their account, and are then deleted. Answers given by a provider who deletes their account stay, without any link to them, so the seeker's summary remains accurate.
• Listing claims: Kept with the decision, so we can show who a listing was handed to and why.
• Listing review records: Review decisions, the reasons our team gave, and review flags are kept with the listing while your account exists, so we can show why a listing was changed or removed. They are removed when the listing is deleted, or with your account, except where a listing is kept for another member's booking history. Photos on a listing you delete are removed from storage when you delete it.
• Direct messages (in-app chat): Messages older than 90 days are automatically deleted, except we always keep at least your most recent 100 messages in a conversation regardless of age, so an active conversation never loses its recent context. If either participant in a conversation is involved in an open safety report, that conversation is held past this period rather than deleted — see Safety & Trust for details. You can delete your own messages or clear an entire conversation at any time (outside of an active report hold) — both are immediate and permanent for everyone in the conversation. You can also remove a conversation from just your own inbox without affecting the other participant, who keeps their copy and message history; this reverses itself if they message you again, and the conversation (and its messages) are only permanently deleted once every participant has removed it on their end.
• Block list: Kept while your account exists, and removed when you unblock a member or delete your account. If a member you blocked deletes their account, the block is removed with it.
• Support interactions: Retained for 2 years.
• Access request logs: Retained for 1 year.
• Financial records: Payment transaction records are retained for 7 years as required by tax and accounting regulations, even after account deletion.

Note: Deleting your account removes your profile from our systems but does not erase content you have already shared with others outside our platform (e.g. biodata PDFs distributed to families, or screenshots taken by other users). The same principle applies to in-app chat: deleting your account does not retroactively erase messages you already sent to another member — they may remain visible to that person and continue to follow the retention and report-hold rules described above until deleted by either of you or automatically removed at the end of the normal retention period.

Your Rights

Depending on your location, you have rights over your personal data. We honour these rights for all users regardless of geography.

Rights Under GDPR (EEA & UK Users)

• Access (Article 15): Request a copy of the personal data we hold about you.
• Correction (Article 16): Ask us to correct inaccurate or incomplete data.
• Erasure (Article 17): Request deletion of your personal data (see note on special category data below).
• Portability (Article 20): Receive your data in a structured, machine-readable format (JSON or CSV).
• Restriction (Article 18): Ask us to limit processing in certain circumstances.
• Objection (Article 21): Object to processing based on legitimate interests.
• Withdraw consent (Article 7): Where processing is consent-based, withdraw at any time without affecting past processing.
• Automated decision-making (Article 22): We do not make decisions with legal or similarly significant effects about you based solely on automated processing. A person reviews every verification decision. You can contact us at any time to ask for a decision to be explained or reviewed again.

Special Category Data & Right to Erasure

Because Panosia Connect processes special category data — including religion, ethnicity, and date of birth — the right to erasure carries particular weight. Upon account deletion:

• All personally identifiable profile data is permanently deleted within 30 days.
• Special category fields (religion, ethnicity, etc.) are deleted immediately — they are not retained for analytics or any purpose after deletion.
• Data you applied via AI biodata import is subject to the same deletion rights. Revoking AI consent does not automatically delete already-applied fields — you must delete them directly or request account deletion.
• We may retain minimal data where required by law (e.g. fraud prevention or legal proceedings) and will inform you of any such exception at the time of your request.

Rights Under CCPA / CPRA (California Residents)

California residents have the following rights under the California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA):

• Right to Know: Request details about what personal information we collect, use, disclose, and sell.
• Right to Delete: Request deletion of your personal information, subject to legal exceptions.
• Right to Correct: Request correction of inaccurate personal information.
• Right to Opt Out of Sale/Sharing: We do not sell or share personal information for cross-context behavioural advertising. This right is not applicable, but we honour it by confirming we have no such activity.
• Right to Limit Use of Sensitive Personal Information: Under CPRA, you have the right to limit our use of sensitive personal information (which includes religion, ethnicity, biometric data, financial information, and precise geolocation). We use sensitive information only to provide the platform — you may contact us at connect@panosia.com to request a review of how any sensitive field is used.
• Non-Discrimination: We will not discriminate against you for exercising any of these rights.

Rights Under India DPDPA (Indian Residents)

Under India's Digital Personal Data Protection Act, 2023 (DPDPA), you have the right to access information we hold about you, request correction of inaccurate data, request erasure of data no longer needed for its original purpose, and nominate a representative to exercise these rights on your behalf. Contact us at connect@panosia.com to exercise any of these rights.

How to Exercise Your Rights

Email connect@panosia.com with your request and enough information to verify your identity. We will respond within 30 days; for complex requests we may extend by a further two months and will notify you. There is no fee for exercising your rights. For account deletion, you may also use the self-service option in Settings → Account → Delete Account.

If you are unsatisfied with our response, you may lodge a complaint with your local data protection authority — for example, the ICO (UK), your EU member state's supervisory authority, or the Data Protection Board of India.

AI-Powered Features

Biodata Import (Google Gemini)

We offer an optional feature that uses Google Gemini to extract profile fields from a document or text you paste. This feature is entirely opt-in:

• Explicit consent required: Your content is sent to Google Gemini only after you grant informed consent. Consent is recorded once and remembered across sessions.
• Data transmitted: Only the content of your uploaded file or pasted text — no other account data or metadata.
• Purpose: Field extraction only (name, date of birth, education, occupation, etc.) to pre-fill your profile form.
• No training use: Google processes data under its Cloud API terms, which prohibit using API inputs to train AI models.
• No retention: Neither we nor Google retain your content after extraction is complete.
• You review before saving: Every extracted field is shown for your review. Nothing is applied to your profile without your explicit confirmation.
• Revocable: Withdraw consent at any time from the import screen. Revocation does not delete fields already applied to your profile.

Legal basis (GDPR): Explicit consent under Article 6(1)(a) and Article 9(2)(a) for special category data including religion and ethnicity. You may withdraw at any time without affecting the lawfulness of prior processing.

Verification Services

All verification services are optional and user-initiated. We collect verification data only to provide the service you request.

Biometric Data Disclosure

The self-service ID verification process involves a selfie for face-match and liveness detection — this constitutes biometric data under laws including Illinois BIPA, Texas CUBI, and Washington's My Health MY Data Act. To be clear: we never collect, store, or process your biometric identifiers or biometric information on our systems. Your selfie and the resulting facial geometry are processed exclusively by Didit (our verification vendor) under their own biometric data policy, and the raw images are not transmitted to or retained by Panosia Connect. We do not receive or store your selfie, document images or facial geometry. We receive and keep Didit's result summary: whether the document, liveness and face-match checks passed, a face-match similarity score, the document type, and the four details read from your ID (name, date of birth, gender and country).

By initiating the self-service ID verification, you consent to Didit's processing of your biometric data for identity verification purposes.

How Verification Data Is Handled

• For self-service ID verification, your government ID and selfie go directly to Didit and are never stored on our servers. We receive Didit's result summary (whether each check passed and a face-match similarity score) and the four details above (name, date of birth, gender and country).
• For digital background checks, supporting documents are reviewed by our verification team and deleted after the check is complete.
• In-person verification: Available on request. If you ask for it, we collect the contact details and city you give us so we can arrange the check. The verifier only confirms who you are; we do not publish personal identity details from a verification, and a verification report shows the result only.
• Verification results are displayed on your profile as trust badges only — detailed report content is not shared with other users without your action.

Verification Report Disclaimer

International Data Transfers

Our service providers may process your data in countries other than your own, including the United States, where data protection laws may differ from those in your country. Where personal data is transferred outside the EEA or UK, we rely on one or more of the following safeguards:

• Standard Contractual Clauses (SCCs) approved by the European Commission or the UK ICO
• Adequacy decisions issued by relevant data protection authorities
• Other legally recognised transfer mechanisms under applicable law

For Indian residents: data may be transferred outside India in accordance with applicable provisions of the Digital Personal Data Protection Act, 2023. By using the platform and consenting to this policy, you consent to such transfers where required for service delivery.

Children's Privacy

Our platform is intended for users aged 18 and over. Registration requires you to confirm you are at least 18 years old. We do not knowingly collect personal information from anyone under 18. If we discover we have done so, we will delete the data promptly. If you believe a minor has created an account, please contact us at connect@panosia.com.

Law Enforcement Requests

We are committed to protecting user privacy while complying with valid legal obligations. We will only disclose user data to law enforcement when legally required — we do not voluntarily share information with government agencies beyond what the law compels.

Types of Legal Process We Honour

• Court orders: Valid orders from a court of competent jurisdiction.
• Search warrants: Valid warrants issued by a judicial authority under applicable law.
• Subpoenas: Valid civil or criminal subpoenas — we may object to or seek to narrow overly broad requests.
• Emergency disclosures: Where there is an imminent risk to life or safety, we may disclose information without prior legal process as permitted by law.

What We Will Not Do

• Respond to informal requests — all requests must follow formal legal process.
• Disclose data we do not possess (e.g. we never hold your government ID images, biometric data, or card details).
• Comply with requests that are overbroad, improperly issued, or inconsistent with applicable privacy law.
• Proactively monitor users on behalf of law enforcement without a valid legal order.

User Notification

Where legally permitted, we will notify the affected user before disclosing their data so they may seek legal protection. If prohibited from doing so (e.g. by a non-disclosure order), we will notify the user as soon as the restriction is lifted.

Data Available to Law Enforcement

In response to valid legal process, we may provide: account registration details (name, email, creation date), profile data stored on our platform, IP addresses and session logs, and payment records (transaction reference and status only). We cannot provide data we do not hold — including government ID images and biometric data processed exclusively by Didit.

How to Submit a Request

Law enforcement requests must be submitted in writing, on official letterhead or through formal legal channels, and must identify the specific account(s), the data requested, and the legal basis. Send to: connect@panosia.com with the subject line “Law Enforcement Request.” Requests from outside our operating jurisdiction must comply with applicable mutual legal assistance treaties (MLATs).

Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by email and by displaying a notice on the platform when you next log in. The “Last updated” date at the top of this page always reflects the most recent revision. Continued use of the platform after a change takes effect constitutes your acceptance of the updated policy.

Contact Us

For privacy-related questions, data subject requests, or concerns:

• Email: connect@panosia.com
• Company: Panosia LLC
• Jurisdiction: North Carolina, USA

We aim to respond to all privacy inquiries within 30 days. For urgent security concerns (suspected breach, account compromise), please include “URGENT” in your subject line.