In a multi-partner network, who can see what is a security question first and a feature second. TrackBooth treats it that way.
Role-based access with permission profiles scoped per account and per entity.
Choose exactly which fields each profile sees, so margin and sensitive data stay private.
All traffic between you, your partners and the platform is encrypted end to end.
Inbound/outbound logs and conversion status history give a complete, reviewable trail.
The parent and child account hierarchy is the backbone of TrackBooth's security model. A JV partner authenticated into their account cannot see another partner's offers, payouts or margin. The data simply isn't in scope for their session. Visibility is granted deliberately through permission profiles, never by default.
Team members are invited with a defined base role, optional special rules layered on top, and a permission profile that controls both feature access and field visibility. Login credentials for partner users are generated and shared securely during onboarding.
Captured customer data, including emails, click and session identifiers and IP intelligence, is stored to power attribution and forensics, and is processed in line with our Privacy Policy and Data Processing Addendum. Customers act as data controllers for the end-user data they collect through the platform; TrackBooth acts as processor.
We follow least-privilege access internally, log administrative actions, and keep the platform updated against known vulnerabilities. For enterprise engagements we can discuss specific controls, data residency and contractual commitments during scoping.
If you believe you've found a security issue, contact [email protected]. We take reports seriously and will respond promptly.
Raise them on a call and we'll walk through how TrackBooth meets them.