This Privacy Policy explains how the Atlas Connector Gateway (Atlas Gateway, we, us, or our), an internal technology service operated for McIntyre Elder Law, handles information when connecting specifically authorized Atlas applications to approved third-party services, including QuickBooks Online.
Atlas Gateway is not offered to the general public. Its connections are intended for authorized internal business use.
1. Scope
This Privacy Policy applies to information processed through Atlas Gateway, its authorization callback, its credential boundary, and its security and operational audit records. It does not replace the privacy policies of Intuit, QuickBooks Online, or other third-party services.
2. Information Atlas Gateway processes
Depending on the authorized connection and capability, Atlas Gateway may process the following categories of information.
A. Authorization and connection information
- provider and connection identifiers;
- production or sandbox environment;
- QuickBooks Online Realm or company ID;
- authorization status, requested scope, and token-expiration metadata;
- short-lived OAuth authorization codes and state values during setup; and
- access and refresh tokens needed to maintain the authorized API connection.
Authorization codes, access tokens, refresh tokens, and client secrets are sensitive credentials. They are not company accounting records and are not returned to connected Reporting applications.
B. Company identity information
The initial QuickBooks Online production capability, qbo.read_company, may retrieve:
- Realm or company ID;
- company name;
- legal name, when available;
- country;
- fiscal-year start or month, when available;
- provider metadata needed to verify company identity; and
- retrieval and provider timestamps.
C. Security and operational information
Atlas Gateway may record:
- requesting application and authorized principal;
- requested capability and operation;
- connection ID, environment, and Realm ID;
- request and audit identifiers;
- timestamps and provider status;
- success, denial, error, and completeness classifications; and
- whether an external write occurred.
The audit design excludes provider response bodies and redacts fields that may contain tokens, secrets, passwords, authorization credentials, cookies, or API keys.
3. Current read-only limitation
The initial production QuickBooks Online connection is limited to qbo.read_company for company identity verification.
Atlas Gateway does not currently use that capability to create, change, delete, post, approve, reconcile, or transfer QuickBooks Online data. It does not authorize bills, invoices, journal entries, payments, bank transfers, money movement, trust disbursements, reconciliation signoff, or administrative changes.
If Atlas Gateway's authorized production capabilities materially expand in the future, the new capability must be separately approved and this Privacy Policy will be updated when the change affects the information practices described here.
4. How information is used
Atlas Gateway uses information only as reasonably necessary to:
- authenticate and maintain an authorized provider connection;
- validate OAuth state and prevent unauthorized callback use;
- distinguish production connections from sandbox connections;
- verify that the selected QuickBooks Online company is the intended company;
- perform the expressly authorized read-only capability;
- refresh authorization without requiring a persistent browser session;
- enforce principal, capability, environment, and write-prohibition policies;
- create non-secret audit evidence;
- detect, prevent, and investigate errors, unauthorized access, or misuse;
- maintain, secure, and improve the reliability of the service; and
- satisfy applicable legal, regulatory, or compliance obligations.
Atlas Gateway does not sell personal information or provider data and does not use QuickBooks Online data for advertising or behavioral profiling.
5. Credential handling
Application credentials and OAuth tokens are controlled by Atlas Gateway and are not disclosed to connected Reporting applications.
In the current production design:
- application credentials and authorization tokens are stored through the operating system's protected credential store;
- secret values are distinguished from non-secret connection identifiers;
- tokens are refreshed through the provider API when authorized and necessary;
- rotated refresh tokens replace prior refresh tokens when required by the provider;
- revoked or unusable authorization fails closed and may require reauthorization;
- secrets are not intentionally placed in source control, prompts, ordinary application logs, or audit payloads; and
- credentials are not returned through the connector API.
The public OAuth callback is designed only to receive the provider's temporary authorization response and direct the administrator back to the secure local setup. It is designed not to intentionally store callback parameters, use analytics, set tracking cookies, or forward authorization data to another destination.
6. Disclosure of information
Atlas Gateway may disclose or make information available only as follows:
A. Authorized Atlas applications and personnel
Approved non-secret results may be provided to an Atlas application or authorized person only when the requesting principal has the required capability. The initial Reporting principal receives only the non-secret result of qbo.read_company after applicable policy and identity checks.
B. Intuit and QuickBooks Online
Information is exchanged with Intuit as necessary to authenticate the connection, refresh authorization, and perform the authorized QuickBooks Online API request. Intuit's handling of information is governed by its own terms and privacy notices.
C. Infrastructure and security providers
Hosting, network, credential-storage, and security providers may process limited information as necessary to provide their services. They are permitted to use that information only for providing, securing, and supporting the applicable service, subject to their contracts and legal obligations.
D. Legal and safety reasons
Information may be preserved or disclosed when reasonably necessary to comply with law, legal process, professional obligations, or enforceable governmental requests; protect rights, security, or property; investigate misuse; or respond to an emergency.
Atlas Gateway does not disclose QuickBooks Online data to data brokers or advertising networks.
7. Retention and deletion
Atlas Gateway retains information only for as long as reasonably necessary for the purposes described in this Policy, including maintaining an authorized connection, enforcing security controls, preserving audit integrity, resolving disputes, and meeting legal, professional, and compliance obligations.
- OAuth credentials are retained while the applicable connection remains authorized and needed. They may be replaced during token rotation and are deleted or rendered unusable when the connection is removed through the approved administrative process.
- Non-secret connection metadata is retained while needed to identify, verify, secure, and administer the connection.
- Security and operational audit records may be retained after disconnection when necessary to preserve the integrity of the audit chain, demonstrate the absence or occurrence of external writes, investigate incidents, resolve disputes, or meet legal and compliance obligations.
An authorized administrator may request disconnection, credential deletion, or information review by contacting us. A deletion request may be limited where retention is required by law, professional obligation, security, fraud prevention, or the integrity of an audit record. When deletion is not available, access may be restricted and the reason for continued retention documented.
8. Security
Atlas Gateway uses administrative, technical, and organizational safeguards appropriate to the nature of the information it processes. These safeguards include least-privilege capability grants, deny-by-default policy checks, environment separation, company-identity verification, protected credential storage, token redaction, bounded provider operations, and append-only audit records.
No security measure can guarantee absolute security. Suspected unauthorized access, credential exposure, or security incidents should be reported promptly using the contact information below. Affected authorization may be revoked or replaced when appropriate.
9. Cookies and tracking
The Atlas Gateway OAuth callback is not intended to use advertising trackers, behavioral analytics, or tracking cookies. Standard network and hosting infrastructure may process limited request metadata for security and reliable delivery, subject to configured retention controls and provider terms.
10. Choices and control
An authorized administrator may:
- decline or stop the OAuth authorization process;
- verify the company identity before accepting a connection;
- request that Atlas Gateway revoke or remove a connection;
- revoke the application's QuickBooks Online authorization through available Intuit account controls; and
- request access to, correction of, or deletion of information, subject to applicable legal and audit-retention requirements.
Requests will be verified before action is taken to protect the company and connection from unauthorized changes.
11. Children's privacy
Atlas Gateway is an internal business service and is not directed to children under 13. We do not knowingly use Atlas Gateway to collect personal information from children.
12. Changes to this Policy
We may update this Privacy Policy to reflect changes in Atlas Gateway, authorized capabilities, third-party services, security practices, or legal requirements. The effective date at the top identifies the current version. Material changes will be communicated through an appropriate internal or public notice.
13. Contact
Questions, privacy requests, or security reports concerning Atlas Gateway may be directed to: