Age signals and younger readers

How OutaStory uses your app store's age signal to protect younger readers, and exactly what is (and isn't) done with it.

Updated Aug 19, 2026

OutaStory is built for storytellers of many ages, and younger readers
get extra protection in the apps.

Where the age signal comes from

When you use an OutaStory app, the store platform it came from can
tell the app which age range the signed-in store account belongs to:

  • Apple (iOS, iPadOS, macOS) — the Declared Age Range API, fed by
    Family Sharing.
  • Google Play (Android) — the Play Age Signals API, fed by
    account verification and Family Link.
  • Windows — the Microsoft family-safety age-consent group of the
    signed-in Windows account.

The signal is an age range (for example "under 13"), never a
birthday, name or identity.

What changes for accounts under 13

  • Commenting, liking and following authors are switched off.
  • Only all-ages stories (age rating up to 12) are shown — the same
    catalogue visitors without an account see.
  • Reading, listening and offline downloads work unchanged.

If the store reports no signal (for example on a local Windows
account, or when age sharing is declined), the app behaves exactly as
before — the signal only ever adds protection, it never unlocks
anything.

What happens with the signal

Almost nothing, by design: it is read at app start and sign-in, kept
only in the app's memory for the current session, and used for the
checks above. It is never stored, never used for advertising,
analytics or profiling, and never shared with anyone. Our privacy
policy and the youth protection page
describe this in detail.

Something looks wrong?

The age range comes from the store account, not from OutaStory. To
change it, review the store's family settings (Apple Family Sharing,
Google Family Link, Microsoft Family Safety). Questions? Write to
youth-protection@outastory.com.

Still need help?

If this article didn’t resolve your question, open a support ticket and our team will follow up.

Open a support ticket

Something went wrong

An unhandled error has occurred.

Reload the page to pick up where you left off.

Reload

Connection lost

Reconnecting to the server…

Reconnect failed. Trying again in seconds.

We couldn't reconnect to the server. Retry, or reload the page.

The session was paused by the server.

The session couldn't be resumed. Please reload the page.