Identity and access
Unverified · design and test least-privilege, resource-level authorization and cross-user and partner isolation before real accounts or records.
Founder preview · Phase A review
Security and recovery readiness.
A record of the current preview, proposed safeguards and unresolved release gates.
No compliance or security certification
This static owner-only preview is not a production security assessment. Backups, restoration, role-based permissions and incident response have not been verified.
What exists today
- A static site on Sites with owner-only access confirmed in the current access settings.
- A source repository and local development preview; source version history is not a complete backup.
- Browser-local saved choices and a search feature whose query can appear in the browser URL. Avoid entering sensitive information.
- No connected Nuvendi operations, customer database, payment system or live customer intake is implemented in this preview.
Hosting limits, commercial eligibility, independent backups and restore capability still need verification. The owner-only site setting is not an application-level role or tenant system.
Critical release gates
Privacy and legal review
Unverified · assess purposes, consent, notices, retention, rights, sharing and applicable Kenyan requirements with qualified counsel.
Recovery
Unverified · inventory data, agree recovery objectives, make appropriate backups and demonstrate restoration before relying on them.
Security and quality
Unverified · complete security, dependency, secret, accessibility, mobile and performance checks appropriate to the release.
Keep Nuvendi separate
Future connections must use separately approved, narrowly scoped access and server-enforced permissions. A website compromise must not provide access to canonical customer, operations or financial records. There is no Nuvendi connection in this prototype.
Recovery and incident plan
For a suspected incident: detect, assess, contain, preserve evidence, escalate to the responsible owner, recover, communicate appropriately and review. Owners, notification duties and runbooks need approval and testing.
Recovery planning must cover a bad deployment, deleted or corrupted data, compromised credentials and hosting or domain outages. A saved source version is useful for rollback but does not prove data backup or restoration.
Launch decision
Phased work
- Phase A: inspect the private preview and document threats, gaps and recovery plans.
- Phase B: add identity or data only after separate approval and security design.
- Phase C: establish approved monitoring and tested backups.
- Phase D: independently verify production release gates after separate authorization.