Public website and mandate intake
Privacy notice
This notice describes the current public website and bounded business-contact intake. It is not a notice for a client execution environment or regulated data-processing service.
Business requests only
The mandate composer collects an objective, mandate category, approximate scope, desired timing, organization, sponsor name and role, work email, and contact consent. It is not approved for passwords, credentials, account numbers, patient information, government identifiers, or other regulated personal records.
Purpose and authority
Information is used to review the objective, determine whether there may be a fit, and respond to the business contact. Submission does not create an engagement, approve a plan, delegate authority, or permit Onuosa to act.
Storage and retention
Configured intake stores requests in an Admin-only Google Cloud Firestore collection. Browser clients have no direct read or write access. Requests and rate-limit records carry an expiry timestamp; production operation requires TTL policies on those fields. Standard hosting and service logs may retain request metadata separately.
Abuse controls
The service validates request size and fields, uses a hidden honeypot, rejects unapproved origins, and rate-limits submissions using keyed hashes rather than storing raw rate-limit identifiers. These controls reduce abuse; they are not identity verification.
Access and disclosure
Access should be limited to personnel responsible for reviewing mandate requests and maintaining the intake service. Information is not collected for advertising, sale, or discretionary automated decision-making. Regulated or licensed activity remains subject to separate authorization and professional review.
Correction and deletion
If Onuosa responds, use that business-contact thread to request correction or deletion of the submitted information. A dedicated privacy contact must be confirmed before production intake is publicly enabled.
Last updated September 19, 2026.