InnieHub Child Safety Standards

Published by: T&T Consulting Business, LLC ("T&T"), which operates InnieHub
Lives at: /child-safety
Version: 1.0
Last updated: 30 August 2026
Effective: 30 August 2026

To report a child safety concern right now

Inside InnieHub: open the menu on the person, the post, the comment or the forum entry, choose Report, and pick A child is involved, or at risk. It goes to the front of the queue.
By email, with or without an account: safety@inniehub.com. You do not have to be a member, and you do not have to sign in.
If a child is in immediate danger, contact your local emergency services first. We are not an emergency service, we do not watch the platform in real time, and we cannot send help.

Before the sections

Google Play requires every social and dating application to publish its standards against child sexual abuse and exploitation. This is that document, and it exists because of the requirement.

It would be easy to write it as a compliance artefact, so here is the part that is not: InnieHub is a service for adults with agoraphobia and social anxiety, and its members are people who are used to being approached by others who noticed they were isolated. Section 5.3 of the Community Guidelines already names that pattern for adults. Everything below is the same reasoning applied to the case where the person on either end is a child.

Nothing in this document is new policy. Community Guidelines section 5.4 and clause 4 of the Terms of Service already said it. What was missing was a single page saying it in one place, and, until this version, a way to report it in the words a person would actually use.

What this document is, and who it binds
The standard
InnieHub is for adults only
What is prohibited
How to report
What happens to a report
What we tell the authorities
What we preserve, and for how long
What prevents this here, and what does not
Who is accountable
Changes

1. What this document is, and who it binds

1.1 These Standards apply to everyone who uses InnieHub and to everything in it: posts, comments, groups, events, forums, stories, direct messages, voice and video calls, profiles, InnieDate profiles, course content, blog articles and what is written to the InnieCare assistant.

1.2 They are read alongside the Terms of Service, the Community Guidelines and the InnieDate Supplemental Terms. Where those documents bind you, these Standards describe how we operate the part of them that concerns children. If this page and a contract ever disagree, the contract governs, and tell us so we can fix this page.

1.3 They apply everywhere the service is available, in every language it is offered in, on the web and in both applications.

2. The standard

2.1 There is one rule and it has no exceptions. Child sexual abuse and exploitation is prohibited on InnieHub, in every form, in every space, public or private, and it results in immediate and permanent termination of the account, without a warning, without a first strike, and without an appeal on the merits.

2.2 It is the only category in the product treated this way. Every other measure we take is proportionate, graduated and appealable, and the Community Guidelines explain at length why. This is the exception, and section 14.3 of those Guidelines already listed it as one.

2.3 A terminated account is not permitted to return. Creating a replacement account after a termination under these Standards is itself a breach, and clause 10 of the Terms of Service covers it.

3. InnieHub is for adults only

3.1 You must be 18 or over. There is no version of InnieHub for anyone younger, there is no supervised mode, and there is no part of the service a child is permitted to use.

3.2 The age gate blocks rather than refuses. At sign-up we ask for a date of birth. A date showing under 18 terminates the account permanently, immediately and automatically, rather than refusing the value and returning you to the form, because a form that reopens is a retry screen and not an age gate. Clause 4.4 of the Terms of Service sets this out, and section 21 of the Privacy Policy covers what happens to the data.

3.3 We do not verify age with a document. We say so plainly rather than implying a check we do not perform. The gate is a declaration, and a declaration can be false, which is exactly why the reporting route in section 5 matters and why section 3.4 exists.

3.4 If we learn that a member is under 18, we terminate the account and delete the personal data, keeping only the minimum record described in section 16.3 of the Privacy Policy. We act on this whether we learn it from a report, from something the person wrote, or from anywhere else.

3.5 Nothing here punishes a child for having got in. A person under 18 who reaches us, or whom we find, is removed from the service and their data is deleted. They are not reported for being here, and being here is not what any of this is about.

4. What is prohibited

4.1 All of the following are prohibited, whether the material is photographic, drawn, animated, written or generated by software, and whether the child is real or depicted:

a) Child sexual abuse material in any form, including material a person did not create and is only sharing, storing or linking to;

b) Sexualising a minor in any way, including sexualised commentary about a real child, and including material that has been edited to sexualise an ordinary image of one;

c) Grooming: any attempt to contact, befriend or build trust with a person under 18 for a sexual purpose, or to move such a conversation to another service;

d) Solicitation: asking a person under 18 for sexual images, sexual contact, or a meeting for either;

e) Sextortion: threatening to publish intimate material about anyone, at any age, in order to obtain more of it, money, or anything else;

f) Trafficking or facilitation: advertising, arranging, paying for or profiting from the sexual exploitation of a person under 18;

g) Advocacy: presenting sexual interest in children as acceptable, promoting it, or seeking others who share it;

h) Signposting: linking to, naming, or explaining how to reach any of the above elsewhere.

4.2 Reporting or describing abuse is not prohibited. A survivor writing about what was done to them, at any age, is doing the thing this platform is for. Section 3.1 of the Community Guidelines says that experience may be described in full, and section 15.1 says the word filter is not permitted to contradict it. Neither is this document.

4.3 An ordinary photograph of a child is not prohibited either. A member's family photograph is a family photograph. What 4.1 prohibits is the sexualisation of one, not its existence.

5. How to report

5.1 In the application, in the words you would actually use. A person, a post, a comment, a forum topic, a forum reply and an InnieDate profile each carry a menu with Report in it. The reasons offered include A child is involved, or at risk, described as sexual content involving anyone under 18, or an adult approaching a child. It is there on the web and in both applications, in English and in Spanish, and it is the same wording in all of them.

5.2 By email, without an account. safety@inniehub.com reaches the same people. You do not need to be a member, you do not need to sign in, and you do not need to have seen the content inside the platform.

5.3 A report can be about anything, not only about a member. If you believe a person under 18 has an account, tell us and we will act, and clause 4.6 of the Terms of Service already commits us to it. If you are a parent, a guardian, a teacher or an authority, the same address reaches us and you will get an answer.

5.4 We never reveal who reported. Not to the reported member, not in the statement of reasons that a measure comes with, and not on appeal. Section 13.4 of the Community Guidelines explains why.

5.5 Report it even if you are not sure. A report that turns out to be nothing costs a moderator a minute. The other way round costs a child. Section 13.3 of the Community Guidelines, on reporting accurately, is about people who use reports as a weapon, and it has never been about somebody who was worried and wrong.

6. What happens to a report

6.1 It jumps the queue. Reports are routed by what they are about rather than by when they arrived, and a child safety report enters the fastest lane, alongside self-harm and fraud. It does not wait behind the morning's advertising.

6.2 Administrators are notified at once, in addition to the report being filed, because the fastest queue is still a queue and this category is not one to leave to the next time somebody opens the panel.

6.3 The content comes down first. Where a report is credible on its face, the material is removed and the account is restricted before any further assessment, and we accept the cost of being wrong in that direction.

6.4 A person decides. No automated system terminates an account under these Standards. Section 15.2 of the Community Guidelines says that nothing automated can ever set a permanent ban, and this is not an exception to it.

6.5 You are told your report was reviewed. You will not be told what happened to the other account, which is information about them. Section 13.5 of the Community Guidelines explains that, and acknowledges that it is unsatisfying.

7. What we tell the authorities

7.1 United States. T&T Consulting Business, LLC is a Florida company and a provider under 18 U.S.C. section 2258A. Apparent child sexual abuse material is reported to the CyberTipline operated by the National Center for Missing and Exploited Children, with the information that section requires.

7.2 European Union. Where we become aware of information giving rise to a suspicion that a criminal offence involving a threat to the life or safety of a person has taken place, is taking place or is likely to, we promptly inform law enforcement or judicial authorities. This is clause 10.7 of the Terms of Service, it is an obligation rather than a discretion, and it applies in particular to anything involving a minor.

7.3 Anywhere else. We answer any public authority, in any jurisdiction, at legal@inniehub.com, whether or not that authority has jurisdiction over us, because declining to reply is not the same as declining to comply. Clause 11.5 of the Terms of Service says so.

7.4 We do not warn the account holder that we have reported them, where telling them would prejudice an investigation or put a child at risk. Everywhere else in this product a member is told what we did and why, and this is the one carve-out from that promise.

8. What we preserve, and for how long

8.1 Where we report under section 7.1, we preserve the material and the associated data for at least 90 days from the report, as 18 U.S.C. section 2258A(h) requires, and longer where an authority asks us to.

8.2 Preserved material is not accessible from the product. It is held for the authority and for nobody else, and it is not used to train anything, sold, shared with any third party, or looked at for any other purpose.

8.3 Preservation survives a deletion request. Section 16 of the Privacy Policy sets out the retention rules and the legal-obligation ground they rest on. A request to delete an account does not delete something we are required by law to preserve, and we would rather write that here than have somebody discover it later.

9. What prevents this here, and what does not

We would rather describe the actual system than the one that would read better.

9.1 What is in place.

An adults-only service with an age gate that terminates rather than retries, section 3.
No public content. InnieHub is not indexed and not readable without an account; there is no anonymous browsing surface for anybody to trawl.
A reporting route in both clients, in both languages, on every kind of content, routed to the fastest queue and notified to administrators, sections 5 and 6.
Termination without a graduated path, which is deliberate and is the only category treated that way, section 2.
A word filter on everything written, described in section 15.1 of the Community Guidelines.
Rules that already prohibit the adjacent behaviour: no sexual content anywhere on the service at all, section 5.1 of those Guidelines, and no approaching people because they said they were isolated, section 5.3.

9.2 What is not in place, said plainly.

We do not run automated image hash matching, and we do not scan uploads against any known-material database. Section 15.4 of the Community Guidelines lists every automated process in the product and says that is the complete list. It is, and this is what that means here.
We do not verify anybody's age with a document, section 3.3.
Nobody reads your direct messages proactively. Private spaces are private from us until somebody reports something, and section 1.2 of the Community Guidelines is what makes a reported message something we can look at.

9.3 Why we are telling you what we do not do. A page that implies detection we do not perform would leave a reader believing something is being caught that is not, and would make the reporting route in section 5 look optional. It is not optional. Until 9.2 changes, a report is how we find out, and that is the honest description of this system.

10. Who is accountable

10.1 The point of contact for these Standards, and for any question about how we prevent child sexual abuse and exploitation, is safety@inniehub.com.

10.2 For an authority, legal@inniehub.com, per clause 11.5 of the Terms of Service.

10.3 Who handles these reports. Administrators, and volunteer moderators who currently hold the Moderator Terms. A moderator who has stood down, paused the role, or not re-accepted a republished agreement stops receiving anything, and no measure under section 2 is taken by a volunteer.

10.4 If we get this wrong, tell us at feedback@inniehub.com. Section 20.3 of the Community Guidelines means what it says about revision, and it applies to this page too.

11. Changes

11.1 This page is versioned and dated at the top, and previous versions are kept at the legal centre.

11.2 We will publish a change here before it takes effect, and section 20.1 of the Community Guidelines governs notice for any change to the rules themselves.

T&T Consulting Business, LLC · 13575 58th Street North, Suite 200, Clearwater, FL 33760, United States