Connected Sources
Connected Sources Policy
Effective date: July 2, 2026. This policy explains how Monocrat handles connected business sources, OAuth, source-health states, provider access, source disconnect, provider-owned exports, and source-write boundaries.
1. Scope
Connected sources are business systems, accounts, exports, APIs, webhooks, files, and provider records that you authorize Monocrat to use for source-backed workflows. They may include Google Workspace, Shopify and Shopify Payments, tenant Stripe, Square, Plaid, manual or POS exports, payment rail providers, uploaded records, email forwarding, external helpdesks, and other enabled providers.
This policy supplements the Terms of Service, Privacy Policy, Account & Data Controls, Billing Terms, and Payment Rail Terms.
2. Authority To Connect
You may connect only sources, accounts, stores, payment processors, workspaces, inboxes, files, exports, and records that you have authority to provide and use with Monocrat. You are responsible for the notices, consents, provider permissions, internal approvals, and legal basis needed for Monocrat to process connected-source data.
Monocrat v1 uses one verified owner-operator account per tenant. Source connection, disconnection, source reauthorization, Billing & Usage authority, data controls, and high-stakes approvals derive from the verified owner session unless a written agreement or support/legal process creates another accepted route.
3. Google Sign-In And Google Workspace
Public waitlist sign-in uses identity-only Google scopes such as OpenID, email, and profile. Product Google Workspace access is requested only after approval and through a separate product onboarding flow. Product scopes may include Gmail, Drive, or Calendar access only where needed for source-backed product functionality and only after you review the permission request.
Google permissions are requested in context where practical and should match the visible product surfaces that need them. During pre-CASA private beta, product Google Workspace access remains limited to allowlisted accounts and does not authorize broad self-serve onboarding or unapproved sensitive or restricted scopes.
Monocrat uses Google API data only for permitted product functionality, security, source health, owner-reviewed workflows, and legal or security obligations. Monocrat does not sell Google API data, use it for advertising, or use it for generalized AI model training. Additional Google API data handling is described in the Privacy Policy.
4. Source Roles
| Role | Examples | Boundary |
|---|---|---|
| Identity and access source | Google sign-in, owner session, source authorization records. | Used to authenticate, bind tenant authority, and protect source access. URL possession or email receipt alone does not grant product authority. |
| Read-only evidence source | Invoices, orders, payments, payouts, messages, files, events, exports, source refs. | Used as business evidence. API access, webhook receipt, object IDs, or export upload do not authorize source writes or external actions by themselves. |
| Execution or payment rail provider | Approved payment rail, provider dashboard, agency portal, source-platform refund or order surface. | Requires the owning provider capability, customer approval, action gate, legal/custody review where applicable, and fallback handling before any live external write. |
| Provider-owned export or privacy route | Google, Shopify, Stripe, Plaid, Square, Moov, or other provider data controls. | Provider-owned exports, revocation, deletion, or privacy callbacks are governed by provider controls and terms. Monocrat records handoff or evidence where available. |
5. Source Health And Coverage States
Monocrat may label sources as connected, syncing, ready, degraded, stale, missing evidence, insufficient scope, unauthorized, provider unavailable, policy-blocked, consent-blocked, or disconnected. These states are source-backed operational facts, not blame labels. Monocrat uses them to avoid pretending that a workflow is complete when the underlying source is missing, stale, conflicting, or unavailable.
A stale, degraded, missing, policy-blocked, or insufficient-scope source may pause, narrow, or block affected workflows, including billing evidence, cash forecasting, support context, Trust Graph claims, payment readiness, tax/payroll readiness, and source-system actions.
6. No Inferred Source Writes
Connected-source data does not create write authority by implication. Monocrat does not infer permission to create orders, issue refunds, capture payments, send customer messages, mutate provider records, update source systems, publish Trust Graph claims, create binding commitments, file tax or payroll items, or execute payment rails merely because a provider is connected, a webhook was received, an object ID is present, or an uploaded export looks valid.
Source writes and other external effects require the owning action package, source refs, current authority, idempotency or replay handling where applicable, provider capability evidence, and a fresh action-gate result. Email, push, app-link previews, or unauthenticated links may notify you, but they do not complete source writes.
7. Billing, Payment Sources, And Payment Rails
Monocrat uses Stripe for Monocrat's own subscription billing, invoices, payment methods, direct charges, refunds, disputes, and Customer Portal sessions. Tenant Stripe, Shopify Payments, Square, Plaid, manual/POS exports, and similar connectors are customer payment-source evidence for your business. They are separate from Monocrat's own Stripe billing processor.
Customer-authorized outbound payment rail workflows are governed by the Payment Rail Terms. Monocrat does not hold customer funds, operate a pooled customer balance, or treat a source connector as payment execution authority unless the selected provider, customer approval, and action gates allow the exact workflow.
8. Source Disconnect And Revocation
You may disconnect or revoke supported sources through Monocrat settings where available or directly through the source provider. Monocrat may also disable local credentials, stop polling, stop webhook handling, or mark a source unavailable when authorization, provider policy, security, legal, data-quality, or product-integrity requirements are not met.
Source disconnect may affect features that depend on the source. Some provider-side records, processor records, backups, logs, payment/tax records, disputes, security records, fraud/abuse records, legal holds, and audit records may remain subject to the retention rules in Account & Data Controls.
9. Provider-Owned Exports And Privacy Requests
Some records remain controlled by the source provider. Monocrat may show source status, provider handoff links, compliance callback status, privacy request status, or export/deletion evidence where available, but provider-owned exports and provider-side deletion are governed by the provider's tools, terms, and legal obligations.
Shopify privacy callbacks, provider privacy webhooks, legal access/export requests, legal erasure requests, and source-provider handoffs route through Monocrat's data controls and support/legal process. Monocrat does not claim a provider-owned export or deletion has completed unless there is source-backed evidence or a provider handoff record.
10. Support And Incidents
Support may help recover source-health, reauthorization, webhook replay, import backfill, billing evidence, data controls, and provider-handoff paths without impersonating the owner. Support access and private-content boundaries are described in the Support & Admin Access Policy.
11. Beta Limits
During private beta, sources may be allowlisted, disabled, degraded, manual, sandbox-only, read-only, or unavailable. Broad Google Workspace OAuth onboarding, provider production access, write-capable provider flows, and live payment rail execution remain subject to the applicable provider, security, legal, product, and launch gates.
12. Contact
Source access, disconnect, privacy, or provider-handoff questions can be sent to privacy@monocrat.ai. Billing-source questions can be sent to billing@monocrat.ai. Security concerns can be sent to security@monocrat.ai.