Portail now asks your age

Portail v2.4.3 shipped on 2026-10-03 as a patch release focused on portail now asks your age. Portail now asks how old you are when you sign up, on the web and in Telegram. You type a number, and we keep only an age range, never the exact age. The reason is simple: we can't knowingly hold chats from kids under 13 without a parent's consent, and we have no way to collect that consent. So under 13 means no account, the same rule OpenAI uses. If you're 13 to 17, you can use Portail with a parent's permission, and you get a short game first that covers five rules for using AI well: double-check facts that matter, keep personal info out of chats, use AI to learn instead of skipping the learning, take real problems to real people, and never make fake pictures of real people. Your chats also get a little extra care around topics that matter more at that age. If you already had an account before this change, you'll see a one-time question the next time you open the chat. Answer it once and it never comes back. Our Terms of Service now spell out the 13+ rule in both English and Russian. The work is recorded here because small releases are still product history. They change how people sign in, read responses, pay for access, share conversations, open files, or trust the system when something goes wrong.

The main changes were direct: sign-up asks your age right after your name, on the web and in telegram. only an age range is stored, never the exact number, under 13 can't create an account. if an existing account answers under 13, it's paused, not deleted, while we check, so a typo can be fixed, ages 13 to 17 get ai street smarts, a two-minute game with five rules for using ai well, plus gentler chat guidance. anyone can replay the game from the sign-up screen, accounts created before this update answer the age question once, the next time they open the chat, telegram asks your age before your email, and the ai street smarts game works there too with /aiguide, and terms of service section 2 now states the 13+ rule and the parent-permission rule for under 18, in english and russian. That list is intentionally plain. It names what changed without turning the release into theatre. When a release fixes a build, a redirect, a storage path, or a UI edge case, the value is often that users stop noticing the problem. The archive keeps that invisible work visible enough for future debugging and for anyone checking whether Portail has cared about the details over time.

This version also fits into the wider Portail contract. One account, one chat history, and one model picker only work if the smaller pieces keep their promises. Authentication has to fail clearly. Billing has to count honestly. Uploads have to arrive in a form models can read. Admin tools have to show the operator what happened instead of hiding it behind a blank screen. v2.4.3 moved that contract forward in its own narrow lane.

The screenshots attached to this entry show the public release record as it now appears on portail.cc. For older releases, this archive was rebuilt from the git history, package version changes, release modal text, and commit subjects. That means the page is honest about its source: it documents the shipped change and preserves the record going forward, even when the exact old production screen cannot be recreated from a single saved image.

The practical result is simple. Someone landing on this page can see the version number, date, release tier, headline, highlights, and a real rendered screenshot of the archive page. Search engines can index the post through the canonical URL, sitemap entry, and structured data. Future releases now have a standard to meet before deploy, so the history should get cleaner from here instead of fuzzier.