Veri-Tech sells compliance, so we hold ourselves to the same standard we ship. Read-only by default, US-based infrastructure, scoped write authorization, and transparent sub-processor disclosure. This page is the source of truth.
Last reviewed: 2026-04-27
When you connect Microsoft 365 to Veri-Tech, we receive permission to read your tenant configuration. We cannot modify, delete, or wipe anything — not policies, not devices, not users, not data — unless you take a separate, explicit action to authorize it.
When you choose to apply a remediation, you grant Veri-Tech write permission for that specific action. The authorization is scoped (only the controls you select), time-bound (auto-expires after one hour), auto-revoked on completion (write permission is dropped the moment the remediation finishes — even if it finishes early), and recorded (audit log captures every change). You can also manually revoke at any time from your tenant’s admin consent panel.
Authentication is certificate-based. Every action Veri-Tech takes against your tenant is signed, logged, and attributable.
Veri-Tech uses the following sub-processors to operate the service. We notify customers in advance of material changes to this list. All sub-processors are bound by data-protection agreements consistent with our customer terms.
| Sub-processor | Purpose | Data handled | Region |
|---|---|---|---|
| Microsoft Azure | Compute, storage, scanning workloads | Scan results, tenant configuration data, audit logs | United States |
| Vercel | Portal hosting and authenticated app delivery | Signed auth tokens and rendered page content in transit; UI assets (no persistent customer-data storage) | US (compute) / global edge (static assets only) |
| Stripe | Subscription billing and payment processing | Billing contact, payment metadata (card data tokenized by Stripe) | United States |
| Postmark | Transactional email (account, support, billing) | Recipient email, message body | United States |
| Microsoft Bookings | Sales-call scheduling | Prospect contact info submitted to book a call | United States |
| GitHub | Support ticket intake and engineering tracking | Ticket content, submitter identifier | United States |
| Anthropic | AI-assisted runbook and SOP generation (when invoked) | Transient prompts; not retained beyond the request | United States |
Veri-Tech ships compliance scoring and remediation across a documented set of frameworks. Coverage is not a substitute for the customer’s own audit, but it provides auditor-ready evidence and continuous monitoring.
Independent attestation (SOC 2 Type 1) and third-party penetration testing are planned milestones. We’ll publish dates and reports on this page when each is complete — we do not pre-claim certifications we have not yet earned.
For suspected security incidents affecting your tenant, vulnerability reports, or any responsible-disclosure submission, contact us at security@veri-tech.net. We acknowledge legitimate reports within one business day. Researchers acting in good faith are welcome — we’ll work with you on coordinated disclosure and recognition.
Book a 15-minute call — we’re happy to walk through any of this in detail before you connect a tenant.