Trust and safety
This page describes current safeguards and their limits. It is not a security certification or guarantee that every threat or unsafe message will be detected.
Last updated: 6 September 2026
Account and access controls
- Authenticated routes and sensitive server actions validate the signed-in Supabase identity.
- Administrative services recheck a stored admin role.
- Parent Hub requires an active entitlement, a Parent PIN and a short-lived server-verified unlock token.
- Private learner reads include ownership or authorised-link checks.
Learner safety
Rookwise checks learner chat text for selected safety risks and private-information patterns before ordinary AI processing. Higher-risk events may create a redacted alert for authorised review. Automated checks are imperfect and are not emergency monitoring.
Files and voice
Ask Rook uploads are limited by type, size and quota, stored privately and retrieved after ownership checks. Voice is sent for transcription only after the learner invokes microphone input. Learners should avoid submitting unnecessary sensitive information.
Subscriptions
Paid entitlement is determined from server-held subscription state. A browser redirect cannot activate a plan. Checkout and live PayFast processing remain disabled until the provider integration is completed and verified. Learners under 18 cannot control financial actions.
Report a concern
Report suspected account misuse, privacy issues or unsafe content to support@rookwiseai.com. Do not use email or Rookwise as an emergency channel.