The short version
- When personal data is in what you send us, you decide what's processed and why, and we process it only on your instructions.
- It's part of the Terms of service, so it applies without a signature. Email us if you need a signed copy.
- The service is hosted in the United States. Transfers out of the EU, UK and Switzerland are covered by the standard contractual clauses.
- We list every subprocessor below and give 30 days' notice before adding one, so you can object.
- We tell you about a breach affecting your data without undue delay, and delete your data within 30 days of your account or team ending.
This summary is for convenience. The full text below is what applies.
What this agreement covers
This Data processing agreement ("DPA") is between you, the customer, and Inference Bureau ("we", "us"). It is part of the Terms of service and applies whenever we process Customer personal data for you. It needs no signature: agreeing to the Terms is agreeing to it. If you need a copy signed by both of us, email hello@inferencebureau.com.
"Customer personal data" is personal data in the content you or your users send through the service, or that you connect it to: prompts, files and outputs; code, pull requests and issues Auditor reads; records, files and logs of apps you build on Inference Bureau, including what they sync from Shopify stores; and the end-user IDs your application sends. "Data protection law" means the laws that apply to that processing, including the EU GDPR, the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, and US state privacy laws such as the CCPA. Words such as controller, processor, data subject and personal data breach have the meanings those laws give them.
Roles
For Customer personal data, you are the controller (or a processor acting for your own customer) and we are your processor (or subprocessor). You're responsible for having a lawful basis to send us the data and for giving people any notices the law requires.
The details we keep about your account, team, sign-ins, usage and billing are ours to run the business, and the Privacy policy covers them, not this DPA.
What we process
- Purpose. Providing the service you use: routing requests to model providers and returning their answers, applying your Directives and budgets, keeping Logs and stored responses when you turn them on, reviewing code and issues with Auditor, and running, storing and syncing data for your apps.
- Data subjects. Whoever your content is about: your staff and users, your customers and end users, and, for apps connected to Shopify, the merchants who install them and those merchants' customers.
- Kinds of data. Whatever you choose to send or connect. Typically names, contact details, account identifiers, order and customer records, messages and free text. Don't send special-category data, or data the Terms say the service isn't meant for, unless we've agreed it in writing.
- How long. For as long as you use the service, and then until it's deleted as described under Deletion and return.
Your instructions
We process Customer personal data only on your documented instructions. These are the Terms, this DPA, the settings your team chooses (such as Directives, Log content and an app's code) and the requests you make. If we think an instruction breaks data protection law, or a law requires us to process data otherwise, we'll tell you first unless that law forbids it.
We don't sell Customer personal data, share it for cross-context advertising, or use it to train models or for any purpose of our own, and we don't combine it with data from other customers except as needed to run the service.
Confidentiality and security
Everyone at Inference Bureau who can reach Customer personal data is bound to keep it confidential, and only people who need it to run or support the service have that access.
We keep appropriate technical and organizational measures in place to protect it, including:
- encryption in transit (TLS) for all connections, and encryption of request content kept by Log content, stored integration tokens and app secrets, with keys specific to each team where the Privacy policy says so;
- passwords and API keys stored only as hashes, two-factor sign-in and passkeys for accounts, and roles that limit what each team member can see;
- isolation between teams, and between apps' environments, in the database, file storage and build environments;
- request content not stored at all unless Log content is on, and then only for 7 or 30 days;
- backups, monitoring and logging of access to production systems, with access limited to the people who need it.
We may update these measures as long as they don't become less protective.
Subprocessors
You authorize us to use the subprocessors below. Each is bound by a written agreement that protects Customer personal data at least as well as this DPA, and we remain responsible to you for what they do.
- Vercel (United States): hosting, scheduled jobs, file storage, build environments and delivering requests to model providers
- Neon (United States): the database
- Upstash (United States): caching and background job queues
- Cloudflare (global network): DNS, custom domains and request routing for apps and theme sites hosted on Inference Bureau
- Resend (United States): sending email on our behalf, including the sign-in emails and team invitations we send for an app that hasn't connected its own email provider
- Model providers: the provider each request is routed to, as listed on the Providers page. Your routing and Directives decide which ones receive your content; Require ZDR and Require no training limit them to providers that have made those commitments.
- GitHub, Shopify, Linear, Jira and Slack: only when you connect them, and only to do what you connected them for.
An app's own integrations, such as a Resend or Sentry account your team adds to it, are your providers, not ours. Until your team connects its own email provider to an app, we send that app's sign-in emails and team invitations to its users through Resend for you, as your processor: the recipient's address, the app's name and the email's link, and for an invitation the team's name and who sent it. We log each one, and any bounce or spam complaint, in the app's Logs, kept for your plan's retention.
We'll give at least 30 days' notice before adding or replacing a subprocessor, on this page and by email to your team's owners. If you object on reasonable data protection grounds, tell us within that time and we'll work with you on an alternative; if we can't find one, you can end the affected service and we'll refund any prepaid balance for it that you haven't used.
Where data is processed
The service is hosted in the United States, and Customer personal data is stored there. Model providers may process a request in the region they serve it from.
When Customer personal data is transferred from the European Economic Area, the UK or Switzerland to a country without an adequacy decision, the transfer is made under the European Commission's standard contractual clauses (Decision 2021/914), which are incorporated into this DPA by reference:
- Module two (controller to processor) applies where you are a controller, and module three (processor to processor) where you are a processor.
- In clause 7, the docking clause applies. In clause 9, option 2 applies, with the notice period above. In clause 11, the optional language does not apply.
- In clause 17 and clause 18, the clauses are governed by the law of, and disputes are resolved by the courts of, Ireland.
- Annex I is the information under Roles and What we process, with you as data exporter and us as data importer. The competent supervisory authority is the one clause 13 points to. Annex II is the measures under Confidentiality and security. Annex III is the list under Subprocessors.
- For transfers from the UK, the UK International Data Transfer Addendum applies alongside the clauses. For transfers from Switzerland, the clauses apply with references to the GDPR read as the Swiss Federal Act on Data Protection, and the Swiss Federal Data Protection and Information Commissioner as a competent supervisory authority.
If you need Customer personal data hosted in the EU, write to us and we'll tell you what we can offer.
Helping you meet your obligations
- Data subject requests. Your team can find, export and delete Customer personal data in the console, the API and your apps. If a person writes to us about data we process for you, we'll pass the request to you and not answer it ourselves unless you ask us to. Apps connected to Shopify receive Shopify's customer data request and redaction webhooks, and run your app's handlers for them.
- Assessments. We'll give reasonable help with data protection impact assessments and consultations with supervisory authorities about the service, using the information we have.
- Government requests. If a public authority asks us for Customer personal data, we'll ask it to come to you, tell you about the request unless the law forbids it, and disclose only what we're legally required to.
Personal data breaches
If we become aware of a personal data breach affecting Customer personal data, we'll tell your team's owners without undue delay, and within 72 hours where we can. We'll say what happened, what data and people are affected as far as we know, and what we're doing about it, and we'll keep you updated as we learn more. Telling you isn't an admission of fault.
Audits
We'll answer your reasonable security and privacy questionnaires and give you the information you need to show that we meet this DPA. If that isn't enough, or a supervisory authority requires it, you may audit our compliance once a year, with 30 days' written notice, during business hours, at your cost, through an auditor bound to confidentiality, and in a way that doesn't put other customers' data at risk. Audits of our subprocessors are done through the reports and certifications they publish.
Deletion and return
You can export your data from the console and the API at any time while your account exists. When your account or team ends, or you ask us to, we delete Customer personal data within 30 days, and it leaves our backups as they expire within a further 30 days, unless the law requires us to keep it. Deleting an app or an environment, or turning off Log content, deletes what it held in the same way. When Shopify asks an app to redact a store's data, 48 hours after the store uninstalls it, we delete the store's records that the app keeps on Inference Bureau; customer data your app keeps elsewhere is for your app's handlers to delete.
Liability and order of precedence
Each party's liability under this DPA is subject to the limits in the Terms, to the extent data protection law allows. Nothing in this DPA limits a data subject's rights under the standard contractual clauses.
If this DPA conflicts with the Terms, this DPA wins for Customer personal data. If it conflicts with the standard contractual clauses, the clauses win.
Changes to this agreement
We may update this DPA when the law or the service changes, and will update the date at the top. We won't make a change that lowers the protection of Customer personal data without your agreement, except to comply with the law or a supervisory authority.
Contact
Questions about this agreement, a signed copy, or a data request: hello@inferencebureau.com.