How Atlas uses information
Pilot information notice. This page explains the information Atlas uses and the controls available to you. Before starting service, your signed order or accompanying notice must identify your contracting entity, support contact, hosting locations, and service providers. Ask your Atlas adviser for these details if they have not been supplied.
Atlas uses authorized business information to answer requested questions, deliver the agreed audit, diagnose connection problems, and improve the customer's workflows. Each Atlas company has one owner, who authorizes access and selects the context to share. Assigned Atlas staff may review that company's approved context, relevant activity, feedback, and audit evidence to perform the service.
This notice describes the authorized Composio-first source cutover. It does not confirm deployment or native acceptance. Restricted Platform reads use normal Atlas read permission through atlas_gateway_read and separate atlas_gateway_read_result retrieval. The REST read-policy contract is verified on one Gmail sample. Other execution requires exact approval; provider consent and Atlas authority stay separate.
Where information comes from
Scroll the table sideways to see every column. With a keyboard, focus the table and use the arrow keys.
| Source | How Atlas connects | What the AI can receive |
|---|---|---|
| Jobber | Directly, through a Jobber app created for your company | The account name, country, currency and the connected Jobber user's timezone and role; bounded pages and complete single records of clients (all emails, phones, contacts, billing and service addresses, balance, lead source, tags, custom fields and notes), requests (including the answers people typed on your request form), quotes and jobs (line items with prices, internal costs and markup, message, contract disclaimer, instructions, job costing and profit), invoices (lines, payments, balance, void details) and properties; visits, assessments, tasks and calendar events; payments, deposits, refunds and Jobber Payments payouts; expenses; timesheet entries with hours and labour rates; team members with their contact details and role; vehicles, drivers and API-visible live state; the products and services price list with costs; tax rates and custom field definitions; and the current version of any record a requested change targets |
| QuickBooks and other supported Composio toolkits, including Gmail, Outlook, Google Calendar, Drive, Sheets, Excel, OneDrive, Contacts and Forms | Through the company-bound Atlas gateway and separately authorized provider accounts | Fields/content supplied by the selected dynamically discovered action, including native IDs, currencies, custom fields, paging and file/resource references. Available data depends on the action schema, actual account/resource access and result limits; the retired fixed reader projections and caps do not apply |
Provider text and images are untrusted data, never instructions or approval. Jobber photo reads can deliver re-encoded images from API-visible attachments/previews; an empty attachment list does not establish that no images exist elsewhere in Jobber. No credential or secret is intended for the AI. Cardholder name/expiry can occur in Jobber payment records; full card numbers are not read.
For non-Jobber tasks Atlas searches Composio capabilities, inspects the selected schema and uses a permitted restricted read or exact-approved generic execution. Returned schemas are data, not additional native ChatGPT tools. There are no per-action Atlas wrappers or fixed QuickBooks/Gmail execution adapters. Exact account pins, provider permissions, Atlas authority and approval remain separate. Proxy, bash and workbench helpers remain on the appropriately approved path; they are excluded from the restricted read path. Composio connection helpers are not offered: apps connect only through the Atlas Connect card, completed by the owner in their Atlas browser session. Generic results can contain content/files when authorized and supported; metadata success does not prove content access or complete coverage.
What reaches Atlas
Scroll the table sideways to see every column. With a keyboard, focus the table and use the arrow keys.
| Information | Purpose | Default retention |
|---|---|---|
| Tool/account metadata: actor/company, operation/version, timing, result/error, provider and request references | Operate the service, account for usage, diagnose failures | 90 days |
| Optional raw chat excerpts the customer chooses to share | Explain a specific problem | 30 days |
| Approved company brief, audit/report evidence, and customer feedback | Deliver the audit, retain context, track resolution | While service is active, then 30 days after service ends or the account is closed |
| Jobber proposals and retained legacy typed proposals: input, preview, risk tier and target preconditions | Let the owner review the exact requested change, or run an eligible Jobber change the owner opted in to auto-run, exactly once | Jobber approval must happen within 24 hours of preparation; approving runs the Jobber change. Retired typed proposals cannot execute. The stored input, preview and preconditions of a finished change, and the provider's quoted rejection reasons (which can repeat values you submitted), are removed 30 days after preparation |
| Jobber and historical typed provider-change receipts: proposal hash, provider/account references, requester/approver, approval route (chat card, auto-run, superadmin direct, or historical portal) and the auto-run consent it relied on, times, outcome, and value-free error-log entries (result and reason codes, verification checks with record IDs and counts) | Explain what was approved, prevent duplicate dispatch and investigate uncertain results | While service is active, then 30 days after service ends or the account is closed |
| Generic gateway invocations: encrypted exact arguments/results, schema/account binding, requester/approver, claim, outcome and settlement evidence | Approve the exact outer request, retrieve its result and prevent replay of uncertain effects; no typed target-precondition or automatic readback guarantee | Durable approval/result/recovery records; closure preserves invocation and uncertainty evidence. The typed-proposal deletion schedule above is not a gateway retention guarantee |
| Restricted gateway reads: separate session purpose, account/authority binding, policy/schema references, exact request, result and outcome | Retrieve the saved result under the original custody and account for usage without creating a write approval | Durable read records separate from approved invocations; no offloaded-resource retrieval on this route. The typed-proposal deletion schedule is not a read-result retention guarantee |
| Provider credentials (Jobber, QuickBooks and optional-source authorizations) | Maintain the authorized connection | Encrypted. Kept while the company exists, including while service is paused. Disconnecting Jobber deletes its tokens; disconnecting QuickBooks or an optional source asks Composio to revoke that authorization. Closure deletes all of them (see below) |
| Order and accounting records | Manual payment receipts and service authorization | Held outside the app; separate retention is disclosed in your order |
| Minimal account records: company, owner membership, sign-in/client/company bindings, service terms, staff and operator action receipts, closure record, and provider account IDs | Keep revoked or closed access from moving into another company, prove who did what, and let a provider account connect to another company later | Kept after closure; these contain identifiers and dates, not briefs, chat excerpts or business records |
Provider responses are processed to answer authorized requests. Jobber proposal previews, generic invocation arguments/results and separate restricted-read requests/results are intentionally retained under their policies above; gateway result storage can contain provider content. Atlas does not deliberately store complete business-record payloads as routine usage logs. Evidence selected for an audit is retained as audit evidence under the policy above, with only the fields needed for the conclusion. The reusable skills package does not contain your company records.
Selected audit files may be held in the assigned operator's restricted engagement storage. The engagement owner inventories and deletes these files under the same service-end-plus-30-day policy; the application's database retention job does not delete external files. Deletion requests cover both locations.
Jobber changes follow their typed prepare, approve or eligible auto-run, execute and receipt process. Non-Jobber requests follow dynamic search/schema and either a permitted restricted read or exact-approved execution, with separate saved-result retrieval for each path. Your adviser verifies the available operations during setup. A timeout or interrupted request can leave the outcome unknown. Atlas records that uncertainty and does not automatically send the same operation again.
Tool events describe what the server observed. Workflow summaries may be assistant-reported. Customer feedback is separately identified as customer-confirmed; a failed tool call is not proof of the customer's emotion or a business outcome.
Reads
The monthly read allowance is disabled; request/result bounds and gateway budgets still apply. Provider requests require an active service and authorized connection. Restricted Platform reads use normal atlas:read without provider-write scope or approval of each read. Atlas requires current positive upstream readOnlyHint, rejects create/update/destructive classifications, and uses independently restricted REST session enforcement. Names, annotations or a model's claim alone are insufficient. The route excludes all helpers, account overrides, custom tools, elicitation and resource offload, and keeps separate durable sessions/results with current actor, client and account custody. Retrieve a stored outcome with atlas_gateway_read_result; that does not execute another read. Read authority is separate from provider-write settings.
The live policy proof contains one Gmail profile read and target-free negative create/destructive probes. It does not establish all former typed semantics, universal account confinement, deployment or native acceptance. Direct consumer execution remains blocked; consumer_project is a candidate without live restricted-read acceptance. The full generic route retains its supported helpers and requires execution permission and exact approval, including for app reads on that path. See the contract receipt for the evidence limits.
Provider changes and approval
Jobber retains 71 typed operations, with risk classification, required reference checks and bounded verification. Eligible low-risk requests can use the owner's own Jobber auto-run opt-in; other changes require an authenticated human click on the exact Atlas approval card in chat. Staff can block Jobber changes or auto-run. Approval and dispatch recheck current membership, MCP grants and the relevant company/account binding. Jobber consent/version/cap rules still apply.
QuickBooks and other providers use exact-approved generic Composio invocations. There is no non-Jobber auto-run, typed target-precondition validation or automatic per-action readback guarantee. The result records the upstream outer response; verification of an individual effect needs separate evidence. Provider write bans remain binding. All supported gateway approval workflows use the exact card in chat, including pending requests and decline. Owners may approve their company’s member requests; superadmins may approve only their own held requests in the selected company. Conversational text approves nothing. Clients without card support fail closed and must use a supported chat client. Website pages retain settings and read-only history; they cannot approve or execute provider changes. No helper may select another company or bypass a refused operation.
Historical typed QuickBooks/Gmail approvals, results and uncertain outcomes remain available under their original custody and retention rules. Only proven-unsent retired proposals may be cancelled through the guarded retirement transition. Dispatched/unknown work keeps its original reference and operator reconciliation; old approvals never become generic invocations. A timeout is not proof of no effect, and neither source retirement nor a reconnect authorizes replay.
What is not collected automatically
Connecting Atlas does not grant it full or historical ChatGPT conversation access. The skills can save an approved brief, selected task summary, or requested problem report through Atlas tools. A customer can use reads without sharing an optional narrative or excerpt. Atlas does not use hidden transcript interception.
Do not share passwords, API keys, payment-card information, or unrelated sensitive personal material in feedback. A short description and receipt/reference are normally sufficient.
Service providers
The service uses the customer's ChatGPT account (which receives the tool results the AI requests), direct Jobber integration, Composio for QuickBooks and every optional source, Auth0 for sign-in (your sign-in identity and email address), and Atlas hosting/storage. Payments are handled manually outside the app through the process disclosed in the order. Each has its own data handling. Your service notice must identify the actual hosting regions and any research or model services used for audit analysis before your content is shared with them. Canadian pricing does not mean all processing takes place in Canada.
Before using the connection, obtain your adviser’s confirmation that Composio tool-payload retention is disabled. Provider metadata may still be retained under Composio's service settings, and disabling payload retention does not erase older logs. Deleting an Atlas feedback item does not erase ChatGPT or provider histories, or external accounting records.
Service end and account closure
Service end is a pause. When your access term ends or service is ended, ChatGPT can no longer read or change your business systems through Atlas. Your provider connections and encrypted credentials are kept so service can resume. Saved company content and change receipts follow the 30-day retention above.
Closing the account ends the relationship. Atlas staff close an account on request. Closure immediately stops company access, cancels proven-unsent pending work and revokes sign-ins and ChatGPT connections. Atlas then asks Jobber, QuickBooks and each connected optional source to remove its access (best effort) and deletes the stored credentials. If a provider does not confirm the removal, Atlas keeps only the encrypted credential it needs to retry, for at most 30 days. After that, or when a removal cannot be confirmed, the credential is deleted anyway and Atlas tells you that its access may still be listed at the provider. You can remove it yourself: in Jobber, disconnect the Atlas app from your connected apps; in QuickBooks, Google or Microsoft, remove the app from the account's connected-apps or permissions settings.
Gateway closure clears its configuration and sessions, expires pending approvals and preserves invocation/uncertainty evidence for settlement. It does not revoke an entire shared Composio project, For You account or every upstream grant. Existing QuickBooks/optional-source revocation obligations continue through their separate ledgers; a missing Composio account is not proof that the provider revoked access.
After closure, saved content (briefs, feedback, excerpts and audit reports) and typed provider-change records are deleted 30 days after the closure; usage metadata follows its 90-day limit. The minimal account records listed above are kept.
Manage your information
The owner can request correction, export, or deletion through their Atlas account or named support contact. A staff member verifies identity and records completion. Retention tasks remove expired content; backups follow the documented retention/restore process so deleted content is not silently reintroduced to active service.
Disconnecting a provider, deleting Atlas content, removing the plugin, ending service, closing the account, and ending an external payment arrangement have distinct effects. The support team can help complete all requested actions and provide confirmation without asking the customer to share credentials.
- Open your account to change optional content sharing and review saved items.
- Review, approve or decline waiting requests in the Atlas card in chat. Open Change history to see Jobber changes and historical receipts and manage Jobber auto-run.
- Use the contact on your signed order to request correction, export, deletion, service end, or account closure.
- Read the usage guide for practical steps and help with connection problems.