Chapter 10 · Security & Compliance
Security that protects your organization
Passkeys with Face ID, Touch ID or Windows Hello, two-factor sign-in, a fresh confirmation for sensitive actions, encryption at rest and hosting in Frankfurt: Flowersynk protects the data your licence depends on.


At a glance
Passkeys
Face ID, Touch ID, Windows Hello and Android.
2FA
Mandatory for admins and the Qualified Person.
Frankfurt
Data hosted in AWS eu-central-1.
AES-256-GCM
Secrets encrypted at rest, keys rotated on schedule.
01Passkeys
Sign in with Face ID, Touch ID or Windows Hello
A passkey replaces password and code with one touch: Face ID or Touch ID on iPhone and Mac, the fingerprint or screen lock on Android, Windows Hello on the PC – or a FIDO2 security key. Passkeys synced with iCloud Keychain, Google Password Manager or 1Password work on all your devices.
A passkey combines your device with your biometrics or PIN, so it counts as two-factor sign-in – also for admins and the Qualified Person. Settings › Security lists your passkeys with device, last use and whether they are synced.
- Offered right after the first sign-in on the phone
- Security mail whenever a passkey is added or removed
- Adding a passkey needs a fresh confirmation
- Cloned passkeys are detected and switched off


02Sudo mode
Sensitive actions need a fresh confirmation
Before sensitive actions – adding a passkey, changes in the account settings, registering a shared device – Flowersynk asks "Please confirm it's you": with password and authenticator code, or with one Face ID.
The confirmation is valid for a few minutes only and is checked again on the server. A stolen session cookie is therefore not enough to plant a passkey or to weaken the security of an account.
- Password and code, or one passkey
- The code of a fresh login mail instead of the password
- Valid for a few minutes only
- Checked again on the server for every action
03Two-factor sign-in
Two-factor sign-in for every account
Sign in with an authenticator app or a password manager such as 1Password, Bitwarden or Apple Passwords – on several devices if you like.
Recovery codes, "Trust this device for 30 days" and "Lost access?" help in an emergency. Without access to your codes, a recovery letter is sent by post to your organization's registered address after a check.
- Mandatory for admins and the Qualified Person
- E-signatures confirmed with your code if your organization wants it

05Organization policy
You decide who needs two-factor sign-in
Administrators and the Qualified Person always use two-factor sign-in. Switch it on for further roles or require it for every member.
The security settings show which members have set it up.
- Per role or for all members
- Reminder by mail in good time

06Your data
Hosted in Frankfurt, encrypted at rest
Flowersynk runs in the AWS region Frankfurt (eu-central-1), with separate environments for testing and production. Connections are encrypted, and uploaded files are stored encrypted.
Secrets are encrypted with AES-256-GCM: two-factor secrets, the API keys of your sensor integrations, TSE PINs and bank data. Personal data of club members and personnel records are encrypted per person with their own key.
- Hosting in Frankfurt (AWS eu-central-1)
- Encrypted connections and encrypted file storage
- AES-256-GCM for secrets and credentials
- Own keys per person for member and personnel data
- Photos without location and camera data
- AI assistants via MCP only if an admin switches them on
07Roles and permissions
Every member sees exactly what they may use
Fixed and custom roles with a permission matrix for every module. A person may do what all their roles allow, plus extra permissions set for them alone.
"Who has what" and "Compare" make permissions easy to review.
- Default roles such as grower, QA, sales and read-only
- Invitations accepted right from the mail

08Key management
Keys that rotate without data loss
Every key that protects stored data has a documented rotation plan: encryption keys yearly and at once on any suspicion, database and server access keys on a fixed schedule and after every staff change. Former keys keep decrypting until everything is re-encrypted with the new one.
Test and production systems use separate keys, and the application gets only the rights it needs. Every rotation is recorded as a change – date, reason and verification, never the key itself.
- Encryption keys rotated yearly
- Database and access keys rotated on schedule
- Separate keys for test and production
- Least privilege for the application
- Re-encryption with the new key without data loss
- Every rotation documented as a change
Real screens of the Flowersynk app with demo data.
See it with your own data
Book a walkthrough: we show you Flowersynk with the processes of your site – from goods-in to batch release.