Privacy Policy
CanonLayer ("CanonLayer", "we", "us", or "our") provides B2B knowledge verification, technical hub hosting, visibility analytics, and customer-authorized multi-channel publishing software available at https://canonlayer.com (the "Services"). This Privacy Policy explains what information we collect, how we use and protect it, and the rights and controls available to workspace administrators and authorized users.
1. Information We Collect
- Workspace & Account Information: Business contact details provided when registering a workspace or requesting access, including name, corporate email address, organization name, job title, billing address, and workspace role permissions.
- Subscription & Billing Data: Subscription tier, invoice history, and payment method metadata processed by our PCI-DSS Level 1 payment processor, Stripe. CanonLayer does not receive or store full credit card numbers or card security codes on our servers.
- Customer-Uploaded Technical Documentation & Fact Vault Content: First-party technical specifications, product documentation, certifications, pricing schedules, and media assets uploaded or approved by your organization for grounding verification and publication.
- Connected Platform OAuth Authorization Credentials: When an authorized workspace user explicitly connects a third-party publishing destination—such as Google / YouTube, LinkedIn, Meta (Facebook / Instagram / Threads), or X—via OAuth 2.0, we receive scoped OAuth access tokens, refresh tokens, token expiration timestamps, and the basic destination channel/page identifier (such as YouTube channel ID/title or LinkedIn organization URN) required to route customer-authorized publications.
- Operational & Security Telemetry: Service audit logs, API request timestamps, deployment receipts, and aggregated crawler/http status metrics necessary to maintain security, prevent abuse, and deliver customer analytics. We do not log raw OAuth secrets or sell visitor tracking profiles.
2. How We Use Information
We process collected information strictly to deliver, secure, and support the Services requested by our B2B customers:
- Authenticating workspace users, provisioning customer knowledge hubs, and enforcing pre-publication factual grounding checks;
- Publishing, updating, or retracting technical briefings, posts, and specification videos solely on external channels explicitly connected and authorized by the customer;
- Generating visibility, indexing, and citation analytics reports for the customer's workspace;
- Processing subscription billing, sending transactional service notices, and responding to support inquiries;
- Maintaining platform security, cryptographic audit trails, and compliance with applicable legal obligations.
No Sale of Data & No Foundation Model Training on Private Credentials: CanonLayer never sells personal data or connected-account OAuth data to third parties or data brokers, and never uses private workspace credentials or non-public Google/social API user data to train generalized third-party foundation models.
3. Google API Services User Data Policy (Limited Use Disclosure)
Google API Limited Use Commitment: CanonLayer's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, when a customer authorizes CanonLayer via Google OAuth 2.0 (including YouTube Data API v3 scopes or Google Search Console verification/sitemap scopes):
- Strictly Scoped Purpose: Google user data and OAuth tokens are used exclusively to perform user-facing actions explicitly configured by the customer—such as uploading customer-approved technical videos and metadata to the customer's own YouTube channel, reading basic channel identity to confirm the connected account, or submitting verified XML sitemaps.
- Prohibition on Unauthorized Transfer & Advertising: CanonLayer does not transfer Google API data to third parties (except as strictly necessary to provide or secure the user-requested feature, or as required by law), and never uses Google API data for serving advertisements, creditworthiness scoring, or third-party profiling.
- Restricted Human Access: Human personnel do not read Google API user data unless we have your affirmative agreement for a specific support request, doing so is necessary for security/abuse investigation, or required to comply with applicable law.
- Instant OAuth Revocation: Workspace administrators can disconnect Google/YouTube integrations at any time through CanonLayer support or revoke CanonLayer's access immediately via Google Security Settings at https://myaccount.google.com/permissions.
4. Credential Encryption & Infrastructure Security
All network traffic is encrypted in transit via TLS 1.2/1.3 with Strict-Transport-Security enforcement. Connected platform OAuth access and refresh tokens are encrypted at rest using authenticated envelope encryption (AES-256-GCM) with strict role-separated database access controls, least-privilege service accounts, and automated token-rotation fencing.
5. Data Sharing & Subprocessors
We share data only with vetted infrastructure and service subprocessors bound by confidentiality and data-processing agreements (such as cloud compute/storage hosting, Stripe for billing, transactional email delivery, and the external platforms to which you explicitly instruct CanonLayer to publish content), or where disclosure is required by valid legal process.
6. Data Retention, Export & Deletion Requests
We retain workspace data for the duration of an active subscription agreement. When a connected OAuth account is disconnected or revoked, associated active OAuth tokens are purged immediately from dispatch eligibility. Upon workspace termination or written request to [email protected], CanonLayer deletes or anonymizes customer account and Fact Vault records within thirty (30) days, except for minimal billing invoices and security audit records required by statutory retention laws.
7. International Data Transfers & Privacy Rights
Depending on your jurisdiction (including Hong Kong PDPO, Singapore PDPA, GDPR/UK GDPR, and applicable US state privacy laws), you may request access to, correction of, export of, or deletion of your personal information. To exercise any privacy right or submit a data protection inquiry, contact our privacy team at [email protected].
8. Changes to This Policy & Contact
We may update this Privacy Policy periodically to reflect new platform integrations or regulatory requirements, and will revise the "Last Updated" date above. Questions regarding privacy, OAuth security, or data handling may be directed to [email protected] or [email protected].