Acceptable Use Policy

This policy sets out what is allowed on CalProof and what is not. It forms part of our Terms of Service and applies to every account, every user invited to an account, and every interaction with the service.

CalProof is a trading name of Crocker Digital Ltd, registered in England and Wales under Company No. 17008789. The contact for any question or report about acceptable use is abuse@calproof.co.uk.

1. What's allowed

You may use CalProof to keep calibration records for your own organisation, including:

• recording instruments, calibration events, out-of-tolerance workflows, and assessor notes;
• uploading and storing certificate PDFs that relate to your organisation's instruments;
• inviting colleagues from the same organisation to collaborate on a single account;
• exporting your data at any time using the in-app export route;
• integrating with your own internal systems through any APIs or webhooks we publish, in line with their documentation;
• evaluating the service during the 14-day free trial in good faith.

If a use is consistent with the spirit of running a calibration record for one organisation, it is almost certainly fine. If you are not sure, ask support@calproof.co.uk.

2. What's not allowed

We do not allow any of the following.

2.1 Illegal use

You must not use CalProof for any purpose that is unlawful in the United Kingdom or in any other jurisdiction that applies to you. This includes uploading content you do not have the right to upload, infringing anyone's intellectual property rights, or using the service to facilitate fraud.

2.2 Unsolicited messaging

CalProof is not a tool for sending email or marketing campaigns. You must not use any function of the service, including notes, certificate metadata, or invitation emails, to send unsolicited commercial messages or to harass another person.

2.3 Abuse of the free trial

The 14-day free trial is offered in good faith so that you can evaluate the product on real data. You must not create multiple accounts to extend the trial period beyond 14 days, use disposable email addresses to create trial accounts at scale, or otherwise circumvent the trial limits. We reserve the right to refuse a trial to any organisation that has already evaluated the product.

2.4 Scraping and automated extraction

You must not scrape the application UI or use automated tools to extract data at a rate that exceeds normal human use. Programmatic access through documented APIs is fine and expected; programmatic access through scraping the UI is not.

2.5 Bypassing plan limits

You must not attempt to bypass the limits associated with your plan, including instrument counts, user counts, storage allowances, or rate limits. If you need a higher limit, please ask — we are usually happy to help.

2.6 Reverse engineering

You must not reverse engineer, decompile, or disassemble any part of CalProof, except to the extent that English law expressly allows despite a contractual restriction.

2.7 Attempting to access another customer's data

You must not probe or attempt to access data belonging to another organisation, whether through the application, the API, the database, or any other channel. We take any such attempt extremely seriously and will report it to the appropriate authorities where the law requires.

2.8 Disruption

You must not knowingly do anything that disrupts the service for other customers, including running denial-of-service attacks, deliberately submitting malformed input intended to crash the service, or uploading malware.

3. Reporting abuse

If you become aware of someone using CalProof in a way that breaches this policy, please tell us at abuse@calproof.co.uk. Include as much detail as you can: the URL involved, any account or organisation name you have, screenshots if available, and the time the activity took place.

If you are reporting a security vulnerability rather than abuse, please use security@calproof.co.uk and follow the Security Policy.

4. Consequences

If we believe you have breached this policy, we may, depending on the seriousness of the breach:

• contact you to ask for an explanation and an opportunity to put it right;
• temporarily suspend your account while we investigate;
• terminate your subscription with immediate effect;
• decline to issue a refund where the breach was made in bad faith;
• report the matter to the relevant authorities.

We will give you reasonable notice and an opportunity to cure where the breach is curable, but we may suspend or terminate without notice where the breach is severe, where notice would not be appropriate, or where we are required by law to act immediately.

5. Examples and edge cases

We work in a real-world industry where the line between "internal sharing" and "shared too far" is not always obvious. The examples below are not exhaustive but should help.

• One account, multiple users in the same organisation: allowed. A calibration manager and three technicians at the same lab using one CalProof account is the intended way to use the product.
• One account, multiple sister companies under one group: allowed if the group is a single legal entity or if they share a single quality system. Otherwise the second entity should have its own subscription.
• One account, two unrelated organisations: not allowed. This breaks the per-organisation pricing model and creates audit-trail problems if either party leaves.
• A consultant managing several clients: not allowed under one account. Each client organisation should have its own subscription, which the consultant can be invited to as a user. Multi-tenant features for consultants are on our roadmap; ask sales if you need an early look.
• Automated data import via the documented API: allowed. Scraping the UI to do the same thing: not allowed.
• Two trials in one calendar year because you needed a fresh look at the product: usually fine if asked first. Three trials a month using disposable email addresses: not fine.

If you are weighing up an edge case and you cannot find it here, the safest thing is to email support@calproof.co.uk and ask. We would much rather have the conversation in advance than enforce an avoidable suspension later.