Privacy Policy
Effective 19 August 2026 · Last updated 19 August 2026
This policy explains what personal information Foundry collects, why, who it is shared with, and what rights you have over it. It covers both the businesses who use Foundry and the people whose details those businesses store in it.
1.Who we are
Foundry is operated by [TODO: Legal entity name, e.g. Foundry Software LLC], [TODO: Street, City, State ZIP, Country]. You can reach us about anything in this policy at [TODO: privacy@yourdomain.com].
Foundry is a customer relationship tool for service businesses. It receives enquiries, prompts a business to call them quickly, records what happened, and sends quotes.
2.Who this policy is for
- Customers — the businesses and their staff who hold accounts with us.
- Leads — the people whose enquiries a customer stores in Foundry, and who never signed up with us themselves.
- Visitors — anyone opening a quote link we host on a customer’s behalf.
3.Our two different roles
This distinction decides who is responsible for what, so it is worth being precise about.
- For customer account data — the email address you sign up with, your settings, your billing details — we are the controller. We decide why and how it is used, and this policy governs it.
- For lead data — the names, phone numbers, addresses and enquiries a customer puts into their workspace — we are a processor (a “service provider” under California law). The customer is the controller. We act on their instructions, we do not decide what that data is used for, and we do not use it for our own purposes.
Customers subject to GDPR, UK GDPR or similar laws should have a data processing agreement with us. Ask at [TODO: privacy@yourdomain.com] and we will provide one.
4.What we collect
From customers, directly:
- Email address and a password, which is stored only as a salted hash by our authentication provider and is never visible to us.
- Business name, public phone number, sending and reply-to email addresses, and your response targets.
- Your price list and quote wording.
- Device details for push notifications: the browser endpoint, its encryption keys and a label you choose.
About leads, entered by a customer or received on their behalf:
- Name, phone number, email address and service or property address.
- The enquiry itself, in the words the person used.
- Where the enquiry came from — for example a Meta lead ad, including the campaign and ad set name.
- A record of contact attempts: when a call was placed, whether it was answered, and notes typed by the business.
- The content of texts and emails sent through the service.
- Quotes: line items, prices, totals, and when a quote was opened, accepted or declined.
If you connect a mailbox: the email address of the account you connect, its display name, and access and refresh tokens. Tokens are encrypted before storage. We request permission to send mail only. We cannot read your inbox, and we do not ask for permission to.
Automatically: ordinary server and security logs including IP address, browser type, pages requested and timestamps. We do not use advertising cookies or third-party analytics trackers. The only cookies we set are those required to keep you signed in and to protect against cross-site request forgery.
5.Why we use it, and our legal basis
- To provide the service — showing your leads, sending the messages you send, hosting quote pages. Basis: performance of a contract.
- To keep the service secure and working — logging, abuse prevention, debugging. Basis: legitimate interests.
- To contact customers about service changes, security matters and billing. Basis: contract and legitimate interests.
- To meet legal obligations — tax records, lawful requests. Basis: legal obligation.
We do not sell personal information, and we do not share it for cross-context behavioural advertising. We have never done so.
We do not use your lead data to train machine learning models, and we do not permit our providers to do so on our behalf.
6.AI drafting
When you use the feature that drafts a suggested text or email, the details needed for that draft — typically the lead’s first name, their enquiry, your business name and the stage of the job — are sent to Anthropic to generate the suggestion. Nothing is sent unless you use the feature.
Drafts are suggestions. Nothing is sent to a lead until you choose to send it.
7.Who we share it with
We use the following providers to run the service. Each is bound by contract to protect the data and to use it only to provide their service to us.
| Provider | Purpose | Location |
|---|---|---|
| Supabase | Database, authentication and file storage for all account and lead data | United States |
| Vercel | Application hosting, request logs and content delivery | United States |
| Resend | Sending email on your behalf when you have not connected your own mailbox | United States |
| Twilio | Sending SMS to the leads you choose to text | United States |
| Anthropic | Drafting suggested message text when you use the AI drafting feature. Lead details you include are sent to generate the draft. | United States |
| Only if you connect a Gmail account: sending mail through your own mailbox | United States | |
| Microsoft | Only if you connect an Outlook account: sending mail through your own mailbox | United States |
| Meta Platforms | Only if you connect Meta lead ads: receiving the leads your ads generate | United States |
We may also disclose information where required by law, to enforce our agreements, or to protect the rights and safety of any person. If our business is sold or merged, information may transfer to the buyer under this same policy.
8.Messages we send on your behalf
When a customer sends a text or an email through Foundry, the recipient’s details are passed to the provider that delivers it. Quote links we host contain a random token; anyone holding that link can view the quote it belongs to, so treat it as confidential. Quote pages are not indexed by search engines.
9.Google user data (Limited Use)
If you connect a Gmail account, Foundry’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically:
- We request only the ability to send mail on your behalf, plus your email address so we can show you which account is connected. We do not request, and cannot obtain, permission to read your messages.
- Google user data is used solely to send the messages you choose to send from within the product.
- We do not transfer Google user data to third parties except as necessary to provide the service, to comply with applicable law, or as part of a merger or acquisition.
- We do not use Google user data for advertising, and we do not sell it.
- We do not allow humans to read Google user data except with your explicit permission, where necessary for security purposes such as investigating abuse, or to comply with applicable law.
You can disconnect a mailbox at any time in Settings, which deletes the stored tokens. You may also revoke access directly from your Google account’s security settings, or your Microsoft account settings for a connected Outlook mailbox.
10.How long we keep it
- Lead data, messages and quotes are kept for as long as the customer's account is active, because the record of who was contacted and when is the point of the product.
- When an account is closed, its data is deleted within 30 days, except where we must keep records to meet a legal obligation.
- A customer can delete an individual lead at any time, which removes its activity, stamps and quotes.
- Disconnecting a mailbox deletes its stored credentials immediately.
- Server logs are retained for a short period for security and debugging, typically no more than 30 days.
11.How we protect it
- All traffic is encrypted in transit with TLS. Data is encrypted at rest by our hosting providers.
- Mailbox credentials are additionally encrypted by us with AES-256-GCM before they are stored, so a copy of the database alone does not yield usable credentials.
- Each workspace's data is isolated at the database level by row-level security, so one customer's queries cannot reach another customer's records.
- Access to production systems is limited to those who need it.
No system is perfectly secure. If a breach affects your personal information we will notify you and any regulator as the law requires.
12.Your rights
Depending on where you live you may have the right to access, correct, delete, port or restrict the use of your personal information, to object to certain processing, and to withdraw consent. Californian residents additionally have the right to know what is collected and to opt out of sale or sharing — we do neither.
We will not discriminate against you for exercising any of these rights.
To exercise them as a customer, write to [TODO: privacy@yourdomain.com]. To exercise them as a lead, contact the business holding your details; we will assist them but cannot act on their data without their instruction. We respond within the period the applicable law requires, and within 30 days where none is specified.
If you are in the EEA or UK and are unhappy with our response, you may complain to your local supervisory authority.
13.International transfers
We and our providers are based in the United States, so information is stored and processed there. Where data is transferred out of the EEA or UK, we rely on the European Commission’s Standard Contractual Clauses or another lawful transfer mechanism.
14.Children
Foundry is a tool for businesses and is not directed at children. We do not knowingly collect personal information from anyone under 16. If you believe a child’s information has reached us, write to [TODO: privacy@yourdomain.com] and we will delete it.
15.Changes to this policy
We will post any change here and update the date at the top. If a change materially affects how we handle personal information, we will notify customers by email before it takes effect.