Owner help
Running your Villow.
Hosting a Villow means looking after the accounts it runs on and the people who trust you with their data. This guide gives the current starting points; unverified procedures stay marked.
Operational guidance is still being completed.
Setup time, group capacity, costs and recovery procedures haven't been fully tested. This page doesn't promise a one-click update, backup, member-deletion or recovery workflow.
Know which accounts run it
Your Vercel account hosts the app, Supabase holds its database, and Google Cloud provides sign-in and YouTube API access. Keep access to those accounts secure and record which projects belong to this Villow.
You control the database and can access its stored data. Explain this to people before inviting them. Member sharing controls govern the normal app experience, rather than restricting your provider-level access.
Invitations and removing access
Start with the invitation guidance. People should know who runs their Villow and choose their sharing settings.
Admin controls let an owner revoke another member's access, then separately delete that revoked member's data. Deleting the owner through this member-removal action isn't supported.
Disabling sign-in, ending sessions, revoking extension connections and deleting stored data are separate actions. A tested end-to-end removal checklist, including provider backups, is still needed: TBDverified member removal, session revocation and deletion procedure.
Check usage and provider allowances
Review usage and billing in your provider dashboards. The Google Cloud YouTube quota is shared by your installation's users.
Group capacity and paid-plan requirements are untested: TBDrough guide to group sizes. Behaviour and recovery at provider allowances still need a verified guide: TBDwhat happens when a free limit is reached. Don't assume the software being free makes its hosting unlimited.
Updates
Keep track of Villow releases and review their instructions before changing the app or database. The supported owner update and rollback procedure is still being verified: TBDverified update and rollback procedure.
Backups and recovery
Check which backups and restore options your Supabase plan provides. Keep a recovery plan appropriate to your installation. A tested Villow-specific backup and restore walkthrough is still needed: TBDtested database backup and recovery procedure. Don't assume a successful app deployment proves the database can be recovered.
Helping someone leave
Someone can revoke Villow's Google access from their Google account. This prevents further authorized access; it doesn't itself delete data already stored in your database.
Revoke the member in Admin before using the separate permanent-delete action. Full member self-service account deletion hasn't been verified. General retention and provider backup handling still need confirmation: TBDhow long other data is kept.
Closing your Villow
Let members know before closing a shared installation. Uninstalling Villow Setup doesn't shut down the hosted projects.
Review your app, database and Google Cloud projects and connections in their dashboards. Check retained backups and billing before considering the shutdown complete. The exact shutdown sequence is still being verified: TBDverified complete shutdown procedure.
Help make the guide reliable.
Tested setup, update and recovery experience is useful feedback. Share what worked, where you got stuck and which release you used.