closed beta · updated 13 September 2026

Safety on Groven

Use Groven as a place to connect with people you know. It is not designed for emergencies or for sharing highly sensitive information.

Protect your account

• Use a unique, strong password and do not share it.
• Review login sessions in Settings if you think someone else signed in.
• Do not send passwords, verification codes, bank details, or identity documents in messages.

Protect your privacy

• Think before making a profile note or post public.
• Ask before sharing photos or information about someone else.
• Only accept friend requests from people you recognise during this beta.

Encrypted messages and recovery

New direct messages use Groven E2EE v2 and are decrypted on participant devices. Older messages sent before this rollout remain legacy messages encrypted at rest with a server-held key, so the server can still decrypt those older bodies for an authorised participant. Message participants, dates, read state and other delivery metadata are not hidden by E2EE.

Save the recovery code somewhere private and separate from your device. Groven support cannot show or replace it. If the code is lost and no device remains unlocked, the E2EE message history cannot be recovered. Never give the code to another person, including someone claiming to work for Groven.

Encryption does not stop a recipient from copying, forwarding, photographing, or taking a screenshot of a message. It also cannot protect a device or browser that is unlocked, compromised, or controlled by someone else. Groven E2EE is not a guarantee of absolute security.

If something feels wrong

Stop replying, keep a copy of what happened if it is safe, and contact a trusted person. Use Report on a post, comment, or public profile; a report is private and is not shown to the reported person. You can also use Block from a public profile. Blocking hides the two accounts from each other, removes their friendship, and prevents new messages.

How reports are handled

Reports enter a private owner-only queue with a reason and a status: Open, Reviewed, or Resolved. The reviewer can dismiss a report, hide or restore reported content, or suspend or restore an account. Decisions require a reason and are recorded in the moderation history. A report alone does not automatically punish anyone.

A narrow automatic check rejects certain explicit public-text solicitations of child sexual abuse material and direct violent threats. Ordinary profanity is not prohibited by this filter. It does not inspect private messages or private attachments, and does not automatically classify images or videos. Other concerns need a report and human review.

For safety concerns, email yep@groven.social or use the in-app Report controls. See Contact Groven. Do not forward private messages or attachments. The owner still needs to appoint a responsible reviewer and define the response process before the App Store release.