Demo data handling

The homepage age-estimation demo is a small public tool. Because it is open to the internet, we log a limited set of data for trust & safety review and for the protection of our service. This page explains exactly what.

What we record for every submission

• Date and time of the request.
• Your IP address, and the country / region / city Cloudflare resolves it to.
• Your network provider (ASN and organisation name).
• Your browser's User-Agent string.
• The image you submitted, its size, format, and a SHA-256 hash.
• The model's response (number of faces detected, age summary).
• A separate classification from our Media Examiner Service indicating whether the image contains sexualised content, plus any body / anatomy-derived age band. Submissions flagged as containing explicit content surface a prompt offering a free pilot of our secure tool.
• If you later give us a work email — requesting a free API key, or asking for expanded demo access — we may associate that email with prior demo submissions from the same IP address, within a 30-day window. This is a best-effort match for trust & safety review, not a confirmed identity: IP addresses are often shared or reassigned.
• A cookie called rigr_vid, set the first time you use any of our demos and kept for up to 400 days. It holds a random identifier — nothing derived from you or your device — and lets us tell that several submissions came from the same browser rather than guessing from your IP address. We use it to see whether people come back and to keep our own record of demo activity honest: an IP address alone splits one person across several entries as their network changes, and merges everyone in a shared office into one. If you go on to open one of our product tours we also record which steps you looked at, against the same identifier, so we can tell whether the demos lead anywhere useful. If you have never used a demo, opening a tour records nothing. It is a browser identifier, not an identity: clearing your cookies resets it, and it does not follow you to another device. It is also what we count your free runs for the day against — previously a separate per-demo cookie, now retired.

When we turn a request away

If you reach your free runs for the day, we record that too — the time, the same identifiers listed above, and which limit you reached. No image is involved: a refused request is stopped before we look at one. We keep it so we can see when the free allowance is getting in the way of someone with a real use for the tool.

How long we keep it

Image bytes are deleted automatically after 7 days. The images themselves live in Cloudflare R2 storage with a lifecycle rule that enforces this deletion. We don't touch them after upload other than for review.

The submission record (timestamp, IP, geo, image hash, response summary) is kept indefinitely. The hash lets us identify the same image being submitted again after the bytes are gone, which is essential for spotting abuse patterns.

Why we keep it

• To investigate misuse of the public demo.
• To comply with legal requests if abuse is reported.
• To monitor traffic patterns and detect automated scraping.
• To protect users by blocking IPs that submit illegal content.

We do not use demo submissions to train models. The image is sent to our age-estimation API for inference and is not added to any training set.

Please don't submit

• Images of identifiable people without their consent.
• Images of minors, unless you are their parent or legal guardian.
• Sensitive personal images, identity documents, or medical imagery.
• Anything illegal under the laws of your jurisdiction or Ireland (where Rigr AI is registered).

Submissions of illegal material may be reported to law enforcement.

Deletion requests

To request deletion of your submission record, or to ask what we hold, email [email protected] from any address and include the approximate date and time of your visit. We will respond within 30 days.

Production use of the age API

This page covers the public homepage demo only. The production age-estimation API used by customers under contract is governed by the relevant data-processing agreement, not by this page.