Privacy policy

Who we are

Revive Code (revivecode.app) is run by PW App Development Limited, a company registered in England and Wales (company number 14108044), whose registered office is at The Post House, Village Street, Thruxton, Andover, SP11 8LZ. We are the data controller for the personal data described here.

For anything about your data, email support@revivecode.app.

Your projects' contents are different. You decide what goes into the code and files you upload. For any personal data inside them, you are the controller and we process it only to do the work you asked for, under our data processing agreement.

What we collect

• Your account: your name and email address, and your password, which our sign-in provider stores only in scrambled (hashed) form. If you sign in with Google or GitHub, they send us your name, email address and a link to your profile picture, which we keep and refresh each time you sign in with them. GitHub also sends your username and account number, which we keep so we can deliver code to your GitHub later. Your picture is loaded from Google's or GitHub's own servers, so they can see when it's viewed. We never keep your Google or GitHub passwords or access keys. Every account signs in with a second step, a code from an authenticator app: our sign-in provider keeps the secret that app uses to make its codes.
• Your projects: the source code and installers you upload, each project's name and description, the email address for its notifications, the decisions you make, answers to our questions, and your comments and review requests, which are stored with your name.
• People you invite: their email address and the role you gave them, stored with the invitation and your name, even if they don't have an account yet.
• Messages to us: what you send through Help, including an assistant conversation if you choose to send it to the team, with your name, email address, the page you were on and the project you picked.
• The assistant: your questions, sent along with a summary of your projects' progress so it can answer. We don't keep the conversation unless you send it to us.
• Deletion receipts: for each project you delete, its name, what was removed and when.
• Technical details: when you use the site, our hosting providers record details such as your IP address, browser and the pages requested, to run the service and keep it secure.

Why we use it

• To provide the service you signed up for (performing our contract with you): your account, projects, team, the assistant, and help when you ask for it.
• To keep the service secure and prevent misuse (our legitimate interests): sign-in checks and technical logs.
• To send emails about your account and projects (performing our contract): confirming your email address, resetting your password, and decisions or invitations that need you. We don't send marketing emails without asking you first.
• To meet legal obligations, such as keeping accounting records once we bill you.

We never sell your data, and we never use your code or data to train AI models.

AI

Our AI is provided by Anthropic, the maker of Claude. Today, the in-app assistant sends your question and a summary of your projects' progress to Anthropic's API. When our migration pipeline starts working on real code, the code you upload will be sent to Anthropic too, as it is analysed and rebuilt.

Anthropic's commercial terms don't allow it to train its models on data sent through its API. We are arranging zero data retention with Anthropic, so that it keeps nothing once a request is complete, and will update this page when that's in place. Until then, see Anthropic's privacy policy for how long it keeps API data.

Who else handles it

We use these providers to run Revive Code. Each handles your data only to provide its service to us.

Where a provider handles data outside the UK, we rely on the safeguards UK law requires, such as UK adequacy regulations or the ICO's international data transfer agreement.

How long we keep it

• Your account: until you ask us to delete it.
• Projects: until the project's owner deletes it. Deletion is immediate: the uploaded files, the project's own encryption key and every record go at once. Our database's daily backups hold a copy for up to 7 days, then it's gone. Uploaded files aren't in those backups.
• Invitations: they stop working after 7 days, and are deleted with the project.
• Deletion receipts and messages to us: until your account is deleted.
• Your comments and review requests in someone else's project: they are part of that project until it is deleted. If you delete your account, your name is taken off them (and off invitations you sent). The project's decision history, which records who accepted, approved or chose what, keeps your name: that record belongs to the team.
• Technical logs: for a short period set by each hosting provider, typically days or weeks.

Deleting your account

Delete it yourself from the Account page (in the account menu), or email support@revivecode.app from the address on your account and we'll do it. Any projects you own are deleted in full first, and their teams see a note that they were deleted.

Your rights

You can ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, or to receive it in a portable format. Email support@revivecode.app and we'll respond within one month, as the law requires.

If you're unhappy with how we handle your data, please tell us first. You can also complain to the Information Commissioner's Office at ico.org.uk.

Keeping it safe

Your data is stored in London and encrypted at rest. Each project can only be seen by its own team, which our database enforces, and each project has its own key, destroyed when the project is deleted. Everything is sent over encrypted connections.

Cookies

We only use the cookies needed to sign you in. See our cookie policy.

Children

Revive Code is a service for businesses and isn't intended for anyone under 18.

Changes to this policy

We'll update this page when anything changes, and email you before any significant change takes effect.