The Requestly Mock/File Server is a tool for developers to test and debug applications. Requestly prioritizes ensuring security and privacy while using the Mock/File Server. Here is a comprehensive guide to the security measures and privacy practices implemented for the Mock server.
Data Encryption
-
All data in transit is encrypted using HTTPS to ensure secure communication and prevent unauthorized interception.
-
Firebase manages encryption for files and data stored in Firestore and Firebase Storage, offering robust protection for stored information.
Authentication & Authorization
-
Firebase Authentication handles user authentication, ensuring secure access to the platform.
-
Mock configurations are accessible to their creators, individuals with whom they share them, and workspace members if created under a workspace.
Access Restrictions
-
By default, cloud mocks are public, meaning anyone with access to the mock URL can view the responses.
-
Password protection can be enabled to restrict access to specific users and secure sensitive mock data.
Privacy Practices
Data Ownership
-
Users retain complete ownership of the mock files and configurations they create.
-
Requestly does not access or use mock data for any purpose other than providing the intended service.
Data Storage
-
All mock server data is stored securely in Firebase Firestore.
-
Files uploaded via the Mock/File Server are stored in Firebase Storage.
No Data Sharing
- Mock data and configurations are not shared with third parties.
Compliance with Privacy Standards
- Requestly adheres to GDPR, CCPA, and other relevant data privacy regulations to protect user data.
Reporting Security Issues
If you identify any security vulnerabilities or privacy concerns with the Mock/File Server, please report them to our team at [email protected]. We take all reports seriously and will address them promptly.
For more details, refer to our Privacy Policy or Terms of Service.