Security
Last updated October 31, 2026
How Bike keeps your company’s data safe, in plain words: what it does today, and what a pilot-stage company doesn’t have yet.
Each company’s data is kept apart
Every record in Bike belongs to one company, and the database itself only shows a company’s records to that company (row-level security). Bike checks it again in its own code on every read and write, so a mistake in one place is caught by the other.
Each company has its own address (yourcompany.bikeapp.si), and a sign-in at one address never works at another.
People see only their part
Within a company, each area of work has roles: who sees every record, who sees only their own, and who sees their team’s. Bike checks them on every read and write, for screens, reports and AI alike. Only admins can change how Bike works, see the Audit log or change Settings.
Signing in
There are no passwords to steal. Bike sends a code to your work email: 6 characters, valid for 10 minutes, used once, with five tries. Requests for codes are limited per email address and per network address. A sign-in lasts up to 30 days at that company’s address, and Log out ends it.
Only people their company has added can sign in, and during the pilot only invited companies can be created.
AI proposes; people decide
AI in Bike writes plans, rules and report queries. It never writes to your data itself: Bike’s own engine checks everything it proposes against how your company is set up, and nothing is live until a person confirms it.
Text in documents you upload is treated as data, never as instructions. A line that tries to tell Bike what to do is flagged in the Audit log and ignored. What the AI is sent is described on our Privacy page.
Records that can’t be rewritten
Every change, by hand or by AI, every rule that ran, every sign-in, and every export and report download is written to the Audit log, which admins can read. The database itself refuses to change or delete Audit log entries, and refuses to delete records outright (a deleted record is marked, not erased). We check on the live database that the app’s access is locked this way.
Uploaded files
Files are limited to PDF, Word, Markdown, Excel, CSV, zip and images, up to 25 MB. Each file must really be the kind its name says, and is scanned for viruses before it is kept; if the scanner can’t be reached, the file isn’t accepted. Files are stored privately and open only for people who may see the record they’re on.
Where it runs
Bike runs on Fly.io in Singapore, with a managed Postgres database that is backed up automatically, and private file storage. Everything travels over HTTPS. The virus scanner is reachable only inside Bike’s private network. Keys and passwords live in the hosting provider’s secret store, never in our code. Emails are sent through Postmark, signed for bikeapp.si.
Bike and its virus scanner are checked from outside every few minutes, and we’re alerted when either stops answering.
Tested on every change
Automated tests try to break in on every change: every action called as the wrong person, the wrong company and the wrong address, with forged requests; AI answers written to break the rules; and documents with planted instructions. Every deploy runs them first, and stops if one fails.
What we don’t have yet
Bike is in a pilot. We don’t yet hold security certifications such as SOC 2 or ISO 27001, and haven’t yet had an outside penetration test. We’ll say here when that changes.
Report a problem
If you think you’ve found a security problem, please write to pilot@bikeapp.si with what you saw. We’ll reply and fix it as fast as we can, and we won’t take action against good-faith reports.