Child Safety Standards

1. Our position

Inviz prohibits child sexual abuse and exploitation (CSAE) without exception. This includes, but is not limited to:

• child sexual abuse material (CSAM)
• the sexualisation of minors
• grooming, solicitation, or sextortion of minors
• trafficking of minors
• any other content or conduct that sexually exploits, abuses, or endangers a child

Using Inviz for any of the above is strictly forbidden. It violates these standards, our terms of use, and the law in every jurisdiction in which Inviz is distributed.

Inviz is an 18+ application. It is not directed at children, and we use Google Play's minor-restriction controls to prevent users identified by Google as minors from downloading it.

2. How Inviz works, and why it shapes everything below

Inviz is a serverless, offline messenger. Messages travel directly between nearby phones over Bluetooth Low Energy, hop by hop, and are end-to-end encrypted using the Noise Protocol. Concretely:

• There are no servers. Brokoz operates no infrastructure. No message ever passes through any system we control.
• There is no internet connection. Inviz has no internet transport of any kind. This is permanent and by design.
• There are no accounts. Identities are generated on the device. We hold no user registry, no email addresses, and no phone numbers.
• We collect no user data, consistent with our Google Play Data safety declaration.
• Messages are text only. Inviz cannot send images, video, or files. The application contains no attachment mechanism.

We state this plainly because it determines what we can and cannot do. It is a deliberate design property, not an oversight - and it is not a means of evading responsibility. It is the same architecture that protects users from surveillance, and we accept that it cuts both ways.

3. What we can and cannot do

We would rather be honest than reassuring.

We cannot:

• see, scan, store, or moderate any message sent through Inviz
• remove content - there is no content under our control to remove
• suspend or ban a user - there are no accounts to suspend
• disclose user data to authorities - we hold none

We can, and do:

• prohibit CSAE in these standards and in our terms of use
• give every user immediate, on-device blocking
• provide in-app reporting that reaches a named child safety contact
• act on the evidence a report contains (see section 5)
• cooperate with law enforcement to the extent our architecture permits
• restrict the application to adults through Google Play

4. Blocking and reporting inside the app

Every conversation offers Report & block.

• Blocking is immediate and local. It takes effect on the user's device at once. It does not depend on us, on a network, or on any report reaching anyone, so it cannot fail.
• Reporting composes a report on the device - the reported user's identity, their recent messages as held on the reporter's own device, and space for the reporter's own account of what happened - and hands it to the user's email application, addressed to our child safety contact. The user sees the full contents and chooses whether to send it. Nothing is transmitted silently.

Because Inviz has no server, a report is an email rather than a background submission. This is the only mechanism available to a serverless application, and we prefer it: the user sees exactly what is sent, and the protective action - blocking - never depends on us at all.

5. What happens when we receive a report

A report reaches us as an email containing whatever the reporter chose to send, which may include message text from their device. This is the only circumstance in which we see any Inviz content.

When a report indicates CSAE, we will:

• review it promptly
• report it to the appropriate authority - the Internet Watch Foundation (UK) and/or the National Center for Missing & Exploited Children (US), or the relevant regional authority
• cooperate with any subsequent law enforcement request, providing whatever we hold - which will ordinarily be only the report itself
• where a report reveals a weakness in the application's safety features, address it

We cannot remove the reported content or ban the reported user. We say so directly rather than imply otherwise.

6. Reporting CSAE directly to authorities

If you encounter child sexual abuse material, or a child at risk, please report it to an organisation that can act on it. They can do more than we can, and reporting to them is more effective than reporting to us.

• United Kingdom - Internet Watch Foundation: iwf.org.uk. To report a child at risk of abuse, contact CEOP at the National Crime Agency: ceop.police.uk
• United States - NCMEC CyberTipline: report.cybertip.org, or 1-800-843-5678
• Elsewhere - INHOPE lists national hotlines: inhope.org
• A child in immediate danger - contact your local emergency services (999 in the UK, 911 in the US).

7. Child safety point of contact

SEAN BURRAGE
childsafety@brokoz.com
Brokoz

We aim to acknowledge child safety reports within 7 business days.

8. Legal compliance

Brokoz complies with applicable child safety laws in the jurisdictions in which Inviz is distributed, and will respond to lawful requests from law enforcement. Users should understand that our ability to assist is limited by the application's architecture: we hold no user data, no message content, and no account records, and we are therefore unable to produce them.

9. Review

These standards are reviewed at least annually, and whenever Inviz's functionality changes materially. If Inviz ever gains the ability to transmit images or files, these standards will be revised before that capability is released.