Privacy Policy

This Privacy Policy explains how Dattuh collects, uses, discloses, and protects information when you use the Dattuh application (the "App"), which integrates with QuickBooks Online (QBO) via Intuit's APIs. It also explains how we handle operational and production log data generated when the App runs.

Information We Collect

We collect the following types of information:

  • QBO Account Data: When you authorize the App via OAuth (Open Authorization, an industry-standard protocol that lets you grant the App access to your QBO account without sharing your password), we access specific QBO data as permitted by your consent (for example: customers, vendors, payment methods, payment terms, classes, locations, sales taxes, and similar information). We only access what is necessary for the App's features. Client's OAuth tokens are encrypted in the database. When your task finishes processing, this data is deleted from our systems.
  • Account and Usage Information: We collect your name, email, address, company name, App usage data (e.g., login times, features used), and other relevant technical data to provide services on your behalf and for billing purposes.
  • Transactions: We store limited transaction metadata (ID/DocNumber, date, amount, document name) to provide information to clients, to support status tracking, and to allow clients to reverse transactions if needed*.
  • Third-party data files: We store the data files you upload in Amazon S3 cloud storage so you can review and re-run them, and delete them automatically after 90 days, or sooner if your account's admins choose a shorter period (30 or 45 days).
  • Operational and Production Logs: We collect technical and diagnostic records generated by the App, such as timestamps, request and job activity, internal record IDs, integration IDs, document names, file extensions, status values, counts, and error details needed to operate, secure, and troubleshoot the service. We do not log uploaded file contents, OAuth tokens, or full QuickBooks payloads, but logs may include limited exception or validation messages when needed to diagnose failures.
  • AI-Assisted Integration Requests: When you use the AI-assisted integration creation feature, your natural-language prompt and relevant structural context — such as sample file column names, an anonymized sample of the file's rows (the same kinds of values, with every value replaced by an invented one), QBO account metadata, field names, chart of accounts — are sent to our AI provider, Anthropic, to generate an integration specification. Your actual file rows, OAuth tokens, and raw QuickBooks payloads are not sent to AI providers for this purpose. The actual processing and integration of your data into QBO is performed entirely by automated app logic using the approved integration specification — not by AI. The sole exception is when AI-assisted technology is used to read PDF files; in that case, you will be notified before processing proceeds.
  • Google Sheets: If you connect a Google account, we read only the spreadsheets you choose, to run your integrations. See Google User Data below.
  • Other Data: Support requests or other information you voluntarily provide.

Use of Integration Metadata for AI Improvements

We may use non-personal integration metadata (i.e., mapping configurations, field mappings, anonymized usage patterns, error and validation patterns, and other structural metadata) to improve automated tooling and AI-assisted features that help create and diagnose integrations. This usage is limited to metadata and aggregated insights — we do not use uploaded file contents, OAuth tokens, or raw QuickBooks Online account data for training or to improve our models.

Data from Google (see Google User Data), including a spreadsheet's column names, is never used for this, whatever this setting.

Dattuh uses a client's integration metadata for these improvements only if the client opts in. A client admin can opt in, or later opt out, with the "Let Dattuh use this client's integration builds to improve the agent" setting on the client's account in the App, or when starting an integration that Joe, our AI assistant, builds. New clients are not opted in. Not opting in doesn't affect the App's core integration functionality.

When a client hasn't opted in, Dattuh's staff can't view its integration interviews, the agent's runs, or its conversation with Joe while Joe builds an integration. If the client asks to bring in the Dattuh team during a build, that request gives Dattuh's staff permission to view them for that integration only. Dattuh's staff still handle what a build needs set up, such as a new data source or a sample file the App couldn't read.

AI-Assisted Integration Creation

When you explicitly request a new integration using Dattuh's AI-assisted workflow, we process your request using a third-party AI provider (or providers, which may change over time) to generate an integration specification. The following applies to this feature:

  • This feature is opt-in: it is only triggered when you explicitly initiate a new integration creation request.
  • We send your natural-language prompt and relevant structural context — such as your sample file's column names and an anonymized sample of its rows (the same kinds of values, with every value replaced by an invented one), and QBO account metadata (e.g., field names, chart of accounts) — to our AI provider, Anthropic, to produce the specification.
  • We do not send your actual file rows, OAuth access or refresh tokens, or complete QuickBooks payloads to AI providers for this purpose.
  • The generated specification is a starting point and may be reviewed or edited before use. No new integration is placed into production until you explicitly review and approve it.
  • The actual processing and integration of your data into QuickBooks Online is performed entirely by automated app logic using the approved integration specification — not by AI. AI is not involved in reading, transforming, or submitting your data to QBO during the integration run.
  • The only exception to the above is when AI-assisted technology is used to extract data from PDF files. When this occurs, you will be shown a warning and given the opportunity to proceed or cancel before any PDF content is sent to an AI provider.
  • Under Anthropic's commercial terms, Anthropic does not use this data to train its models and deletes it within 30 days, keeping it longer only if required by law or, if its automated systems flag it as violating its Usage Policy, for up to 2 years. The AI providers we use may change over time; we will update this policy as material providers change.

Messages and Joe, Dattuh's AI Assistant

Messages. Your account's admins can message Dattuh from the Messages page, in the App or by replying to our emails. We keep these conversations, with who wrote each message and when, for as long as your account exists, as part of your support history. Replies you send by email are received by our email provider, Resend; we keep the original email for up to 30 days to process it, then delete it, and keep only the reply's text in the conversation. A Dattuh team member can see a conversation only after one of your admins brings them in, with two exceptions. While Joe's replies are reviewed, the reviewer sees Joe's draft and the messages it answers, and nothing else of the conversation. And when a sync fails for a reason Dattuh has to fix, a Dattuh team member may start a conversation with your admins about it: they see that conversation and your replies in it, and about the sync only its number, its integration and how many rows failed in which way, never the rows themselves. Each time a team member opens a conversation is recorded.

Joe, Dattuh's AI assistant. When you ask Joe a question, Joe uses Anthropic's Claude, through Anthropic's API, to read and answer. For each answer we send Anthropic:

  • the conversation's messages;
  • a summary of the integrations and tasks it concerns: their names, status, setup checklist, whether their connections are working, and each task's row counts and the kinds of failure (for example, "a customer isn't in QuickBooks"); and
  • in a conversation about an integration interview, your answers to the interview and the notes Dattuh's integration agent made on the draft integration it built from them (its questions for you, its assumptions and the reminders it proposed).

Joe does not look up, and we do not send, your uploaded files' rows, your customers' or vendors' names, transaction details or amounts, your QuickBooks data or login tokens, or other clients' information. What you write in the conversation is sent as you wrote it, so if you type a customer's name or an amount there, it's included; there's no need to, since Joe works from your task's counts and the kinds of failure.

Under Anthropic's commercial terms, Anthropic does not use this data to train its models, and deletes it within 30 days. It keeps it longer only if required by law, or, if its automated systems flag it as violating its Usage Policy, for up to 2 years. We do not opt in to any program that shares your data with Anthropic for training, and we never send them your content as feedback. Anthropic's privacy policy is available at https://www.anthropic.com/legal/privacy.

What Joe can do. Joe reads and explains how Dattuh and your integrations work and why a task did what it did; he cannot change your integrations, settings or tasks, sync or reverse anything, or reach another client's information. Joe does not give accounting, sales tax or other tax, legal, or general business advice — for example, how to categorize a transaction, whether something is taxable or at what rate, or how to run your business; for those, consult a qualified accountant, CPA or tax advisor. A Dattuh team member reviews his replies before you see them, until we judge a kind of reply reliable enough to send automatically; we may change this over time. Joe can suggest bringing in the Dattuh team, and the Dattuh team sees the conversation only if one of your admins approves.

Joe's working records. To review, troubleshoot and improve Joe, we keep a record of each answer he works on (the instructions he was given, what he looked up and what it returned) for 90 days, then delete it. The conversation itself is kept as described above.

Your choice. Joe is one way to get help; you can always bring in the Dattuh team instead.

How We Use Your Information

  • Provide and improve the App's integration features.
  • Authenticate and manage your QBO connection (OAuth token rotation).
  • Communicate updates, support requests, and job status.
  • Detect and prevent abuse, fraud, or security incidents.
  • Monitor system performance, investigate bugs, diagnose failed jobs or integrations, and maintain reliable production operations.
  • Comply with legal obligations and enforce our agreements.

We do not use your QBO data for unrelated marketing or profiling without explicit consent.

Emails We Send

We send three kinds of email:

  • Service emails, needed to run your account: sign-in and security, billing and receipts, task results, and changes to our terms. You receive these while you have an account.
  • Product updates, about new features and changes to Dattuh. We send these to our customers because they're about the service you use, and we have a legitimate interest in keeping you informed about it. You can turn them off at any time.
  • News and offers, only if you ask for them, for example by ticking the box when you sign up or turning them on in your account.

Every product update and news email has a one-click unsubscribe link, and you can change your choices on your account page at any time. We act on an unsubscribe immediately. We keep a record of each choice you make (what you chose, when, and how) to show we have your consent, and delete it if your account is deleted. We never sell or share your email address for anyone else's marketing.

Data Sharing and Disclosure

We do not sell your data. We may share information with:

  • Service providers (such as hosting, infrastructure, storage, email, and analytics vendors) who may process application data or operational logs on our behalf and who are contractually bound to protect the data.
  • Authorities if required by law or to protect rights and safety.
  • In connection with a merger or sale of assets (with notice as required).

We never ever share a customer's data with another customer. Any aggregated or anonymized insights will comply with Intuit guidelines and applicable law.

Service Providers and Infrastructure

We use third-party providers to host, operate, secure, and support the App. These providers may process personal data or operational log data only as needed to perform services for us.

  • Anthropic, PBC: Provides the Claude AI models behind Joe, Dattuh's AI assistant, and the AI-assisted integration creation feature, through its API under commercial terms. Anthropic does not train on this data and deletes it within 30 days, except as its policies allow for legal requirements or Usage Policy enforcement. Anthropic's privacy policy is available at https://www.anthropic.com/legal/privacy.
  • Resend / Plus Five Five, Inc.: Used to deliver our emails (service emails, contact-form messages, product updates, and news you've asked for) and to receive replies you send to our emails. Resend's privacy policy is available at https://resend.com/legal/privacy-policy.
  • Render / Render Services, Inc.: Used to host and run the application, serve the website, maintain backups, and support operational logging and security controls. Render's privacy policy is available at https://render.com/privacy.
  • Amazon Web Services (AWS) / Amazon S3: Client data files you upload are stored in Amazon S3 cloud storage and deleted automatically after 90 days, or sooner if your account's admins choose a shorter period. Emails you send in reply to our messages are also kept there for up to 30 days while they're processed. AWS's privacy policy is available at https://aws.amazon.com/privacy/.
  • Cloudflare, Inc. (Turnstile): Checks that the person submitting the sign-up and request-access forms isn't a bot. When you open those pages, Cloudflare receives your IP address and information about your browser and device to run the check. It doesn't set advertising cookies or track you across sites. Cloudflare's privacy policy is available at https://www.cloudflare.com/privacypolicy/.
  • Honeybadger / Honeybadger Industries LLC: Receives reports of errors in the App: the type of error and where in our code it happened, and which page or background job it happened in. Error messages, the data being processed, request details and your account data aren't sent. Honeybadger's privacy policy is available at https://www.honeybadger.io/privacy/.
  • Support and security vendors: We may use vendors that help with monitoring, incident response, or customer support. We will update this policy as our material service providers change.

Production Logs and Diagnostics

  • We maintain production logs to support availability, security monitoring, incident response, fraud prevention, debugging, and service improvement.
  • These logs may include internal identifiers such as user IDs, client IDs, job IDs, transaction IDs, integration IDs, source file IDs, blob IDs, document names, status values, file extensions, and count-based metrics.
  • Logs may also include exception classes, exception messages, and limited validation messages when needed to understand and correct failures.
  • We do not intentionally use production logs to store full uploaded file contents, OAuth access tokens, refresh tokens, or complete QuickBooks payloads.
  • Access to production logs is limited to authorized personnel and service providers with a legitimate operational, security, or support need.
  • Our default operational goal is to retain routine production logs for no longer than 90 days, unless a longer period is reasonably necessary for security investigations, incident response, fraud prevention, dispute resolution, backup recovery, or legal compliance.

QuickBooks Online and Intuit

The App is a third-party service and is not affiliated with or endorsed by Intuit. Data accessed from QBO is governed by your agreement with Intuit and their privacy policies. We access only the data you authorize via OAuth.

Google User Data

An integration can take its rows from a Google Sheet. When you connect a Google account, Dattuh asks Google to identify your account (its account id and email address) and for access to only the files you choose in Google's file picker (Google's drive.file permission). Dattuh can't see anything else in your Google Drive.

  • Who chooses the files: only the person who connected your account's Google account in Dattuh (one of your account's admins) can choose a spreadsheet, in Google's own file picker while signed in to that Google account. Others in your account can run an integration from a sheet already chosen, but can't choose files or see anything else in that Google account.
  • What we read: the spreadsheet you choose: its title, its tabs, and the rows of the tab you choose. We read them only to run your integrations and to show you the sheet you chose.
  • What we keep:
    • your Google account's id (not its email address), and which spreadsheet and tab an integration runs from and who chose them (not their titles or contents);
    • for each task run from a sheet, a copy of the tab's rows as they were when the task started, kept as the task's file and deleted automatically after 90 days, or sooner if your account's admins choose a shorter period, like an uploaded file;
    • when a data source's sample is taken from a sheet, a copy of the tab's first 1,000 rows and its column names, kept with that data source until it's replaced or deleted;
    • for each row a task sends to QuickBooks, the same limited record as for any data source (its id, date, amount and the name of the QuickBooks document's customer or vendor), kept as your sync history so it can be checked or reversed (see Transactions above);
    • your Google sign-in tokens, encrypted.
  • AI: when you ask for an integration to be built with AI assistance, the AI provider sees a sheet's column names and an anonymized sample of its rows (every value replaced by an invented one), as for an uploaded file, only to build the integration you asked for. Data from Google is never used to train or improve AI or machine-learning models, ours or anyone else's.
  • Sharing: we don't sell data from Google or use it for advertising. We share it only as needed to provide the features you use (with the service providers listed above) or as required by law. People at Dattuh don't read it unless you ask us to (for example, when you bring in the Dattuh team), it's needed for security or to comply with the law, or it's aggregated and anonymized.
  • Removing access: disconnect Google from your client's connections in the App (your client's page), or remove Dattuh's access in your Google Account at myaccount.google.com/permissions. Copies already made are deleted as described above, or sooner if you ask us.

Dattuh's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Operational Reference Cache

To reduce the volume of API requests to QuickBooks Online and to improve processing performance and reliability, Dattuh maintains a durable reference cache on our infrastructure. This cache stores resolved reference identifiers that map QuickBooks Online entity names (such as accounts, payment methods, tax codes, and terms) to their corresponding QuickBooks IDs.

  • What is stored: Reference identifiers (QuickBooks entity IDs) associated with lookup metadata such as the entity type, a verification timestamp, and a source indicator. For counterparty entity names (customers, vendors, and employees), the cache key is pseudonymized using an HMAC-SHA256 digest of the normalized lookup value — the raw entity name is not stored in the cache key.
  • Retention windows: Non-entity reference entries (accounts, payment methods, tax codes, terms, and similar) are retained for up to 24 months. Counterparty entity reference entries (customers, vendors, employees) are retained for up to 12 months. Entries may be invalidated earlier if a reference is updated or deleted in QuickBooks.
  • Purpose: The cache eliminates redundant API calls for data that rarely changes, reduces job processing time, and improves reliability for high-volume webhook and polling workloads.
  • Isolation: All cache entries are scoped to the client's account and the connected QuickBooks provider account. No cache entry is shared across different customers.

Data Storage, Security, and Retention

  • Data is encrypted in transit (TLS) and stored with appropriate safeguards.
  • Uploaded files, and copies of Google Sheets taken for tasks, are retained for 90 days, or less if your account's admins choose a shorter period (30 or 45 days), and then deleted automatically.
  • QBO data is retained only as long as necessary to provide services or as required by law. You can request deletion by revoking access or contacting us.
  • Production logs and diagnostic records are generally retained for up to 90 days, unless a longer period is reasonably necessary for operational continuity, security, audit, support, backup recovery, or legal compliance, after which they are deleted, rotated, or de-identified according to our internal practices.

No system is perfectly secure; we implement reasonable safeguards, restrict log access, and review logging practices periodically, but cannot guarantee absolute security.

Your Rights and Choices

Depending on your jurisdiction (e.g., GDPR, CCPA (California Consumer Privacy Act)), you may have rights to access, correct, delete, or port your data, and to withdraw consent. To exercise rights, contact us at business@dattuh.com. We respond in accordance with applicable law.

Geographic Scope

The App is intended solely for use by businesses operating in the United States with a United States QuickBooks Online account. We do not knowingly offer or market the App to users in the European Union, United Kingdom, or other jurisdictions outside the United States. If you access the App from outside the United States, you do so at your own risk and Dattuh makes no representations about compliance with the laws of any other jurisdiction.

Children's Privacy

The App is not directed to children under 16 (or 13 in some jurisdictions). We do not knowingly collect data from children.

Changes to this Policy

We may update this Policy. Material changes will be notified via email or in-app notice. Continued use constitutes acceptance.

Contact

For questions or requests, email business@dattuh.com.