This policy explains how we handle personal data when you use lintl. It is written for busy people in small practices. If something here conflicts with a signed data processing agreement, that agreement wins for the processing it covers.
Exact retention periods and cookie detail will be tightened near launch once account, payment and support setup are final.
1. Who this is for
lintl is a browser workspace that helps UK residential architects with planning research, site context, feasibility framing and early project work. It is not a substitute for your professional judgement.
If you upload client materials, you remain responsible for having a lawful reason to do so. For that content we usually act as your processor (see our data processing terms).
2. What we collect
**Account:** email address, authentication details, organisation id if set, display preferences.
**Workspace use:** chat messages and tool results, session titles and metadata, property context you attach (such as address, postcode, UPRN), files you upload or that the assistant generates for you, usage and billing meter events.
**Technical:** IP address and device/browser signals via hosting and security logs, cookies and local storage needed to keep you signed in and remember UI settings.
We do not ask for special category data (for example health). Please do not put that in prompts or files.
3. Why we use it
| Why | Basis |
|---|---|
| Run your account and the workspace | Contract |
| Look up property and planning context you ask for | Contract |
| Meter usage and manage allowances | Contract |
| Keep the service secure and investigate abuse | Legitimate interests |
| Meet legal duties (for example tax records when billing is live) | Legal obligation / legitimate interests |
We do not sell your personal data.
4. AI and your content
Messages and files you provide are processed to return results in the product. We use cloud AI and data providers listed in section 5.
**We do not treat day-to-day use as permission to train foundation models on your practice content, or to take ownership of your work.** Any later programme where architects opt in to verification contributions will be described separately and will stay voluntary.
Amazon Bedrock — model provider retention
For foundation models on Amazon Bedrock, we configure AWS account data-retention settings so that, **where the model allows it**, prompts and responses are **not retained** by AWS / the model provider after the request (zero data retention / `mode=none`).
Some models **require** the provider to retain or share prompts (for example certain frontier models). Those models are labelled in the product (for example under Settings → Models). Before you can use one, we ask you to accept a clear notice. If you decline, that model stays unavailable and other models continue under the stricter retention setting.
Your chats, files, and account data that lintl stores for the product remain in our application storage (see section 6). That is separate from Bedrock’s inference retention settings.
Outputs can be wrong or incomplete. See the AI and property disclaimer.
5. Who we share with
We use service providers to run lintl, including:
- Amazon Web Services (hosting, auth, storage, logging, AI inference and runtime)
- Google (Places and map-related APIs we call for address and map features)
- PropertyData and Ordnance Survey (UK property and mapping lookups)
- Other research tools you enable in the product (for example web search tools)
These providers only get what they need to do their job. Some may process data outside the UK. Where that happens we rely on appropriate transfer safeguards.
We may disclose data if the law requires it, or to protect rights, safety or the integrity of the service.
6. Where data is stored
The live lintl application stack is hosted in Europe (UK/EU regions) on Amazon Web Services. Durable chats, files, and account preferences stay there.
If you choose a **USA-hosted** model, prompts and responses for that turn are **processed in the United States** for inference. We tell you before the first use of those models. Some sub-processors may also operate elsewhere. Ask us if you need a current list for a client questionnaire.
7. How long we keep it
We keep account, chat, file and usage data while you use lintl and for a sensible period after you stop, so the product works and we can handle support, security and (when live) billing duties. Fixed public deletion timelines will be published here before relaunch.
Until self-serve export and account closure are available, email us to request access, correction or deletion and we will help manually where we can.
8. Sharing with your practice
If you share a file with your practice (when that feature is available), other members of your organisation can see it. Do not share client material more widely than your own policies allow.
9. Your rights
Under UK law you can ask to access, correct, erase, or restrict personal data, object to some processing, and ask for portability where it applies. You can also complain to the Information Commissioner’s Office (ico.org.uk).
To exercise rights: gareth@flyingriverlabs.com.
10. Cookies
We use cookies needed to run the service (sign-in, security, basic display choices). We do not currently use advertising or third-party analytics cookies. See the cookie notice.
11. Children
lintl is for professional use. It is not directed at children.
12. Changes
We will update this page when the product or the law changes. Material changes will be highlighted in the app or by email when we can.
13. Contact
Flying River Ltd (trading as lintl) gareth@flyingriverlabs.com United Kingdom