Security
Security boundaries and responsibilities
This page explains the website's current control boundaries and the questions that must be settled before a business pilot. It is not a certification or a guarantee against incidents.
- Minimize
Start with process descriptions, not private customer records.
- Validate
Treat visitor text and provider output as untrusted.
- Constrain
Limit allowed tasks, data, time and cost.
- Approve
Require authorization for external or irreversible actions.
- Observe
Review failures and reconcile accepted records.
- Recover
Preserve a tested rollback and legitimate data.
Controls must be verified for each implementation; this is not a certification.
The public website boundary
The website is served through Cloudflare. Public discovery submissions are validated on the server and use a Turnstile abuse check. Internal notification-management endpoints are not exposed by the production website Worker. These controls reduce specific risks; they do not make submitted information appropriate for public forms.
- Use the forms only for business contact details and general process descriptions.
- Never include credentials, payment-card information or private customer, patient or employee records.
- Do not interpret an accepted form as permission for an automated action in another system.
Separate development from production
Changes are evaluated locally and in an isolated staging environment before a separately approved release. Synthetic records are used for staging write tests. Production changes require a reviewed artifact and rollback plan, and protected records must be checked for unintended changes.
- The release gate covers routes, metadata, form protection and data integrity.
- Provider activation, production test submissions and external transport have separate approval boundaries.
- A staging result is not evidence that a production integration is available.
Responsibilities before a pilot
A pilot needs an agreed purpose, data inventory, access owner, retention expectation and incident contact. Software permissions should be limited to the selected workflow. Customer-specific security requirements and any legal or regulatory obligations must be assessed for that implementation; no general compliance status is asserted here.
- Confirm which systems can be read and which, if any, can be changed.
- Define safe failure, human escalation and restoration procedures.
- Verify provider processing and regional requirements before sharing business data.
Report a concern safely
Contact hello@akeelos.com with a short description of the affected page and general behavior. Do not email secrets, raw records or exploit payloads containing private information. Ask for an agreed secure reporting method before sending sensitive technical detail. Do not test against other visitors or disrupt the service.