Privacy

Privacy Policy

What information we handle, why we use it, how long we keep it, and how to request access, correction, or deletion.

Last updated: October 23, 2026

1. Scope and responsibility

This policy covers the Decisionate website, web application, and related services ("Decisionate", "we", "us", or "our"). We handle account and service information to operate Decisionate. Workspace owners control the business data they import, their members, connections, and sharing choices. They are responsible for having the authority and any required consent to provide information about other people.

Our privacy contact is support@decisionate.ca. Questions about information imported by your employer or another business may also need to be directed to that workspace owner.

2. Information we handle

  • Account information: name, email address, authentication identifiers, session information, and internal user identifiers.
  • Workspace information: business and onboarding details, members and roles, invitations, agency-client relationships, branding, preferences, and access records.
  • Business information: uploaded files, authorized connector records, dataset columns and metrics, dashboards, forecasts, relationships, alerts, reports, decisions, notes, outcomes, and lessons.
  • Analysis configuration and results: selected metrics, date columns, dimension columns and selected unique values, date ranges, grouping and timing settings, seasonal-business settings, business questions, saved report definitions and snapshots, weekly templates, and decision evidence.
  • Background analysis records: job identifiers, workspace and source references, submitted analysis settings, processing status, results, timestamps, and error information. Closing a page does not itself delete these records.
  • Connection information: provider and account identifiers, configuration, authorization scopes, and credentials needed to import authorized data.
  • Service information: request metadata, usage and AI-credit records, billing identifiers, delivery status, activity history, errors, and support messages.
  • Email preferences: verification and marketing-consent records, the wording and sender details shown when you opted in, unsubscribe and suppression records, lifecycle classifications, and email-delivery history.

3. Why we use information

We use information to authenticate accounts, enforce permissions, import and analyze authorized data, display dashboards, track decisions and outcomes, deliver requested reports and alerts, and provide support. We also use relevant service records to operate billing and AI, prevent abuse, investigate failures, and maintain reliability. We do not use a connection as authorization to access unrelated accounts or to publish a workspace's data.

Marketing is optional and requires recorded opt-in and a verified email address. We use account type, subscription and trial status, successful data setup, and meaningful product activity to tailor eligible onboarding emails and product campaigns. Background syncing and email opens do not count as meaningful product activity. You can change marketing preferences in Settings or unsubscribe using the link in a marketing email without signing in. Withdrawal stops marketing; essential account notices and your configured reports and alerts have separate controls. We retain consent and withdrawal evidence, suppression records and delivery history as needed to honor preferences, operate the service and meet applicable obligations.

4. Connected providers and Meta Ads

A connection requires authorization from a person with the relevant provider permissions. The imported information depends on the provider, selected account, resource, and granted permissions. Meta Ads imports can include ad-account and campaign identifiers, names, and performance metrics such as spend, impressions, clicks, and conversions. Decisionate uses these records for reporting and analysis, not to create or edit advertising campaigns on your behalf. Provider approvals may be required.

Removing a connection removes its stored authorization credentials and prevents future syncs through that connection. It does not automatically delete datasets already imported. An authorized user can delete those datasets separately, or request workspace deletion. You can also revoke authorization through the connected provider. Revocation and deletion in Decisionate do not delete the provider's original records.

Where the source supports date-based imports, the initial sync requests 90 days. Older available history is loaded in background chunks, up to three years. Longer imports are checkpointed so they can resume. Provider permissions, resource coverage, and history limits can reduce the records available; a configured history window is not a guarantee that every record in that window can be imported.

5. Workspace access and public sharing

The API checks identity, workspace membership, and role permissions for private data. Agency management of a client workspace does not by itself grant permission to read the client's data. Platform administration is a separate permission.

Date and dimension filters narrow the records used for analysis; they are not access controls or anonymization. Dimension values, small groups, labels, and user-authored report text may identify people. Saved reports, decision evidence, PDFs, and email reports can include selected analysis context and results. Choose recipients and sharing settings accordingly. Revoking a share does not recall copies already downloaded or delivered by email.

If you enable a public dashboard share, anyone with a valid share link can view the information exposed by that link without signing in. Share links should be treated as confidential and can be revoked by an authorized user. The public live demo and recorded walkthrough use prepared sample data, not customer workspace data. Demo sample files are public and may be cached by browsers and hosting infrastructure.

6. AI processing

When you use Ask Decisionate in Help & Support, your question, recent questions from the conversation, and relevant product documentation may be sent to the configured AI provider. This guidance does not query your datasets or change your account. The conversation is held in the current page, not saved as a chat history by Decisionate. Clearing it or leaving the page does not delete information already processed by the provider. Contact support opens a separate form for you to review and send.

For a requested AI analysis, Decisionate prepares bounded facts, selected metric or relationship context, aggregate values and trends, and relevant decision outcomes or learning notes from the same workspace. For reports, this can include your business question, selected dimension filter values, and bounded unusual-change and seasonal-analysis results. This context is sent to the configured AI provider. The analysis request is not an upload of the raw dataset file or every source row.

Text, labels, and notes included in that context may contain personal information. Do not include passwords, API keys, or unnecessary sensitive information. Outputs are decision support and require human review; they do not automatically execute business actions. Provider processing and retention terms also apply when you use AI.

7. Service providers and transfers

The following providers or categories can receive information for the stated purposes. Contact our privacy team for the active provider and processing-location details relevant to your workspace.

ProviderPurpose and information
ClerkAccount authentication, identity information, and sign-in sessions. Decisionate does not store your sign-in password.
Hosting and storage providersApplication delivery, databases, files, stored report definitions and results, analysis-job records, service logs, and backups. Supported infrastructure includes Railway, Vercel, PostgreSQL, and Cloudflare R2 or Amazon S3; the providers and locations used depend on the deployment.
OpenAIThe requested analysis context, including selected dimension values, business questions, aggregate metrics and trends, bounded unusual-change evidence, and relevant decision outcomes or learning notes. User-authored text, filter values and category labels can contain personal information.
StripeSubscription identifiers, checkout, payments, invoices, and billing events. Stripe collects payment-card details through its services; Decisionate does not store full card numbers.
Resend or the configured email providerRecipient details and the contents of requested reports, alerts, invitations, support correspondence, and service emails. With marketing opt-in, Resend also receives your name, email and lifecycle segment memberships; it does not receive raw business datasets or connector credentials for marketing.
Sentry, when diagnostics are configuredError context and service request metadata. The API disables default personal-information collection, local-variable capture, and request-body capture in its monitoring configuration.
Optional cache and analytics providersUpstash Redis may process temporary cache values and operational counters; BigQuery may process configured analytical data. These providers receive data only when the corresponding service is configured.
Connected providersAuthorized imports and provider API requests, including Meta Ads, Google services, accounting, commerce, payment, and CRM connectors selected by a workspace.

Providers may process information outside your country. Their processing locations, safeguards, and retention practices depend on the configured service. We may also disclose information when required by law or to address a security incident or misuse, subject to applicable requirements.

8. Cookies and browser storage

Authentication uses session cookies and related provider mechanisms. Local browser storage remembers preferences such as language, theme, and selected workspace. Browser caches and the application's offline shell may keep static resources and public demo samples. These functions support sign-in and the application experience. Sign out on shared devices and use browser controls to clear stored information when needed.

Saved dashboard preferences, report definitions, and weekly templates are also stored by the service with the relevant account or workspace. Clearing browser storage does not delete those server-side records.

9. Retention and deletion

Connector data is kept for three years, then deleted. The retention window is a rolling three calendar years, using the source date where available. Sync and scheduled maintenance remove expired connector records and partitions from live analytical storage. Records without a usable source date are aged using their ingestion partition month. This rule does not automatically delete manually uploaded datasets, decisions, account information, or workspace configuration.

Saving a report stores its settings and a snapshot of the generated results, rather than a live view that automatically changes with every source update. An authorized user can delete a saved report and its associated saved-report analysis-job records. This does not delete source datasets, linked decisions, or evidence copied into those decisions. If the report is the weekly template, deleting it also removes that template and pauses delivery. Removing only the weekly template pauses delivery but keeps the saved report and decisions. Neither action recalls downloaded files or emails already delivered. Source-record retention should not be treated as deletion of every saved output or copied decision record; contact us about information retained in those records.

Where a trial or paid subscription expires, analytical dataset storage becomes eligible for deletion 89 days after the subscription end date. If a subscription is cancelled, the cancellation deadline is 90 days after the recorded cancellation date; the earlier applicable deadline applies. Scheduled lifecycle processing removes analytical files, dataset records, related analyses, joins, and share records, including client workspaces governed by an expired agency plan. Renewing after deletion does not restore deleted data. This purge does not remove connection settings or credentials; remove the connection separately when you no longer want those retained.

Authorized workspace deletion removes supported live workspace records and data files. Account, billing, security, and support records may need to be retained for their service purpose, legal obligations, or disputes. Backups, replicas, and storage versioning can have separate retention cycles. Deleting live data is not a promise of immediate erasure of every backup copy, and provider source records remain subject to the provider's terms.

10. Product exports and individual privacy rights

Available exports of Decisionate-generated outputs follow workspace permissions; supported decision exports are restricted to workspace owners. Decisionate does not provide raw connector rows or Parquet files as a separate source-data download service. Use the connected provider for source exports.

These product restrictions do not limit an individual's rights under applicable privacy law. You can contact us to request access to or correction of your personal information, ask about its use or disclosure, request deletion, or withdraw consent where applicable. You do not have to be a workspace owner to request your own personal information. We verify identity or authority, protect other people's information, and explain any lawful exception or retention requirement.

Where PIPEDA applies, access requests are generally answered within 30 calendar days, subject to permitted extensions and exceptions. You may raise an unresolved concern with the applicable privacy authority. See the Office of the Privacy Commissioner of Canada's access guidance.

11. Security, updates, and contact

We use application access checks and protected credential storage; deployment safeguards and their limits are described on our Security page. No service can promise absolute security. We update this policy as the product and its data practices change and show the update date above.

Send privacy, deletion, access, correction, or security requests to support@decisionate.ca. Include the relevant account or workspace and a short description. Do not email passwords, access tokens, full payment-card details, or unnecessary copies of personal information.