Security and privacy
Your file is yours. We built Stedlan to keep it that way.
Updated
Stedlan will hold the most sensitive data a person has: IDs, salary, bank statements and credit reports. This page explains how Stedlan is designed to protect it. Stedlan is not open yet, so where something will be in place before launch, we say so.
01Access
Signing in
Passkeys and Face ID
You will sign in with your mobile number or email and a one-time code, then add a passkey so Face ID or Touch ID signs you in. Once you have a passkey, sensitive actions will need it, so a stolen SIM card will not be enough.
An app that locks itself
The iPhone app will open only after Face ID, Touch ID or your passcode, and lock itself after five minutes in the background.
No tokens in your browser
On the web, your session will live in a secure cookie that page scripts cannot read. No sign-in token will be stored in your browser.
02Your data
Protecting your data
Encryption
Everything between your device and Stedlan will be encrypted in transit, and data encrypted at rest. ID numbers, account numbers and documents will get an extra layer of application-level encryption, with their own keys.
Your data, kept apart
Every record will carry the account it belongs to, and the database itself will enforce the separation: the application’s own database account cannot read across that line.
Keys in a vault
Signing and encryption keys are designed to live in a key vault, never in application settings, and to be rotated on a schedule.
A record of every access
Sign-ins and security events will be written to an append-only, tamper-evident log. Every view of client data will be logged too, and you will be able to see who accessed your file.
03Sharing
Sharing and where data lives
Consent, per bank and purpose
Nothing reaches a bank without your consent for that bank and that purpose, signed with Face ID or a passkey. Withdraw it, and that bank’s access through Stedlan ends immediately.
Where your data lives
During the pilot, documents will be stored in the European Union, and pilot users will be told so before they agree. In production, Jordanian clients’ data will live on servers in Jordan.
AI with limits
The AI never decides and never touches Stedlan’s database. It sees only what a step needs, with ID and account numbers masked, under no-training, zero-retention terms.
Sharing, step by step · illustrative
04Commitments
What we never do
- Sell or rent your personal data.
- Share your file with a bank without your consent.
- Use your data to train the engine without your separate consent.
- Alter, leave out or “clean” anything in your file.
05Testing
Testing and standards
We build to the OWASP application security standards for the web (ASVS Level 2) and for mobile apps (MASVS Level 2). An independent penetration test will be done before the pilot launches. We are working towards ISO 27001; we are not certified yet.
06Reporting
Report a concern
If you think you have found a security or privacy problem, write to privacy@stedlan.com.