Is Perplexity Safe for Kids?
Perplexity requires 13+, and under-18s need a parent to accept the terms on their behalf. Our own recommendation is 13+ with supervision; better suited to 15+. The citation-first design makes this one of the better options for an older student learning to verify claims, which is the skill that matters most. Against that: no parental controls at all and no age gate. Suitable for a supervised teenager doing research, not for a younger child browsing freely.
Checked against Perplexity AI’s own terms and help documentation on 28 July 2026. Sources at the foot of this page.
Guided, age-appropriate AI projects instead of an open-ended chatbot. Free to start, no card required.
What is Perplexity?
An answer engine: it searches the web and returns a written answer with citations, rather than a list of links. For schoolwork the citations are the valuable part.
What do under-18s actually get on Perplexity?
There is no distinct teen experience. Perplexity’s terms require a parent or guardian to accept the terms on behalf of a minor before use, but there is no age gate at signup, so nothing enforces this technically.
What parental controls does Perplexity have?
None built in.
At a glance
| Vendor minimum age | 13+, and under-18s need a parent to accept the terms on their behalf |
|---|---|
| Our recommendation | 13+ with supervision; better suited to 15+ |
| Cost | Free tier available; Pro subscription adds capability |
| Data handling | Queries are processed and retained under Perplexity’s standard terms. |
| Use in school | Genuinely useful for research because it cites sources inline, which makes claims checkable in a way a plain chatbot does not. |
What should parents know?
- •Inline citations are a real teaching advantage — a student can be asked to open the source and check it.
- •The parental-consent requirement in the terms is not enforced by anything at signup.
- •It searches the live web, so results are not filtered to age-appropriate content.
- •No parental controls exist, so supervision has to be device-level or agreement-based.