How we keep your team's voice safe

1. Separation between organisations

Every university, company or team that uses Awesome Ted has its own space. The database itself checks which organisation each request belongs to and returns only that organisation's records, so a single mistake in one screen is not enough to show one organisation's data to another.

2. Who can see what

• You see your own reflections, the feedback and results released to you, and your own result.
• You never see which teammate gave which rating; you see summaries only.
• Professors and leads see reflections, results and concern flags for their own classes or teams, with peer feedback as summaries and rater counts.
• Organisation administrators see data across their organisation only where their organisation enables it.
• Our staff access platform data only when needed for support, security or legal obligations.
• When an organisation submits a framework for public sharing, the Janna AI review team reads it as submitted, with its source, Ted test run checks and rights confirmation. If someone reports a library framework, reviewers read the reason and note, but not who sent it. Reviewers never see any organisation's sessions, conversations, feedback or grades.

3. Signing in

Signing in needs your password and a single-use code sent to your email. Passwords are stored only as secure one-way hashes, never in readable form. Sign-in and our forms are rate limited to slow down guessing and abuse.

4. Encryption

Connections to Awesome Ted, between our services and to our providers are encrypted. Notes about wellbeing and other concerns raised in a conversation are also encrypted when stored.

5. How Ted's AI is kept safe

• Ted sends AI providers only what each task needs, using first names or pseudonyms in place of full details where possible.
• Our AI providers process data under agreements that do not allow them to train their models on it.
• Voice calls go straight from your browser to our AI provider. Our servers never receive or keep the sound of anyone's voice, and only a written transcript is kept, like a typed conversation.
• Ted treats documents and what people say as information, never as new instructions. Attempts to change its rules that Ted detects are refused and flagged.
• Common ways of hiding text in uploaded PDFs are detected and that text is removed before Ted sees it, and your organisation is told when some was found.
• Ted helps evaluate reflections, and your professor or lead can review any result and adjust it. Awesome Ted makes no decision with legal or similarly significant effects on its own.

6. Our website

awesometed.com uses no cookies, analytics or advertising, and loads no third-party scripts. It sends strict security headers on every page. Details you send through Book a demo or Contact us are sent to our team by email and are not kept on the website. To stop abuse, the website keeps only short-lived counters and, for 24 hours, a one-way fingerprint of the email address that cannot be turned back into it.

7. Logs and audit trail

Our logs never contain what people write in reflections, and people are identified in them only by pseudonyms. Sensitive actions, such as changing roles, changing grades or exporting results, are written to an audit log built to show if its entries have been altered or removed.

8. How we build and release

Every change is security reviewed and tested before release, and automated checks look for known vulnerabilities in the software we depend on and for secrets accidentally written into code. Changes reach the live service only after those checks pass and a person approves the release.

9. If something goes wrong

If a personal data breach happens, we act quickly to contain it, assess the risk, and tell your organisation without undue delay so it can meet its own obligations. Where we are responsible for the data and the law requires it, we also notify the relevant authority and the people affected. Our Privacy Notice explains this in full.

10. Reporting a vulnerability

If you believe you have found a security problem in Awesome Ted or awesometed.com, please tell us privately so we can fix it before anyone is harmed.

Security researchers and tools can also find our contact details in the standard machine-readable file at /.well-known/security.txt.

No system is perfectly secure, but we work continually to protect the people who trust Ted with their words.