1. Who this applies to
boxli has two categories of users: operators (the B2B revenue teams who run campaigns through the platform) and recipients (the individuals who receive a physical boxli send). Different parts of this policy apply to each.
2. Data we collect from operators
- Account data: name, email, organization, role, billing contact information.
- Campaign data: contact lists, target accounts, video content, message templates.
- Integration tokens: OAuth credentials for HubSpot, Salesforce, Slack — encrypted at rest with per-org keys.
- Usage data: dashboard activity, feature usage, error logs.
3. Data we collect from recipients
- Identity data: name, role, company, mailing address — supplied by the operator from their CRM.
- Engagement signals: lid open events, video play sessions, NFC tap events, QR scans, time-on-page on the personalized landing page.
- Geo data: coarse latitude/longitude and resolved place_id from device telemetry, used for pass-around detection.
- Device data: user-agent and OS for video play sessions.
4. How we use it
Operator data: to provide the platform, bill subscriptions, support pilots, and communicate about service changes.
Recipient data: to deliver the physical send, render the personalized landing page, generate engagement signals for the originating operator's CRM, and — in aggregate, anonymized — to improve our default trigger thresholds and signal scoring formula.
5. Recipient rights
Recipients can opt out of all future boxli sends from any operator by emailing optout@sendaboxli.com. We honor the request within five business days. Opt-out is enforced centrally and applies across all operators using the platform.
6. Sharing
We share recipient engagement data with the originating operator only. We do not sell recipient data, do not share it across operators, and do not provide it to third parties except as required to deliver the service (FedEx for fulfillment, Stripe for payment processing, Resend for transactional email).
7. Retention
Engagement events are retained for the duration of the originating operator's subscription plus 90 days. After that, recipient-identifying fields are anonymized; aggregate event counts are retained indefinitely for product analytics.
8. Security
Data is encrypted in transit (TLS 1.3) and at rest. Per-org row- level security in our Postgres database isolates each operator's data. SOC 2 Type II is planned for 2026; full security posture at /security.
9. Contact
For privacy questions, data access requests, or to exercise any right under this policy: privacy@sendaboxli.com.