Legal
Privacy Policy
In short
- We use your account details to sign you in and run your workspace. We don't sell personal data, and we don't use it for advertising.
- What your team builds and connects in a workspace belongs to your organisation. We process it on their behalf, to run the service.
- Each workspace runs in its own isolated environment, hosted in the EU (Germany).
- Google files you link are read only, only the ones you pick, and never used to train AI or for advertising.
- AI features send what's needed to AI model providers to get an answer. We don't use your content to train AI models.
- You can see, correct, export or delete your data. Write to hello@ourforge.app.
The summary is for convenience. The sections below are what apply.
Who we are
Forge is a service for building internal tools by describing them to an AI. It is provided by Purdy & Figg Ltd, a company registered in England and Wales (company number 12477148), whose registered office is at 9 Heron Business Park, Eastman Way, Hemel Hempstead Industrial Estate, Hemel Hempstead, England, HP2 7FW ("Forge", "we", "us").
This policy explains what personal data we handle when you use Forge: the website at ourforge.app, your account, and the workspaces you belong to (each at its own address, such as yourcompany.ourforge.app). It also explains your rights.
Our two roles
- Controller
- For your account: who you are, how you sign in, which workspaces you belong to, and how you use Forge. We decide how this data is used, and this policy covers it fully.
- Processor
- For workspace content: the apps your team builds, the data sources it connects, and the data that flows through them. That belongs to the organisation that owns the workspace, which is the controller. We process it only on their instructions, to provide the service, under the data processing addendum in our Terms of Service. If you have questions about that data, ask your organisation first. We'll help them answer.
If you use Forge on your own rather than for an organisation, you are the owner of your workspace, and we handle its content only to provide the service to you.
You give us
- Account details from signing in with Google: your name, email address and profile picture.
- Workspace details: workspace names, who belongs to which workspace, roles (viewer, builder, admin), invitations, requests to join, and requests for a different role, with any note you add.
- What you build: app descriptions and code, your conversations with Forge's in-browser builder, app settings, documentation you upload, and descriptions you write for a data source's map.
- What you connect: details for APIs and databases an admin connects (addresses, settings, and the keys or passwords, which we store and use only to make the connection), Google Sheets and Docs you choose to link, and Shopify stores an admin connects.
- Messages you send us, such as support requests.
We record as you use it
- Activity in a workspace: which apps were opened and when, changes to apps, publish requests and approvals, and the audit log of reads from connected sources (which app or person, which source, when, whether it worked). For database queries we record the query, never its parameter values.
- AI usage: which features were used, the model, the number of words processed and the cost, so a workspace can stay within its plan's monthly allowance.
- Technical data: IP addresses, browser type and request logs, kept for security and to keep the service running.
From others
- Google, when you sign in (name, email, picture) and, if you connect your Google account, the files you pick (see section 4).
- Shopify, if an admin connects your organisation's store: the store's name, and whatever apps built in the workspace read from it (orders, products, stock, refunds and customers). Forge only reads; it can't change anything in the store. If Shopify passes on a customer's or store's request to see or delete their data, we act on it within 30 days.
- Your organisation, when an admin invites you, gives you a role, or connects a data source.
We don't ask for special categories of personal data (such as health or beliefs), or data about criminal convictions. Our customers agree not to put either into Forge without our written agreement.
UK data protection law (the UK GDPR) requires a lawful basis for each use. These are ours:
| What we do | Why we may |
|---|---|
| Create your account, sign you in, and run the workspaces you belong to | To perform our contract with you or your organisation |
| Build, host and run apps, and connect them to the sources your workspace chooses | To perform the contract; for workspace content, on your organisation's instructions |
| Keep the service secure: detect abuse, investigate incidents, keep audit logs | Our legitimate interest in a safe, reliable service, and your organisation's in knowing what its apps do |
| Count AI usage against a plan's allowance, and bill for paid plans | To perform the contract |
| Answer support requests and send messages about the service (security notices, changes to these terms) | To perform the contract, and our legitimate interest in keeping you informed |
| Improve the service from how it's used overall (for example, which features fail most often) | Our legitimate interest, using activity data, not the content of your apps or data |
| Comply with law, and respond to lawful requests | Legal obligation |
We don't sell personal data, use it for advertising, or make decisions about you by automated means that have legal or similarly significant effects.
You sign in to Forge with your Google account. Separately, you can choose to connect your Google account so you can use your own Google Sheets and Docs in apps.
What we can reach
When you connect, we ask Google for one permission beyond sign-in: access to the files you pick (Google calls it “drive.file”). You choose files one at a time in Google's own file picker. We can't see, list or open anything else in your Google Drive.
How we use it
- We only read the files you pick, to show their contents in apps you or an admin attach them to, and to draw a map of their structure (tabs and column names) so apps can be built correctly. We never change, move, share or delete them.
- An app reads a file on our servers and shows people what the app is built to show. The file itself isn't shared with them, and they don't need access to it in Google.
- The file's actual contents are shown only to you: other people working on apps see its structure, not its values.
- Your Google connection is stored encrypted, and used only for the files you linked. You can disconnect at any time in Forge (Integrations → Your Google files), or remove Forge's access in your Google account settings. Either stops all reads.
Forge's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In particular, we do not use data from Google's APIs for advertising, do not sell it, do not use it to train AI models, and do not let people read it except with your permission, for security, or to comply with law.
AI features
Forge uses AI models in two ways.
- The in-browser builder: when you describe an app, we send your conversation, the app's code, and the maps of the data sources it uses to an AI model to produce the app. Real values from a database or sheet are sent only in limited samples, with columns marked as personal data hidden, and a Google file's values only when you are its owner. The model is chosen by Forge and reached through OpenRouter, which passes the request to the model's provider (see section 6).
- Suggested descriptions for a data source's map: we send an outline of its structure (names and types, not its data) and short extracts of documents you uploaded.
- Your own AI assistant: if you connect an assistant such as Claude to Forge, what you share with it is governed by your agreement with its provider. Forge gives it only what you or your role may see.
We don't use your content or your data to train AI models.
AI output can be wrong. Review apps before relying on them (see our Terms of Service).
Workspaces are hosted in the EU, which the UK recognises as protecting personal data adequately. Some of our providers are in other countries, including the USA. When data goes outside the UK, we rely on the UK's adequacy regulations (including the UK Extension to the EU–US Data Privacy Framework, where a provider is certified), or on the UK International Data Transfer Agreement or Addendum, with the safeguards they require. Contact us for a copy of the relevant safeguards.
If your organisation is in the European Economic Area, its data comes to us in the UK under the European Commission's adequacy decision for the UK, and any onward transfer uses the EU's standard contractual clauses where needed.
| Data | Kept |
|---|---|
| Your account | While you have one. When it's closed, deleted within 30 days, apart from what we must keep by law. |
| Workspace content | While your organisation's licence lasts. When it ends, your organisation can ask to export it for 30 days; after that we delete it, unless the law requires us to keep it. |
| Backups | Up to 30 days, then overwritten. A closed workspace's backups are gone within 30 days of its export period ending. |
| Audit logs of reads from connected sources | 30 days. |
| Your Google connection | Until you disconnect, or remove access at Google. Then deleted immediately. |
| A Shopify store connection | Until an admin disconnects it, or the store removes Forge in Shopify. Then the connection stops working at once and is deleted on disconnect. |
| AI usage records | For as long as needed to account for the plan and its billing. |
| Technical logs | Short periods for security, usually days. |
| Messages to us | As long as needed to deal with them, and up to two years after. |
- Every workspace runs in its own isolated environment, with its own database and network rules that stop one workspace reaching another.
- Data at rest, including workspace databases, backups and shared files, is encrypted (AES-256 or equivalent).
- Connections are encrypted in transit. Keys, passwords and Google connections for data sources are held by Forge and never handed to the apps that use them; Google connections are also encrypted at rest.
- Databases are read only through Forge, with every query checked; apps read connected sources through Forge, which logs each read.
- Access is limited to the people who need it, and actions in a workspace are recorded.
No system is perfectly secure. If a breach affects workspace content, we tell the organisation it belongs to within 48 hours of finding out, and help it meet its own duties. If a breach affects your account, we'll tell you and the authorities when the law requires it.
Your rights
Under UK data protection law you have the right to:
- Access your personal data and receive a copy
- Correct data that's wrong
- Erase your data
- Restrict or object to how we use it, including where we rely on legitimate interests
- Port data you gave us, in a common format
- Withdraw consent, where we rely on it
To use any of these, write to hello@ourforge.app. We'll reply within a month. For data in a workspace, your organisation is the one to ask: if you write to us, we'll pass your request to them and help them respond.
If you're unhappy with how we handle your data, please tell us first. You can also complain to the UK's Information Commissioner's Office at ico.org.uk or on 0303 123 1113.
Children
Forge is for people aged 18 and over, and isn't directed at children. If you think a child has given us personal data, contact us and we'll delete it.
We'll update this policy when Forge changes how it handles data, and change the date at the top. If a change matters to you, we'll tell you in Forge or by email before it takes effect.
Contact
Questions, requests or complaints about privacy: hello@ourforge.app.
By post: Purdy & Figg Ltd, 9 Heron Business Park, Eastman Way, Hemel Hempstead Industrial Estate, Hemel Hempstead, England, HP2 7FW.