Self-hosting: current status

• •Today this is NOT a complete, working self-host for the public: key components (fitness-data writes, account export/deletion) remain tied to FitMesh's managed backend, regardless of the Supabase server you configure.
• •Custom-server configuration exists in the app's software, but it's for internal/technical use: it isn't a self-service path open to users.
• •The main fitness-data write path still sends data to FitMesh's endpoint, regardless of the Supabase server you configure.
• •There's no automatic migration of data already synced to your new server.

• •It doesn't automatically migrate existing data from FitMesh's backend to a different server.
• •It doesn't make the app fully offline: some functions remain connected to FitMesh's services.
• •It doesn't disable Firebase Crashlytics (crash diagnostics) or Firebase Cloud Messaging (push notifications): these stay separate from the database, independent of the server you choose.
• •It doesn't change purchases made on the App Store or Google Play.
• •It isn't a generic NAS backup service: it's a configuration mechanism for the app's backend.

On FitMesh's managed backend, you can always export or delete your synced data and account from within the app, on your own, with automatic deletion within 24 hours. On an alternative Supabase backend this isn't today a supported end-to-end path: the app's export and deletion functions rely on the managed FitMesh backend's schema and functions, which aren't automatically replicated on a different Supabase project. For full details, see the Privacy Policy.