makesplit
Security

Trust & Security Standards

Last Updated: October 15, 2026

At makesplit, we understand that your financial ledger data is the lifeblood of your business. We build our infrastructure using bank-grade security protocols, ensuring that your automated data pipeline remains safe, isolated, and completely secure from checkout to reconciliation.

1. Data Protection & Encryption Rails

We secure your data both in transit and at rest using modern, industry-standard cryptographic tools.

  • Bank-Grade Encryption in Transit: Every piece of data flowing between your Boulevard POS terminal, the makesplit engine, and your accounting platform (QuickBooks/Xero) is forced over end-to-end TLS 1.3 and AES-256 bit encryption pipelines.
  • Cryptographic Ledger Ingestion: When transaction events trigger our webhooks, payloads are parsed immediately in sub-second memory queues. Any database storage of configuration parameters or mapping rules is encrypted securely at rest.

2. Platform Integration & Authorization Architecture

We enforce strict data minimization rules, meaning we only access the precise info required to process your splits.

  • OAuth 2.0 Secure Handshakes: makesplit connects to Boulevard, QuickBooks, and Xero via secure, limited-scope OAuth 2.0 API protocols. You never have to share your primary administrator passwords with us. You grant permission directly through the platform providers, and you can revoke our access tokens instantly with a single click.
  • Read-Only Transaction Isolation: Our Boulevard interface uses read-only access scopes. makesplit reads transaction totals, service categories, and line-item splits to compute your formulas—we do not have permission to alter your inventory, modify customer appointments, or touch payment settings.

3. Strict Credit Card & PII Exclusion

We maintain an intentionally tiny data footprint to remove compliance risks for your establishment.

  • Zero Cardholder Data Storage: makesplit is entirely out of scope for complex PCI-DSS compliance because we never see, process, transmit, or store raw credit card numbers, CVV codes, or expiration dates. All payments are handled entirely by Boulevard’s encrypted hardware and processing terminals.
  • Minimalist Customer PII: We strip away unnecessary personally identifiable information (PII). Our ledger maps transaction calculations to internal staff IDs and ticket reference hashes, keeping your client database completely private.

4. Infrastructure & Server Security

Our processing pipeline is housed in modern, hardened server environments built for maximum uptime.

  • Infrastructure Isolation: The makesplit core engine runs on secure, virtualized container environments managed by DigitalOcean within highly secure, SOC 1, SOC 2, and ISO 27001 compliant data centers.
  • Immutable Audit Logging: Every single calculation, rule alteration, and ledger injection creates a permanent, dual-entry tracking hash. This digital paper trail allows your bookkeepers to trace any synchronization anomaly instantly.
verified_user

Vulnerability Disclosure & Compliance Focus

We continuously audit our dependencies and backend codebase to ensure absolute software integrity. If you are a security researcher or have a question regarding our automated data pipeline safeguards, please contact our technical response team directly at security@makesplit.com.