Privacy notice
Effective upon publication.
SamurAI Technologies Inc. operates SamurAI Technologies, a private connector for internal accounting in the QuickBooks companies StyleLabs Inc and Samurai Technologies Inc. This notice describes that connector. It does not describe Intuit's services or the separate StyleLabs production connector.
Privacy and support requests go to Almin Kassamali at support@stylelabs.ca.
What the connector processes
The connector processes the accounting records QuickBooks returns for a requested tool. Those records can include customers, vendors, employees, invoices, bills, payments, deposits, journal entries, reports, and similar data, including names, email addresses, telephone numbers, addresses, amounts, and employee or tax-related fields when QuickBooks returns them. The records can concern people other than the person who connected the app.
It also processes connection data: a principal identifier, the company slot, the QuickBooks company id, company names, token expiry, link time, and reauthorization status; Intuit authorization codes during the callback; access and refresh tokens; and short-lived link, confirmation, and optional PKCE state. Downstream connector sign-in uses separate OAuth client, redirect, and grant records that carry the principal identifier. Application logs can include error codes, HTTP statuses, and QuickBooks API paths. Cloudflare observability and tracing are enabled. This notice does not describe every field an infrastructure log or trace may contain.
A safeguard removes specified credential keys and some social-security-number patterns from certain outputs and errors. Other personal or financial information can still reach the authorized client. A blocked write can contain personal information in the request that was submitted. That request is not sent to QuickBooks while writes are off.
Why it is used
The connector uses this information to sign in an authorized client, link and check the selected company, carry out the accounting request, return the result, refresh a company credential, mark a connection that needs reauthorization, and diagnose errors. Approving the connector sign-in does not by itself link a QuickBooks company. Each company is linked through Intuit, checked against its pinned company id and expected name, and confirmed before the credential is saved. A failure for one company does not fall back to the other company's grant.
The reviewed application does not include a separate advertising, data-sale, or model-training integration. That does not describe what the authorized client, Intuit, or Cloudflare does with information under its own terms.
Who receives it
Intuit receives the OAuth exchange and the accounting API request, and returns the requested company information. Cloudflare runs the Worker, Durable Objects, key-value storage, and observability, and therefore processes connector traffic and stored authorization data. The authorized client receives the results. If that client is an AI client, it may process and retain those results under its own terms. This notice does not promise that an AI client refrains from training, and it does not state a hosting country or an international-transfer arrangement.
What is stored
Each principal and company has its own credential record in a Cloudflare Durable Object. The record includes company identifiers and names, tokens, expiry, and connection metadata. The record is encrypted with AES-256-GCM. The encryption is bound to that principal and company. The key is derived with HKDF-SHA-256 from an operator secret. The token is decrypted in memory when the connector calls Intuit.
Short-lived link records store a hashed one-time handle, an encrypted OAuth, confirmation, or return payload, purpose, principal, company slot, and expiry. The company id pin is stored with those records. It is encrypted with AES-256-GCM under a separate HKDF-SHA-256 derivation from the same operator secret, and the ciphertext is bound to the company slot rather than to one principal. A stored pin that is not in this encrypted form is not read and is not deleted. Downstream OAuth state is stored separately through the OAuth provider's key-value binding. Upstream Intuit tokens are not copied into those downstream grant properties. Browser cookies identify the signed-in principal for up to 400 days and support connection checks for 10 minutes. On HTTPS those cookies are Secure, HttpOnly, and SameSite=Lax. Clearing cookies can remove access to a principal without deleting its stored connections.
The request path returns accounting results to the authorized client. The reviewed implementation has no separate persistent cache of the books. That does not mean financial data is absent from logs, traces, backups, or the client's own storage.
How long it is kept
A saved company credential stays until it is removed for that principal and company. Refreshing a token updates the saved record. An expired or rejected grant is marked for reauthorization and is not deleted on a schedule. There is no automatic purge.
The disconnect action first asks Intuit to revoke the connector's tokens for that company, then deletes that local credential. If Intuit does not confirm the revocation, the local credential is still deleted and the user is told. Disconnect does not delete QuickBooks records, remove the connector sign-in, clear the company pin, or erase results already returned to a client. Link records are valid for 10 minutes. Using one, or opening it after it expires, deletes that record. There is no separate cleanup job, so an untouched expired record has no guaranteed deletion time.
No retention deadline is stated for logs, traces, backups, downstream grants, or copies held by a client. No deletion service level is promised.
Requests
Email support@stylelabs.ca to ask about access, correction, deletion, or a complaint. Name the company and the request. Do not send access tokens. The operator will ask for enough information to verify that you are authorized for that company before acting. The supported way to stop this connector's use of one company credential is the disconnect page or the unlink tool for that company, which also asks Intuit to revoke the connector's tokens. You can also remove the app from the company's connected apps in QuickBooks. This connector does not guarantee deletion of every copy, including provider logs, backups, downstream grants, and client history.
Changes
Financial writes are off in the current configuration. That is not a permanent read-only design. If practices change in a material way, including if writes are turned on, an updated notice will be published with its effective date.