Acceptable Use Policy

Everyone who uses the service, whether or not they have paid and whether or not they have an account. It also covers anything done through your account by someone else, which is why you should keep your sign-in details to yourself.

Do not put any of this into an answer, a support email, or anywhere else:

• Another identifiable person’s personal information. Write about yourself. If you need to mention someone, leave out their full name and anything else that identifies them.
• Content that is unlawful — infringing copyright, breaching confidence, defamatory, or an offence to possess or distribute.
• Content that harasses or threatens any person, or incites hatred or violence against any person or group.
• Sexual content, and in particular anything sexual involving a child. Content of that kind will be reported to the authorities.
• Material that identifies a child, or that solicits information from one.
• Malware, scripts, or deliberately malformed input intended to break the service.
• Deliberately false information submitted in order to obtain a refund, a free attempt, or access to someone else’s account.

Please also avoid putting sensitive information about yourself into a free-text answer where you can. You do not need to disclose a health condition, a disability, your religion, your ethnicity or your sexuality to get a useful report. That is a request for your benefit rather than a prohibition — our Privacy Policy explains what happens if you do.

Against the service

• Attempt to gain unauthorised access to the service, to any account other than your own, or to any system connected to them.
• Attack it — denial of service, flooding, or anything meant to disrupt availability.
• Circumvent rate limits, authentication, payment, or the limit on how many attempts your account holds.
• Probe, scan or test the security of the service without our written permission in advance. We will normally give it — see below.

Automation and extraction

• Use bots, scrapers, crawlers or scripts to complete questionnaires, generate reports, or harvest content.
• Create multiple accounts to get more free usage than one person is meant to have.
• Attempt to reconstruct the scoring model by submitting large numbers of systematically varied answers.
• Reverse-engineer, decompile or disassemble any part of the service, except to the limited extent the law permits despite this clause.
• Use the service, or anything it produces, to train a machine learning model.

Misusing the AI

• Try to make the AI produce content unrelated to careers. The free-text box is not a general-purpose chatbot.
• Attempt prompt injection — instructions written into an answer and aimed at the model rather than at us, meant to change its behaviour, reveal its instructions, or bypass its limits.
• Attempt to extract our prompts, system instructions or scoring logic.

Commercial misuse

• Resell, sublicense or redistribute reports, or run a service that generates them for other people.
• Present a report as your own product, as human-written careers advice, or as the output of a regulated careers service.
• Sell, rent or transfer your account or the attempts on it.

University access

• Use an email address you are not entitled to — someone else’s, or one obtained only for this — to get a university’s free access.
• Let other people use your account so that they get your university’s attempts.

If you have a university dashboard

• Try to work out which student is behind a figure, including by combining the totals with other information you hold.
• Require or pressure a student to show you their report, their answers or their scores.
• Share the dashboard, or your sign-in to it, with anyone your university has not named to us.

Sign-in, sign-up, password reset, payment and report generation are rate-limited. This protects the service and everyone else using it.

Hitting a limit in ordinary use is not a breach and nothing to worry about — wait a moment and try again. Deliberately working around one is a breach. If a legitimate use of yours keeps hitting a limit, tell us and we will look at it.

If you see something that breaches this policy, email support@adaqno.com with enough detail for us to find it.

If a report you received contains something harmful, offensive or seriously wrong, please tell us. We want to know. We do not read your answers or reports as a matter of routine, so a failure mode we are not told about is one we cannot fix. We look at specific content when you ask us to, when investigating an abuse report, or where the law requires it.

Depending on what happened, we may:

• send a warning, for a first, minor or probably accidental breach;
• remove or refuse specific content, where one submission is the problem;
• suspend the account temporarily, for a repeated breach or while investigating;
• close the account permanently, for a serious breach or repeated ones after a warning;
• block access at network level, for attacks and automated abuse;
• report the matter to the police or another authority, where conduct appears criminal;
• take legal action, where we have suffered loss.

Where it is reasonable and lawful, we will tell you what you did and give you a chance to put it right or explain. Where the breach is serious — an attack, or illegal content — we may act immediately and explain afterwards.

Refunds if we close an account for a breach. We do not refund attempts you have already used. Unused attempts we will refund, unless we have suffered loss as a result of your breach, in which case we may keep an amount reflecting that loss — and we will explain the figure.

If you think we have got it wrong, reply and say so. A different person will look at it, and we will restore the account if we made a mistake.

If you have found a security vulnerability, we would much rather hear from you than not. Email support@adaqno.com with the detail, and give us a reasonable time to fix it before telling anyone else.

If you act in good faith, stay within what is needed to demonstrate the problem, do not access or alter anyone else’s data, and do not degrade the service for other people, then we will not treat your testing as a breach of this policy and we will not pursue you for it.

That does not extend to denial-of-service testing, social engineering of our staff or suppliers, physical attacks, or accessing real customer data.

We may update this policy. The version that applies is the one published when you use the service, and the date at the top says when it last changed. If we add a significant new restriction, we will email account holders about it.