1. Encryption in transit
All traffic between respondents, vendors, clients and Requesk, and between your browser and the Requesk app, is encrypted over HTTPS.
2. Workspace isolation
Each customer workspace is logically separated. Data in one workspace cannot be seen or reached from another, and respondent data from one customer is never used for another customer.
3. Access control and audit trail
- Role-based permissions let you decide what PMs, sales and finance users can see and change.
- Actions in the workspace are recorded in an activity log, so you can see who changed what and when.
4. Protecting respondent data
- Device fingerprints are stored as hashes, not as raw device data.
- Respondent data is used only to screen, route and report on traffic for the customer who sent it.
5. Infrastructure
Requesk runs on [Hosting provider and region, e.g. AWS, Mumbai (ap-south-1)].
Enterprise customers can have a dedicated server and a dedicated database with its own backups, kept separate from other customers.
6. Reporting a vulnerability
If you believe you have found a security issue in Requesk, please email reach@requesk.com with the details and steps to reproduce it. Please give us reasonable time to fix it before sharing it publicly, and don’t access or change other customers’ data while testing. We will acknowledge your report and keep you updated.