Third Party Index

Snapshot 25416

Document
Security page
URL
https://www.simpleinout.com/en/security
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
17655 bytes
SHA-256 (raw)
7a69be62755fbfecff293c9d67c412bcc2da6aff0495f902f2323b75c5e0a95c
SHA-256 (normalized text)
a94f701ffc6fca3e1040c65d821df2da34597fe6ff09ecd22510bb9d8f66e824

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Security we're committed to keeping your data safe
At the very core of Simple In/Out is our commitment to security. Outlined below are a few of the measures we take to ensure your data is safe and secure. This outline is far from a complete list, and if you have any questions don't hesitate to contact us.
Encryption and data storage
Simple In/Out forces HTTPS for all our apps and services using TLS (SSL). Stripe protects all credit card data and entry. Please refer to Stripe's security page for details on their PCI compliance and security measures.
A special note about Geofencing
Geofencing monitors an area and sends notifications to the application when the boundary is crossed, either entering or exiting. Our applications are provided this information only if you have a Geofence enabled. The data transmitted to our servers to process a status update includes the Geofence that was activated as well as when it was activated. Latitude and longitude information is never saved, transmitted, or stored. Period.
Physical location
Simple In/Out's physical infrastructure is located in the United States of America.
Independent security reports (SOC2/3)
For SOC2/3 reports, refer to AWS Cloud Security.
Data breach notification
Our procedures are outlined in our privacy policy and terms of service.
Reporting vulnerabilities
We take any report of a security vulnerability seriously. If you believe you've discovered a bug that impacts Simple In/Out's security, please click the button below to report this to us.
We do ask that you keep the reported issue confidential until we've had the opportunity to address this issue. We will respond as soon as we are able and will patch any problems rapidly. We also ask that anyone looking for security issues do so responsibly. As an example, please refrain from compromising user data, denial of service attacks, social engineering, or spam.
We do not operate an official Bug Bounty program. But you can become part of our Bug Reporter Hall of Fame!
Report a Vulnerability
Bug Reporter Hall of Fame
We are grateful for our bug reporters' help and we want to thank them for their contributions.
2026
Team-DisclosureX — Cybrgen
Muhammad Haneef B A
Manasi Deokate
Aryan Malhotra
2025
Pavan Baile
Parth Narula — ScriptJacker
Parth Narula — ScriptJacker
2024
Parth Narula — ScriptJacker