Compliance & Legal

Where to find each piece of compliance and legal documentation, and an honest account of what is a real, working control today versus what is a draft template awaiting a business or legal decision.

1. Compliance documentation index

DocumentWhat it covers
PCI DSS ScopeHow card payments are handled, and why this platform's architecture keeps card data out of scope.
SOC 2 OverviewSecurity, availability, processing integrity, confidentiality, and privacy controls, mapped honestly against what exists today.
Information Security PolicyAccess control, data classification, and incident response, the written policy behind the technical controls.
KYC / AML / OFAC ProceduresWhat screening is inherited from the payment processor, and what would need to be built for higher-risk business models.
Acceptable Use PolicyThe rules for using the platform, and how violations are enforced.
Data Processing AgreementRoles, data subject rights, and security measures for personal data, in DPA structure.
BillingPlans, proration, overdue-account handling, invoicing, and what billing automation is and isn't built yet.
Settlement SystemHow the financial ledger is reconciled, retried, and protected against tampering.

2. Sub-processor list

The vendors that currently handle data on this system's behalf, kept accurate to the real infrastructure in use.

Sub-processorService ProvidedData Processed
Stripe, Inc.Payment processing and billingCustomer name, payment reference tokens. See PCI DSS Scope for why full card data is never processed here.
HetznerServer hosting (self-hosted application and database)All application data, encrypted at rest where noted in the SOC 2 Overview
AnthropicAI inference for lead qualification and scoringSanitized lead messages used for qualification
Google (Gmail SMTP)Transactional email deliveryRecipient email address, notification content
ZendeskSupport ticket managementSupport ticket content for tenants using this integration
TwilioSMS delivery for the Outreach BotRecipient phone number, message content, for tenants who connect their own Twilio account
This list should be re-verified against your actual production deployment before publishing, hosting provider, region, and any additional vendors can change as the infrastructure evolves.

3. Service Level Agreement (SLA)

Rather than starting from an arbitrary target, here is the platform's actual, measured uptime over the most recent continuous observation window, taken directly from the automated health-check history (also visible on the Status page):

MetricObserved value
Observation window9.2 days, 2,640 automated health checks at 5-minute intervals
Measured availability100% (0 failed checks)
This is a real measurement, not a marketing figure, and it will naturally include any future incidents going forward, it is not guaranteed to stay at 100% forever. A formal SLA turns a number like this into a contractual commitment with a remedy (typically a service credit) if it is not met. That commitment has two parts still to be decided by the business before it is a real SLA rather than an observation:
  • What target to commit to, a common starting point is 99.9% monthly uptime excluding a defined maintenance window, but this should reflect your own risk tolerance and what your infrastructure can realistically sustain.
  • What remedy applies if the target is missed, typically a tiered service credit (for example, a percentage of that month's fee) scaled to how far below target the actual uptime fell.

Until those two decisions are made and published, the honest position to give a customer is the measured historical figure above, not a promised number.

4. Tax documentation & 1099-K reporting

Payment transactions processed through Stripe are subject to United States IRS Form 1099-K reporting once a merchant crosses the applicable annual threshold, per Stripe's own reporting obligations as the payment processor of record. In practice this works as follows:

  • Stripe, not this platform, is the entity responsible for issuing 1099-K forms, since Stripe is the payment processor that actually settles funds.
  • Because all payments are collected via Stripe Checkout (see PCI DSS Scope), Stripe has the complete transaction record needed to determine when reporting thresholds are crossed, without this platform needing to separately track it for tax purposes.
  • Sales tax / VAT collection on subscription fees is not currently automated by this platform. If you are required to collect sales tax or VAT in your jurisdiction, that would need to be configured either through Stripe Tax or a separate tax-calculation integration, neither of which is wired in today.
Confirm with your accountant whether any additional tax documentation, beyond what Stripe provides, is required for your specific business structure and the jurisdictions you operate in, before presenting this section as settled guidance to customers.

Was this page helpful?