Acceptable use policy

Draft: under legal review. The version that applies to you is the one accepted in the app.

This policy sets out how dpow.app may and may not be used. It forms part of the Terms between DPOW Group Ltd (company number 17276695, registered office 71-75 Shelton Street, Covent Garden, London WC2H 9JQ), "we", and the organisation that subscribes to dpow.app, "you". It applies to everyone you let use dpow.app: Editors, admins, Viewers and anyone given access to a client portal you publish. You are responsible for their use.

1. Lawful use only

You must not use dpow.app to:

1. upload, store, share or publish anything that is unlawful, defamatory, threatening, harassing, discriminatory or obscene;
2. break any law or regulation, including data protection law, anti bribery law, competition law and export controls;
3. process personal data in a way you have no lawful basis for, or upload special category or criminal offence data unless we have agreed in writing;
4. send spam or unsolicited marketing through any feature that sends email or messages, including report emails and WhatsApp;
5. mislead anyone about who you are, or impersonate another person or organisation.

2. Security

You must not:

1. try to get into any account, organisation, project, portal or data you have not been given access to;
2. test, probe or scan dpow.app for weaknesses, or try to get round any sign in, access code, permission or limit, except under our vulnerability reporting rules (section 8);
3. upload or send viruses, malware or any code designed to harm, disable or take over a system;
4. overload dpow.app, interfere with its operation, or run denial of service or automated load against it;
5. share sign in details, or let more than one person use an Editor seat (each seat is for one named person, as the Terms say);
6. share a client portal access code with anyone your client has not authorised to see the portal.

3. No scraping or reverse engineering

You must not, except where the law expressly allows it and cannot be excluded:

1. scrape, crawl or harvest data from dpow.app by automated means, other than through exports and features we provide;
2. copy, decompile, disassemble or reverse engineer any part of dpow.app, or try to obtain its source code, prompts or models;
3. remove or change any notice of ownership, or any label we put on AI generated output;
4. resell, sublicense or rent access to dpow.app, or run it as a service for third parties, unless we agree in writing.

4. No competing product

You must not use dpow.app, its outputs, its templates or its methods to build, train or improve a product or service that competes with dpow.app, or help anyone else do so. This includes using outputs to train an AI model and systematically copying dpow.app's templates, registers or workflows into another product. Your own project documents remain yours to use as you wish (see "Your data and outputs; our platform" in the Terms).

5. Content you have the right to use

You must only upload, connect or publish content you own or have permission to use. That includes drawings, specifications, contracts, photographs, logos and documents from clients, consultants and other project parties. You are responsible for having the right to let dpow.app process that content for you, including sending it to AI providers as described in our privacy notice and data processing agreement. Our copyright and content takedown policy explains how to report content that infringes someone's rights.

6. Using AI features

dpow.app uses AI to draft documents, registers, reports, RFIs, answers and site photo readings. AI output can be wrong, incomplete or out of date. When you use AI features:

1. Review before issue. A competent person on your team must review every AI generated output before it is issued, shared outside your organisation, relied on, or moved to a Shared or Published state. AI output is a draft, as the Terms say.
2. Professional sign off. You must not use AI output for any decision or document that needs a qualified or competent professional's sign off (for example structural, fire, building regulations, principal designer, CDM or Building Safety Act duty holder matters, or a regulator submission) unless that professional has checked and signed it off. dpow.app does not replace that professional, and does not make a project compliant.
3. Site photo readings are indicative only. They are not an inspection and must not be relied on as evidence of compliance.
4. Do not feed in what you may not share. Do not ask AI features to process content you have no right to share with the AI providers we use, or that a contract or confidentiality duty forbids you to share. If you connect your own AI provider key, your own contract with that provider also applies.
5. Do not try to make the AI misbehave. Do not enter or upload content designed to manipulate the AI into ignoring its instructions, revealing other data, or producing unlawful content.
6. Do not present AI output as a person's work where that would mislead, for example in a signed professional statement.

7. Consequences

If we reasonably believe you or someone you let use dpow.app has broken this policy, we may, in proportion to the breach:

1. ask you to stop or put it right;
2. remove or disable access to the content concerned;
3. suspend the user concerned, a client portal, or a feature;
4. suspend your workspace under the Terms, with notice where practical and without notice where needed to protect dpow.app, other customers or the law;
5. end your subscription under the Terms for a serious or repeated breach;
6. report it to the police or a regulator where the law requires or the breach is serious.

Suspension does not end your duty to pay. While your workspace is suspended you can still ask us for an export of your data, unless the law or the breach itself prevents it.

8. Reporting a problem

To report a breach of this policy, or a security vulnerability, email pc at dpow.co.uk. The same address is published in our security.txt file at dpow.app/.well-known/security.txt and datum.dpow.app/.well-known/security.txt. Good faith security research that follows the rules on our Security page will not lead to action against you.

9. Changes

We may update this policy. We will tell account admins about a material change before it takes effect.