Privacy Policy
How SIRJ handles account, integration, and reporting data.
Last updated: July 5, 2026
SIRJ ROI connects ad platforms, call tracking, CRMs, booking systems, invoices, and payments to produce source-backed revenue attribution. This policy explains the data we collect, why we use it, how connected-source data is protected, and what controls customers have.
Related SIRJ page: review retention and deletion controls.
Who this policy covers
This policy applies to SIRJ ROI account owners, team members, invited client users, and the connected accounts a customer authorizes SIRJ to read for attribution, dashboards, Ask Data answers, reports, exports, billing, and support.
- Agency accounts can contain multiple client workspaces, and each workspace should stay scoped to the right client.
- Invited client users receive access only to the workspace and reporting surfaces permitted by the account owner.
- Connected providers remain governed by the provider account owner's permissions and provider terms.
Related SIRJ page: review this control.
Information SIRJ collects
SIRJ collects the account, workspace, integration, billing, diagnostic, and reporting records required to operate the product. The product is designed to use the source fields needed for revenue attribution instead of collecting unrelated provider data.
- Account records can include names, emails, account memberships, client workspaces, invitations, roles, sessions, and billing status.
- Integration records can include selected provider resources, setup configuration, sync state, normalized source events, dashboard rows, and report snapshots.
- Operational records can include audit logs, sync errors, report export history, notification delivery records, and rate-limit metadata.
Related SIRJ page: review this control.
Connected source data
When a customer authorizes an integration, SIRJ reads the provider records needed to produce dashboards and reports. Those records may include campaign performance, calls, leads, jobs, invoices, payments, messages, CRM stages, resource selections, and source-health signals.
- Integration pages describe the imported objects and the reporting questions each source can support.
- SIRJ does not claim a metric when the required source record, client scope, or validation gate is missing.
- Customers choose which services to connect and can disconnect integrations to stop future source access.
Related SIRJ page: review this control.
Google user data and Google Ads
SIRJ uses Google Ads data on a read-oriented reporting basis when a customer connects an authorized Google account. Google data is used to show spend, campaign, click, and conversion context beside downstream leads, jobs, invoices, and revenue proof.
- SIRJ does not use Google Ads access to create, edit, pause, or manage campaigns, ads, budgets, or keywords.
- Google Ads data is used to provide the customer-requested reporting and attribution service, not to sell data or build advertising profiles.
- SIRJ use of information received from Google APIs is intended to follow the Google API Services User Data Policy, including Limited Use requirements.
Related policy: Google API Services User Data Policy
Related SIRJ page: review this control.
How SIRJ uses information
SIRJ uses customer data to provide and secure the service: authenticate users, connect providers, normalize source records, generate dashboards, answer supported Ask Data questions, deliver reports, manage subscriptions, and troubleshoot integration health.
- Source records are used to compute attribution, source health, metric cards, recommendations, exports, and cited answers.
- Billing records are used to manage trials, subscriptions, checkout, billing portal access, plan limits, and account status.
- Diagnostic records are used to investigate sync failures, setup gaps, provider errors, and product reliability.
Related SIRJ page: review this control.
How SIRJ shares information
SIRJ does not sell customer data. Data is shared only as needed to operate the service, comply with law, protect the platform, or provide customer-requested workflows through infrastructure, database, email, payment, analytics, or connected-provider services.
- Service providers should process data under contractual obligations that support confidentiality, security, and product delivery.
- Client workspace users see only the reporting data and surfaces their role and invitation scope permit.
- SIRJ may disclose information when required by law or to investigate abuse, fraud, security incidents, or platform misuse.
Related SIRJ page: review this control.
Retention, deletion, and customer choices
Customers can choose which sources to connect, disconnect integrations, export eligible account data, request deletion, manage client users, and cancel subscriptions. Some records may be retained when needed for security, audit, billing, legal, or abuse-prevention reasons.
- Disconnecting an integration stops future provider access but does not automatically remove every historical dashboard, report, audit, or billing record.
- Data export and deletion workflows are account-scoped and permissioned so one user cannot remove or retrieve another customer's data.
- Customers can also revoke provider access from the connected provider account, such as the Google Account permissions page.
Related SIRJ page: review this control.
Privacy questions
Does SIRJ sell customer data?
No. SIRJ uses account, integration, and reporting data to operate the requested service. It is not sold or used to build advertising profiles.
Can customers disconnect an integration?
Yes. Customers can disconnect integrations to stop future provider access. Historical records may remain where needed for reports, audit, billing, legal, security, or customer-requested retention.
How is client workspace data separated?
SIRJ carries account and client scope through sessions, memberships, invitations, source records, dashboards, reports, exports, and compliance jobs so users see only permitted workspaces.
Does SIRJ manage Google Ads campaigns?
No. Google Ads access is used for reporting and attribution context. SIRJ does not use that access to create, edit, pause, or manage campaigns, budgets, keywords, or ads.
Related trust pages
Contact
Questions about this policy or your data can be sent to privacy@sirj.ai.