Privacy Policy
Offisavvy UCR Reconciliation Engine
This Privacy Policy explains how Offisavvy LLC collects, accesses, uses, stores, discloses, retains, and deletes information in connection with the Offisavvy UCR Reconciliation Engine. The Application is a private internal tool used by authorized Offisavvy personnel to work with Offisavvy’s own business financial records. It is not a consumer financial service.
1. Scope
This Policy applies to the Application and its connected components, including the UCR workbook, cloud worker, QuickBooks Online connection, proof and matching engine, approval queue, audit records. It supplements Offisavvy’s general website privacy policy. If the policies conflict concerning the Application, this Application-specific Policy controls.
The Application is intended only for Offisavvy employees, officers, contractors, accountants, bookkeepers, and other expressly authorized personnel. It is not intended for children or public consumer use.
For this Policy, “Company Data” means Offisavvy’s accounting, transaction, customer, vendor, employee, payroll, payment-processor, banking, operational, and related business records processed by or through the Application, including information generated from those records.
2. Who is responsible for the information
Offisavvy LLC is responsible for the operation of the Application and the handling of information described in this Policy. Offisavvy determines the business purposes and access rules for the Application.
Offisavvy processes QuickBooks Online data for Offisavvy’s own Application purposes and not on Intuit’s behalf. Intuit and Offisavvy independently determine their respective data practices under their applicable terms and privacy notices.
3. Information we process
Depending on configuration and authorized use, the Application may process:
- Authorized-user information, such as name, business email address, role, account identifiers, access status, approvals, and security events;
- QuickBooks Online company information, chart of accounts, account balances, transaction identifiers, dates, amounts, descriptions, memos, classes, locations, references, linked transactions, customers, vendors, employees, products and services, invoices, bills, payments, deposits, credits, journal entries, and reports;
- Authorized bank, credit-card, line-of-credit, payment-processor, payroll, accounts-receivable, accounts-payable, purchase-order, commission, and other business source records supplied by Offisavvy or approved providers;
- Personal information contained within legitimate business records, such as names, business contact details, addresses, payment references, employee or contractor details, and transaction history;
- Reconciliation cases, candidate matches, confidence scores, evidence, transaction relationships, duplicate indicators, exception notes, account maps, proposed actions, approvals, rejection reasons, before-and-after hashes, and verification results;
- Technical and security information, such as timestamps, request identifiers, service logs, configuration status, IP or device information made available by service providers, error codes, and authentication or access events; and
- Support communications and information voluntarily provided when requesting assistance.
The Application is not designed to collect full payment-card numbers, card security codes, online-banking passwords, Intuit passwords, Social Security numbers, or personal medical information. Authorized Users must not intentionally place such information in worksheet cells, support messages, or free-text notes.
4. Sources of information
Information may come from:
- Authorized Users and Offisavvy’s existing business records;
- QuickBooks Online through Intuit’s OAuth 2.0 authorization process and Accounting API; the initial release does not request the QuickBooks Payments scope or process card payments;
- Google Sheets and other Offisavvy-controlled files or source tabs;
- Offisavvy-supplied exports or source records from financial-data, banking, payment-processor, payroll, or operational providers. No direct Plaid, payroll, payment-processor, or similar provider connection is enabled in the initial release; and
- security, hosting, logging, and support systems used to operate the Application.
5. How we use information
Offisavvy uses information only for legitimate internal business purposes, including to:
- retrieve and normalize authorized accounting and transaction data;
- reconcile source records against QuickBooks Online and identify incomplete, duplicated, erroneous, unsupported, or mismatched records;
- map transaction relationships and create evidence-backed explanations;
- prepare prioritized work queues and controlled accounting proposals;
- record human approvals, enforce safety modes, execute only authorized actions, and verify results;
- produce financial operations, cash-flow, customer, vendor, commission, tax-support, audit, and management reporting;
- detect abuse, investigate errors, preserve auditability, maintain security, troubleshoot, and improve reliability;
- comply with accounting, tax, legal, contractual, security, and recordkeeping requirements; and
- respond to support requests and communicate material service or security information.
Offisavvy does not use QuickBooks data for unrelated advertising, consumer profiling, data brokerage, or sale. The Application is restricted to Offisavvy’s own authorized records and is not designed to pool or commingle Company Data with data controlled by an unrelated company.
6. When information is disclosed
Offisavvy may disclose information only as reasonably necessary to:
- Intuit, to authenticate the connection and provide QuickBooks Online data and API functionality;
- Google, to provide Google Workspace, Cloud Run, Cloud Storage, Secret Manager, logging, and related infrastructure;
- approved financial-data or operational providers when Offisavvy has separately authorized the connection;
- professional advisors, auditors, insurers, lenders, or service providers who need the information for legitimate Offisavvy purposes and are subject to appropriate confidentiality or data-protection duties;
- law enforcement, regulators, courts, or other parties when required by law or reasonably necessary to protect rights, security, or safety; or
- a successor in a merger, financing, restructuring, sale, or transfer of relevant business assets, subject to appropriate protections.
Offisavvy requires service providers processing information on its behalf to use the information only to provide the contracted service and to maintain appropriate security and confidentiality protections.
7. No sale or targeted advertising
Offisavvy does not sell Company Data or personal information processed by the Application. Offisavvy does not share such information for cross-context behavioral advertising or use it for targeted advertising.
8. Security safeguards
Offisavvy uses administrative, technical, and organizational safeguards appropriate to the sensitivity of the information and the relevant component. Current controls include dedicated service identities, least-privilege cloud permissions, encrypted transport, encrypted cloud storage, managed secret storage, request authentication, workbook access restrictions, audit logging, operating-mode ceilings, and idempotency controls. The initial production connection remains READ_ONLY. Offisavvy will not enable LIVE operation until approver identity, role authorization, protected audit records, execution limits, and post-action verification are configured and tested.
No security measure can guarantee absolute security. Authorized Users must follow Offisavvy security policies and immediately report suspected loss, unauthorized access, or misuse.
9. Retention and deletion
Offisavvy retains information only for as long as reasonably necessary for the purposes described in this Policy, to maintain financial and audit integrity, and to satisfy legal, accounting, tax, contractual, security, and dispute-resolution obligations.
| Information category | Typical retention |
|---|---|
| OAuth tokens | While the QBO connection is active. After revocation, administrative deletion is initiated as soon as reasonably practicable; deletion is not treated as complete until relevant stored generations are purged or rendered inaccessible. |
| Reconciliation snapshots, evidence, approvals, sealed actions, and verification records | Up to seven years when needed for accounting, tax, audit, legal, or evidentiary purposes. |
| Operational and security logs | According to the configured provider retention, generally 30–400 days, or longer when required to investigate a security incident or satisfy law. |
| Support communications | Generally up to two years after resolution, unless a longer period is reasonably necessary. |
| Deleted or superseded backup/version copies | Retained until removed by a configured lifecycle or administrative purge. Because versioned storage may preserve older generations, Offisavvy treats deletion as complete only after relevant generations are purged or rendered inaccessible. |
Retention may be shortened when information is no longer needed, or extended when required by law, legal hold, audit, contract, or security investigation.
10. Disconnecting QuickBooks Online
In the initial release, an authorized administrator disconnects the Application through Intuit’s available connection-management controls and asks the Offisavvy administrator to remove the stored connection. The initial release does not provide a public self-service disconnect endpoint. After revocation, Offisavvy blocks new QuickBooks Online API access and initiates administrative deletion of stored access and refresh tokens, including relevant versioned copies, as soon as reasonably practicable. Previously generated business records may be retained for the periods stated above when required for accounting, tax, audit, security, legal, or evidentiary purposes.
11. Access, correction, deletion, and other requests
Authorized Users and other individuals whose personal information may appear in Company Data may contact Offisavvy to request access, correction, or deletion, or to ask how information is used. Offisavvy will verify the requester’s identity and authority and will respond as required by applicable law.
Deletion may be limited where information must be retained to comply with law, maintain accurate accounting or tax records, establish or defend legal claims, investigate security incidents, or preserve the integrity of an audit trail. Where California privacy law applies, California residents may also have rights to know, correct, delete, limit certain uses of sensitive personal information, and receive non-discriminatory treatment for exercising applicable rights.
12. International access and hosting
The Application is intended for United States business operations and is hosted and administered in the United States. Information may be processed by approved service providers in locations permitted under their agreements and applicable law.
13. Children
The Application is not directed to children under 18, and Offisavvy does not knowingly authorize children to use it. If information about a minor appears incidentally in legitimate business records, it is handled only for the authorized business and legal purpose.
14. Security incidents
If Offisavvy identifies a suspected security incident, it will investigate, contain, remediate, and document the incident as appropriate. Offisavvy will provide notifications to affected parties, Intuit, regulators, or others when required by applicable law or contractual obligations.
15. Changes to this Policy
Offisavvy may update this Policy to reflect changes in law, service providers, security controls, data practices, or Application features. The revised effective date will be posted with the updated Policy. Material changes will be communicated to Authorized Users as appropriate.
16. Contact
Privacy questions or requests may be submitted to Offisavvy LLC, 7668 Miramar Rd., Suite B, San Diego, CA 92126; email: info@offisavvy.com; telephone: 858-727-5444. Please use the subject line “UCR Privacy Request” and do not include passwords, OAuth tokens, API keys, full account numbers, or other unnecessary secrets.