This public summary describes TrailMarke's application controls, provider boundaries, and the security commitments that depend on service settings or the customer agreement. It is not a SOC 2 or ISO report, FedRAMP authorization, penetration-test report, legal opinion, DPA, SLA, or security certification or guarantee.
TrailMarke relies on the following providers for selected infrastructure, identity, billing, and email functions. Their assurance pages are useful starting points, but a provider assurance statement does not certify TrailMarke or establish that a particular customer configuration is covered.
TrailMarke publishes TLS 1.2+ in transit and AES-256 at rest through managed infrastructure. TrailMarke applies organization and role permissions, but coverage for exports, reports, support access, integrations, backups, logs, and provider copies depends on the service settings and customer agreement. MFA, SSO, session lifetime, retention, support access, and backup treatment depend on the provider, plan, and customer settings.
Private storage and time-limited access links are used when enabled. Storage settings, backups, malware controls, logging, monitoring, and complete deletion depend on providers and the applicable agreement. Google and Microsoft calendar connections are optional.
Anonymous Mode uses administrator-issued participant codes. Codes and structured signals can still identify someone in context, and authentication, support, billing, security, and program history may remain. It is not a CUI authorization, a compliance determination, or a promise that no personal data exists.
TrailMarke does not claim SOC 2, ISO, or FedRAMP certification or authorization based on provider assurance statements. This page does not represent that an independent penetration test has been completed. Backup, restore, recovery-time, recovery-point, and failover commitments depend on the hosting setup and signed agreement; this page does not set them.
Choose the program privacy configuration deliberately, and enable optional calendar, file, free-text, analytics, and AI-assisted workflows only when their data use is approved. Hosting geography, retention, support access, backups, and onward transfers vary by provider. Request provider legal entities, locations, transfer mechanism, retention, support access, backup treatment, deletion boundaries, and any required DPA, security exhibit, SLA, incident timing, continuity terms, or audit access in the applicable agreement. Report a suspected vulnerability to security@trailmarke.com; no response-time SLA is promised here.
YarnBurner is a separate product and is not part of TrailMarke's current integration offering or required to use TrailMarke. Any future connection would be separately agreed and disclosed.