Ownership & approvals
Rush owns Rush.
Project Rush maintains full ownership and administrative control of its technology, accounts, data, and digital assets. Collaborators receive scoped access to perform authorized work; access never transfers ownership.
Rush-owned assets
The full digital operation.
- Domains, DNS, websites, and application-store accounts
- Source code, repositories, APIs, integrations, and documentation
- Databases, hosting, cloud infrastructure, analytics, and monitoring
- Payment systems and secure purchasing infrastructure
- Customer, courier, retailer, operational, and reporting data
- Design files, brand assets, administrative systems, and credentials
Named access
Use individual accounts, permissions, and roles whenever the service supports them.
Least privilege
Provide only the access required for authorized work and only for as long as it is needed.
Rush administration
Project Rush retains primary ownership and at least one independent administrative recovery path.
No exclusive control
No developer, contractor, agency, employee, or provider may hold sole ownership or exclusive administrative control of a Project Rush asset.
Secure credentials
Do not share Project Rush primary passwords for routine access. Store and rotate credentials through approved secure controls.
Offboarding
Remove access promptly when work, employment, or a provider relationship ends, and preserve Rush-owned records and assets.
Development handoff & continuity
Built to continue.
At completion or termination of development services, Project Rush retains everything required to operate, maintain, recover, and transfer the platform. Rush must not depend on one developer or development company for access or continuity.
- Complete, current source code and repository access
- Database access, schema, migrations, backups, and database documentation
- Hosting, cloud, deployment, monitoring, recovery, and administrative access
- API, integration, payment-system, App Store, and Google Play information
- Design source files, technical documentation, credentials, and operating runbooks
- Everything required to operate, maintain, or transfer development
Approvals
Julianna and Maya
Primary decision-makers · Project Rush Founders
The development team may recommend technical, security, or infrastructure solutions. The following decisions require documented Project Rush approval:
- Final branding, design, and major UI/UX decisions
- Pricing, delivery fees, memberships, return fees, and promotions
- Courier compensation, cancellation rules, and financial decisions
- Payment systems, major integrations, recurring costs, and security decisions
- Major technical direction, legal and privacy materials, and final launch acceptance
Legal and privacy materials require appropriate professional legal review and final Project Rush approval. Listing a decision here does not mean it has been approved; approval must be separately recorded.
Last updated August 30, 2026. This operational policy should be incorporated into final contractor, provider, security, and governance documentation before launch.
