SYNTRIX

Support & Trust Center

SYNTRIX is designed for high-trust environments. This page explains how support works, how we approach security and risk, and where to find governing policies.

Last updated2026-01-06
CheckPlatform Status

We believe trust is earned through consistency, not claims.

Launch posture

Before you reach out

Most questions are resolved in minutes through status checks and self-service answers.

Check Platform Status

If something is broadly impacted, it will be reflected there.

Use the knowledge base

Account access, billing, integrations, and data availability answers live below.

Jump to Section 3 for FAQs.
Structured escalation

If the issue cannot be resolved through self-service, submit a structured request.

Support is handled asynchronously to ensure clarity and consistency.
Support Request Template
Choose your preferred intake. Email draft opens prefilled. PDF is available for internal workflows.
Security note: do not include passwords, access tokens, API keys, or sensitive customer data in email.
Section 1

Support model

Lean by design. Structured for clarity, security, and predictable handling.

Support is provided through controlled channels to protect sensitive information and maintain consistent handling. We do not provide platform support through social media, direct messages, or informal channels.

At launch, SYNTRIX support is handled asynchronously and prioritized based on impact, urgency, and scope.

Platform status first

Check known incidents and maintenance windows before submitting a request.

General support requests

Product questions, access issues, billing inquiries, and bug reports.

Include: page, expected behavior, actual behavior, and screenshots if available.
Security and vulnerability reporting

Private channel for responsible disclosure and coordinated remediation.

Do not include credentials or sensitive customer data.
Requests are reviewed and prioritized based on impact, urgency, and scope. Response targets reflect operational intent, not contractual guarantees.
Section 2

Response expectations

High-trust expectations without over-promising.

General inquiries
Within 1 business day

Product questions, general guidance, non-urgent requests.

Billing or access
Within 8 business hours

Subscription state, access entitlements, checkout and portal issues.

Platform-impacting
Prioritized by severity

Scoped by impact and breadth across customers.

Operating hours: Monday–Friday, standard business hours (Central Time), excluding U.S. federal holidays.
Section 3

Self-service knowledge base

High-signal answers to common platform questions.

Does SYNTRIX generate or simulate operational data?
View
No. SYNTRIX does not fabricate operational signals, metrics, or insights. If data is not present in the underlying provider system, is outside scope, or cannot be retrieved due to permissions, configuration, or availability, SYNTRIX will reflect that reality rather than inventing values.
Why might a tile, metric, or insight appear empty or unavailable?
View
This typically indicates one or more of the following:
  • A provider is not connected, was disconnected, or has not completed consent.
  • Required permissions were not granted or were later reduced.
  • The provider does not expose the data for your tenant, plan, or configuration.
  • The signal exists but has not been produced or reported in the source system.
  • Data is present but not yet within the supported scope for that integration surface.
  • Temporary provider API limitations or upstream delays.

This behavior is intentional and designed to preserve analytical integrity.

Best practice: Which account should connect providers to SYNTRIX?
View

Use an org-owned service account (not a personal user) as the integration identity. For most providers, the account must be admin-capable to grant tenant-wide consent and enable the telemetry SYNTRIX needs to populate signals.

Success guardrail
If you connect a non-admin account, SYNTRIX may appear partially empty due to missing tenant-wide visibility.
  • Keep ownership with the organization (controlled access, auditable changes).
  • Use least privilege within the admin-capable requirement by granting only the scopes required for read-only telemetry.
  • SYNTRIX is read-only for provider integrations and does not execute configuration changes in connected systems.
  • Access can be revoked at any time by disconnecting the integration in the provider admin console.
How is authentication handled?
View
SYNTRIX uses modern authentication mechanisms for platform access and does not request raw credentials for connected providers. Provider connectivity is established through secure authorization flows and can be revoked by disconnecting the integration.
How is billing handled?
View
Billing and invoicing are processed through a secure third-party payment provider. Customers can view plan details, invoices, and subscription status through their account settings.
Are refunds available?
View
Refund considerations are evaluated case-by-case based on plan terms and platform usage. For billing questions, contact support through the support channel listed above.
How do I submit a feature request?
View
Use the same support channel with a clear subject prefix and impact statement.

Strong requests include: the workflow, who benefits, frequency, and expected impact.

Section 4

Security posture

Trust without over-disclosure.

Security is treated as a core system property, not a feature. Our approach emphasizes least-privilege access patterns, secure authorization flows, environment isolation, and controlled integration boundaries.

We intentionally avoid publishing sensitive architectural or control-level details that could increase platform risk.

Data handling
  • Customer data is not sold or shared for advertising purposes.
  • Access to customer data is restricted and governed.
  • Data handling is designed to align with enterprise expectations.

Specific technical controls may vary by deployment and configuration.

Responsible disclosure

If you believe you have identified a security issue, report it privately. Public disclosure without coordination may increase risk to all users.

Section 5

Policy and governance

Clarity without overwhelm.

The following documents define how SYNTRIX operates and how risk is managed. These are living artifacts and may evolve as the platform scales.

Data Processing Addendum (where applicable) is available for enterprise customers upon request.
Policy set last updated: 2026-01-06
Section 6

What SYNTRIX does not claim

Decision support, not decisions.

  • SYNTRIX does not guarantee uninterrupted availability.
  • SYNTRIX does not replace human judgment or professional advice.
  • SYNTRIX does not act as a compliance certification authority.
  • SYNTRIX does not provide legal, financial, or regulatory determinations.
The platform provides decision support, not decisions.
Section 7

Contact and escalation

Structured escalation based on impact, urgency, and scope.

For matters requiring formal review or enterprise coordination, contact is handled through structured requests. Escalations are evaluated based on impact, urgency, and scope to maintain consistent handling.