Private by design.
Updated 21 October 2026
Service contact
Kept. Developed by Ashpey Labs. kept.app.au@gmail.com
Individual accounts
Sign in with your email and password. New signups do not require email verification. An email address alone does not prove identity: invitations are bound to the intended account and private link, and migrated team access can require administrator approval. Secure sessions, recovery codes, password reset and server-enforced roles protect access. Hub selection is checked against membership; supplying another hub ID does not grant access.
Private storage
Images are held in private R2 storage. The server checks hub access before returning a photo, profile image, branding asset or condition evidence. Upload limits, image signature validation and workspace storage reservations protect the service.
Keys and administration
Provider credentials are encrypted with AES-GCM and bound to their hub or service scope. The application returns masked key endings, not secret values. Control Room requires a platform role and a separate current-password unlock that expires after 30 minutes. Privileged changes are audited.
Payments and AI
Subscription access comes from verified Stripe events and current provider state. Returning from checkout alone cannot grant paid access. Managed AI has both workspace allowances and service budgets. BYO hubs do not inherit a platform key.
Report a concern
Send security concerns privately to kept.app.au@gmail.com. Include a description and reproduction steps, but do not email passwords, API keys or another customer’s private records. No security certification is claimed.