Lucentay

Lucentay — Safety Policy

DRAFT — NOT LEGAL ADVICE. Drafted by an AI assistant describing the safety features that actually exist in Lucentay's codebase as of 19 August 2026, plus gaps worth closing before launch. A lawyer should review the commitments made here before this is published — especially if a specific response-time promise is ever added later, since a stated commitment becomes something you're expected to actually meet.

Last drafted: 19 August 2026

1. Our approach

Lucentay is built around a simple idea from the "PRODUCT CONCEPT" behind the app: trust should be earned gradually, with family and community involved, not assumed from the start. Every safety feature described below exists to slow things down, add a human check, or give you an easy way to flag a problem — not to promise that every interaction on the platform is risk-free. No matrimonial platform can guarantee the character or intentions of another person, and Lucentay does not claim to.

2. What we verify, and what we don't

Identity verification (optional, via Stripe Identity): confirms that a government-issued ID was presented and matched basic checks. It does not confirm marital status, criminal history, or character.

Imam Verification (optional): confirms that a named religious leader, contacted directly by us, affirmed that the user is known to their mosque community. It reflects that one person vouched for another — it is a meaningful trust signal, but it is not a background check, and we do not independently verify the imam's own identity beyond the email address provided.

Guardian (wali) notification (optional): lets a user name a guardian who is informed of the user's matches. This adds a layer of family awareness but is currently a soft, opt-in feature, not a mandatory gate.

We display badges for these on a profile only when actually completed, and we do not allow a user to self-report verification status.

3. The structured 30-day journey

Unlike an open-ended chat app, a new match on Lucentay proceeds through a structured, week-based process before unrestricted messaging opens, intended to encourage profile review and family/guardian involvement before direct contact deepens. Messaging currently opens in week three of this process. This pacing is a deliberate safety and values feature, not a bug, and we ask users not to try to work around it.

4. In-conversation safeguards

Once messaging opens, Lucentay automatically and privately (not via human review, unless a report is filed) looks for two categories of risk in message content, and shows the sender a supportive reminder when detected:

  1. General boundary phrases — language suggesting meeting in person unaccompanied, keeping the conversation secret, or similar — triggers a general reminder to keep the connection purposeful and to involve one's guardian.
  2. Actual contact information — a real phone number, email address, or social media handle typed in a message (not just someone mentioning the concept) — triggers a more specific reminder, tiered by how hard the shared information would be to take back: phone numbers get the strongest reminder.

These reminders are shown to the sender, not blocking their message, and are not reported to anyone else. They exist to prompt reflection, not to police conversation. Users remain free to exchange contact information if they choose to — Lucentay does not, and cannot, prevent an adult from sharing their own information with another consenting adult.

5. Reporting a concern

Any user can report another user directly from that person's profile, selecting a reason (harassment, fake profile, inappropriate content, safety concern, or other) and an optional description. Reports go to a moderation queue reviewed by [NAME THE ACTUAL PERSON(S) OR TEAM — CURRENTLY THIS APPEARS TO BE THE FOUNDER ALONE; STATE THIS HONESTLY RATHER THAN IMPLYING A LARGER TEAM].

We currently make no specific response-time promise anywhere in the app or backend (confirmed 20 Aug 2026 by checking the actual report code and screen — both just say a report will be "reviewed by our team," with no timeframe stated). That's consistent with what this document should say too: aim to review promptly, without committing to a specific number of hours you might not consistently meet at current staffing. If you later decide to commit to a real SLA (e.g., "within 24 hours"), add it to the code/in-app copy first, then update this document to match — don't promise something here that the product doesn't actually say or do.

Depending on severity, a report may result in: a warning, a temporary suspension, or a permanent ban (which also disables the person's ability to sign in). Reports themselves are not shared with the person being reported.

If you are in immediate danger, contact local emergency services (911 in Canada) — do not wait on an in-app report for an urgent situation.

6. Ending a connection

Either person in a match can end it at any time, with a reason and an optional note, without needing the other person's agreement. Ended matches keep their message history visible to both people for a 7-day grace period, after which [CONFIRM: intended long-term behavior for message history after the grace period — this is not yet fully defined and should be decided and reflected here and in the Privacy Policy's retention section]. New messages cannot be sent once a match has ended, enforced on the server, not just hidden in the app.

7. Preventing repeat harm

Updated 20 Aug 2026. A permanently banned account, and the email address it was registered under, are both blocked from creating a new account. This is a real, working protection, not just a policy statement — but it has a real limit worth stating honestly rather than glossing over: it cannot stop someone from signing up again using a genuinely different email address. Closing that fully would require mandatory identity verification for every user at signup (not just the optional Identity/Imam Verification described in Section 2), which is a larger product decision, not something implemented today. [CONFIRM WITH A LAWYER whether this document should describe the limit this explicitly, or in softer language — the underlying fact (partial, not complete, protection) should not change either way.]

8. Photo privacy

You control whether your main profile photo is visible only to your matches, or also visible to other members browsing Discover, before you've matched with them. We recommend reviewing this setting and choosing what you're comfortable with.

9. What to do if something feels wrong

If a match, or anyone on Lucentay, pressures you to bypass the structured pacing, discourages you from involving your family or guardian, asks for money, or asks you to move off-platform quickly — these are worth pausing on. Report it, tell your guardian or a trusted family member, and remember that no one on Lucentay can see your private information without your choosing to share it.

10. Contact

Safety concerns, outside of an in-app report, can be sent to [SAFETY CONTACT EMAIL].

End of draft. Section 7 in particular describes something that needs to be true in practice — a real re-registration block — not just words in a policy, before this should be published.