Loading page
How we protect your project
Access
Server-verified sessions
Data
Owner-scoped Firestore rules
Files
Private by default
Handover
Payment verified first
Trust is only useful when it is specific. These are the protections the platform is designed around, from the first submitted brief to the final handover record.
01
No project is auto-accepted. A human review establishes feasibility, scope and fit before any price or commitment is presented.
02
Quotations, deliverables, exclusions, revision limits and timelines are stored as versioned records. Accepted versions are preserved and cannot be silently rewritten.
03
Project files and conversations are restricted at the database and storage layer. Clients cannot access another client's records, and administrators act through server-authorized routes.
04
Payments are never marked successful by a browser callback alone. Provider signatures and server-side verification are required before handover eligibility.
05
Source code, documentation and agreed assets are released only after verified payment, with the receiving user, administrator and timestamp recorded.
06
Privileged actions and project status changes are recorded with actor, reason and time. Administrative actions are append-only by design.
These are implementation controls, not marketing badges. Where a service requires external configuration, the requirement is documented and never replaced with a fake success state.
Google sign-in is exchanged for an HTTP-only session. Protected routes verify the session and account status on the server — not only in the browser.
Firestore rules limit client reads to owned projects and conversation records. Privileged fields such as status, pricing and payment state cannot be written from the browser.
Storage rules restrict project files to the owner and authorized administrators. Upload type and size limits are enforced, and executable uploads are not accepted.
Administrator roles are controlled through Firebase custom claims. The Firebase Admin SDK is used only in trusted server routes with environment-held credentials.
Status changes, reasons, quotations, payment events and handover records are preserved with actor and timestamp. Administrative actions produce audit entries.
Final deliverables are released only after completion review and verified payment. The handover record identifies who released and who received them.
03 / The lifecycle
Every privileged transition is recorded. The client can see the current state and the reason it changed; the administrator cannot silently rewrite history.
01
Identity
Google session verified server-side
02
Submission
Validated, rate-limited and recorded
03
Review
Human decision with written reason
04
Quotation
Versioned and immutable once accepted
05
Execution
Milestones and progress notes
06
Payment
Provider signature or finance verification
07
Handover
Completion + payment + confirmation
08
Audit
Actor, action, entity and timestamp
04 / Reporting
Report suspicious payment requests, impersonation, abusive messages, privacy concerns or intellectual property issues through support. Include the project reference and any relevant message or file. Reports are stored and reviewed by an authorized administrator.
Reviewed, not auto-accepted
Every brief is read by a person. If we can build it, we will tell you what it takes. If we cannot, we will tell you that too.
© 2026 Forma Project Studio. All rights reserved.