Legal
Last updated: 31 August 2026
Reporting period: to 31 August 2026. This is the first publication, and it contains no statistics. That is deliberate, and the reason is below.
Flirtly is pre-revenue. There is no checkout, credits are granted rather than sold, and the user base is small. Report volume over this period is correspondingly low — low enough that a median computed from a handful of tickets would be arithmetic pretending to be a measurement.
So we publish nothing rather than publish noise. Where a number is not yet meaningful this page says so in those words. It does not print a zero, because a zero is a claim — it says we measured and found none — and we would rather be dull than be read as claiming something we have not established.
The Removal Policy says we measure and publish two numbers: median time to removal, and the share of NCII requests resolved within 48 hours. The measurement side of that is real — every report and decision is written to an append-only ticket log with its timestamps, and that log is kept for three years. The publication side has not happened yet. This page is where it will happen, and section 5 says when.
| Metric | How it is counted | This period |
|---|---|---|
| Reports received, by category | One per ticket at the moment it arrives, split into minor safety, NCII and likeness, copyright, and other. A ticket covering several assets counts once. | Not yet published |
| Content removed, by category | Assets or characters disabled as the result of a report, counted against the category of the report that caused it. | Not yet published |
| Median time to removal | From the ticket arriving to the content ceasing to be servable, across all removals in the period. Median, not mean — one bad week should not be averaged away. | Not yet published |
| Share of NCII requests resolved within 48 hours | Valid NCII requests decided inside the statutory 48-hour deadline, as a share of all valid NCII requests received. The clock starts when a valid request arrives. | Not yet published |
| Reports made to NCMEC | CyberTipline reports submitted in the period. | Not yet published |
| Accounts actioned | Warnings, feature restrictions, suspensions and terminations, counted separately. | Not yet published |
| Appeals received and upheld | Appeals filed against a removal or an account action, and how many of them changed the original decision. | Not yet published |
| Law-enforcement requests received and complied with | Subpoenas, court orders, warrants, preservation requests and emergency disclosure requests, and the number we produced data for in whole or in part. | Not yet published |
“Not yet published” means exactly that: the underlying tickets are being logged, and the aggregate has not been published for this period. It does not mean zero, and it should not be read as one.
Twice a year, covering January to June and July to December, published within 60 days of the period ending. The first report with figures in it will cover the period ending 31 December 2026. If the volume in that period is still too small for a median to mean anything, we will publish the raw counts and say that the median is not meaningful, rather than publish a median we do not believe.
Not the content of a report, not the identity of a reporter, not the account behind a removal, and nothing that would identify a person depicted in reported content. Minor-safety material is never described. Aggregates only, and where an aggregate is small enough to identify someone we will say the bucket is suppressed rather than print it.
Counted in the table above, and described in the Law Enforcement Guidelines. We are not currently subject to any legal restriction that prevents us from stating a number of requests received, and if that ever changes we will say as much as the law lets us say.
If we publish a figure and later find it wrong, we correct it on this page and say what changed and why, rather than quietly restating it. Questions and challenges to anything here: legal@flirtly.co.