Source
Security / trust page — SimpleLocalize
Checked for SimpleLocalize on 1 Nov 2026
- Page
- https://simplelocalize.io/security/
- Checked
- 1 Nov 2026, 10:04 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:4ccc5757b5f22da573388f3769ebe737b22d238f821af3e28a2f05b82af00169
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Provider Report an error
“SimpleLocalize (we) uses Amazon Web Services (AWS) as our cloud hosting provider.”
-
Source code storage Report an error
“Source code is stored on GitHub, which also uses industry-standard physical security and data center facilities, and local copies of the source code are stored on encrypted hard drives.”
-
Redundancy backups Report an error
“SimpleLocalize stores all data on redundant systems to help prevent data loss. Data are also automatically backed up on AWS servers with the capability to provide point-in-time recovery down to the second. SimpleLocalize’s production data is also regularly backed up to a separate location and all backups are encrypted.”
-
Payment provider Report an error
“SimpleLocalize uses Paddle as our payment provider, to accept and process credit card payments. We implement these payment technologies in a such way that SimpleLocalize does not store or process any credit-card information.”
-
Encrypted in transit Report an error
“All data sent to and from SimpleLocalize is encrypted in transit using industry-standard HTTPS/TLS encryption.”
-
Immutable infrastructure Report an error
“We practice immutable infrastructure, where we don't make changes to live code or running servers in production.”
-
Access control Report an error
“All access to production systems requires VPN access. All access to production systems is logged and audited.”
-
Password hashing Report an error
“We use bcrypt to hash all passwords before storing them in our database.”
-
Authentication controls Report an error
“We rate-limit authentication attempts to prevent brute-force attacks, every authentication attempt is logged and audited, and requires a reCAPTCHA verification.”
-
Hashed tokens Report an error
“We store access tokens in our database in a hashed form.”
-
Disaster recovery Report an error
“We have a disaster recovery plan in place, which includes regular backups of all data, and a plan for restoring service in case of a disaster.”
-
Entity Report an error
“Copyright © 2026 Jakub Pomykała Software registered in Poland. All rights reserved.”
-
GDPR posture Report an error
“Developed and maintained, adhering to the highest standards of data protection and privacy regulations, including GDPR.”
Scores citing this record
- The App Developer Confidentiality of translated content
- The Data Protection Officer Confidentiality of translated content
- The In-House Document Translator Confidentiality of translated content
- The E-Commerce Marketer Confidentiality of translated content
- The Localization Manager Confidentiality of translated content
- The Localization Manager European sovereignty
- The Skeptic Confidentiality of translated content
- The Skeptic European sovereignty