Privacy Policy

Account information. Your email address, your name, and a cryptographic hash of your password. We never store your password itself. We also record which organisation you belong to and the role you hold in it.

Information your employer provides about you. Accounts are set up for you, not by you. During early access we provision each organisation's accounts ourselves from the email addresses your employer gives us; a display name is derived from the address, and an initial password is generated that you are never shown until you set your own. You may therefore have an account, and a record in U-Do, without ever having filled in a form or agreed to anything.

Work instruction content. The procedures, steps, text, images, diagrams and video your organisation authors in U-Do. This is your organisation's content and remains so.

Execution records. When someone carries out a procedure, U-Do records who did it and when, which steps they completed, values they entered into forms and measurement fields, pass and fail results, and any notes they wrote.

Photographs and signatures. Photographs captured or attached during authoring and execution, and signature images, which are stored as pictures together with the typed name and timestamp accompanying them.

Training and competency records. Quiz answers, scores, pass and fail outcomes, training assignments and completion dates, competency assessments, and free-text assessments written about a named person by a supervisor.

Feedback and suggestions. Comments and ratings you leave on a procedure or a step, and improvement suggestions you submit — including any photograph you attach — together with a reviewer's notes and decision.

Workforce organisation. Which department, job role and shift you are assigned to, and requests for a supervisor's sign-off, including the message written and who decided.

Technical information. Your IP address is read when you sign in or ask to reset your password, and held briefly in server memory to limit repeated attempts; it is not written to our database. We also record a small number of product events in our own database — today, a record of each sign-in, and a record of calls made with an organisation's API key.

• To operate U-Do: authenticate you, show your organisation's procedures, and record work as it is carried out.
• To produce the records your organisation relies on — execution history, training and competency evidence, and audit trails.
• To send transactional email you or your administrator triggered: welcome messages, password resets, and invitations.
• To keep the service working and secure, including limiting repeated failed sign-in attempts.
• To provide AI assistance where a user invokes it. See section 4.

We do not sell your information, and we do not use your organisation's work-instruction content to market to anyone.

U-Do runs on infrastructure operated by other companies, and some of your information reaches them. The table below is the complete list, with what each one receives and whether it is receiving anything today. Status was verified against our production configuration on the verification date shown in the control block.

"Not configured" means the integration exists in U-Do but is switched off in our production environment, so the provider receives nothing from us today. We list these rather than omit them so you can see the whole picture, and we will update this page and its version number before switching one on.

Each provider publishes its own data-processing terms and its own list of the providers it uses in turn. We link to those rather than reproduce them, because they change on their schedule and not ours.

Web fonts are downloaded when we build the application and served from our own domain, so displaying a U-Do page does not send a request to a font provider.

Some U-Do features send your content to Anthropic's Claude API. This happens in two places: when someone submits a suggested improvement to a step — U-Do sends it automatically, to turn it into a structured edit — and when a written quiz answer is graded. It does not happen on a background schedule, and not to every piece of content in your account. An administrator can switch suggestions off for the whole organisation.

What is sent is specific, and worth stating plainly rather than in summary: for an improvement suggestion, the full content of the step in question, the text the person wrote describing the change, and — where a photograph was attached — a temporary link to that photograph, which Anthropic's systems retrieve directly from our file storage. For quiz grading, the question, the expected answer, and the trainee's written answer.

Anthropic's Commercial Terms of Service, which govern our use of that API, provide that Anthropic may not train models on customer inputs or outputs. That is Anthropic's own standard commercial term, which we rely on — not a bespoke restriction we negotiated.

Not training is not the same as not storing, and we will not blur the two. Anthropic deletes API inputs and outputs from its systems within 30 days of receiving or generating them, except where content is flagged by its automated trust-and-safety systems, or where it is required to retain it by law. We do not hold a zero-retention agreement with Anthropic.

Anthropic's terms carve out content submitted through its optional feedback channels, which may be used for training. U-Do sends no content through those channels. If that ever changes, this page changes first.

Cameras record information inside the image file itself — commonly the capture time and device, and on many devices the location where the photograph was taken.

Photographs captured while carrying out a procedure, and signatures, are re-encoded when the upload is confirmed, and that re-encoding removes the embedded metadata. Every other image reaches our storage exactly as your device wrote it, and may therefore retain embedded camera metadata including location: images added in the procedure editor or the media library, photographs attached to an improvement suggestion, and photographs uploaded as evidence for a skill verification. U-Do does not read, index, display or use that metadata for any purpose.

We state this because it is true today, not because it is the behaviour we want. Aligning both upload paths is a tracked change; when it ships, this section and the version number change with it.

U-Do sets a small number of cookies needed to sign you in and keep you signed in: a session cookie that expires after 24 hours, and cookies that protect the sign-in form itself, one of which is set when the sign-in page loads and before you sign in. They are necessary for the application to work and cannot be switched off while you are using it.

Vercel Web Analytics is active on our pages and records page views with coarse device and referrer information. Your browser also stores interface preferences on your own device — for example which navigation sections you have collapsed — which never reaches our servers.

We do not run advertising trackers, third-party marketing pixels, or cross-site profiling, and no third-party script is loaded into U-Do beyond what the table in section 3 describes.

We keep your organisation's data for as long as its account is open. U-Do is a record-keeping system: execution records, training results and audit trails are retained by design, because deleting them would destroy the evidence the product exists to produce.

We do not currently run any automatic deletion schedule. Uploaded files are retained until deleted through the application. If a member is removed from an organisation, their membership ends but the work they recorded remains part of that organisation's history.

You can export execution records, form submissions and procedure analytics as CSV from inside the application, and save or print an execution report. What U-Do does not offer is a one-click export of an entire organisation, or a self-service way to delete an account and its data. Those requests are handled by a person, and we will tell you what we can and cannot do in your case — including where your employer, not us, decides the outcome.

To make a request, write to support@u-do.build. Depending on where you live you may have rights to access, correct, delete, or obtain a copy of your personal information, or to object to how it is handled. We will work with you in good faith on any such request; where your data belongs to your employer's organisation, we will refer the request to them and support them in answering it.

Where an organisation buys U-Do for its workforce, that organisation decides what procedures exist, who is assigned to them, what is recorded, and who may see it. We hold and process that information on their instructions.

In practice this means your employer — not U-Do — decides whether your execution history, photographs, signatures, quiz results and competency assessments are collected and who reviews them. Questions about why a record exists, or requests to change or remove one, are answered by them. We will help them answer you, and you can always contact us at support@u-do.build if you cannot get an answer.

Passwords are stored only as cryptographic hashes. Data is held by the providers named in section 3, transmitted over encrypted connections, and access to a given organisation's data is scoped to that organisation. Uploaded files are served through short-lived links rather than public addresses.

We do not hold a SOC 2 report or an ISO 27001 certificate, and we do not claim our providers' certifications as our own. If your procurement process needs a security review, write to us and we will answer your questionnaire directly.

U-Do is a workplace tool sold to businesses and is not directed to children. We do not knowingly collect information from anyone under 16.

U-Do is operated from the United States, and our database and file storage are located in the United States. Our hosting provider operates a global network and may serve your connection from a location closer to you. If you use U-Do from outside the United States, your information is transferred to and handled in the United States.

This document is version-controlled. Every substantive change increments the version number, sets a new effective date, and records what changed in the revision history below. We will not change what this page says about where your data goes without changing its version.

Privacy questions, data requests, and security questionnaires: support@u-do.build. Danalytics Technologies LLC, Oregon, United States.