MAYE
Delete your account
You can securely start deletion in the app; if you cannot access the app, you can make a support request.
A. Delete in the app
- Open the Profile tab in Maye.
- Tap Delete my account and data.
- Review the information and confirm with Delete everything.
This is the preferred route because the signed-in account can be verified directly. Guest/anonymous accounts cannot reasonably be identified externally and should use this in-app route.
B. External deletion request
If you cannot access the app, send a Maye Account Deletion Request.
Where possible, contact us from the email associated with your account and provide enough account information for verification. Do not send your password, full payment-card information, fridge photos, or unnecessary sensitive information.
What is deleted
The deletion workflow removes:
- Profile and preferences (including allergies and sensitive restrictions, if you gave explicit consent)
- Inventory and scan records/results
- Saved and history recipe records
- Menus
- Weekly plans and plan history
- Shopping data
- Usage records and free-trial records
- Legal acknowledgement records (the Terms of Use and Privacy Policy versions you accepted and consent records)
- Content reports you sent
- Subscription-related app records
Maye then asks RevenueCat to delete its subscription customer record, PostHog to delete your analytics person record and events, and Supabase to delete your sign-in account. Shared canonical recipes and AI-generated recipe images may remain because they are not personal account data.
What remains, and for how long
- Deletion record: a minimal record that the deletion was requested and completed (the internal account identifier, its status and timestamps; no profile, kitchen, photo or contact data). It is kept so the deletion is not repeated or reversed by mistake and so we can show it was carried out. It has no automatic expiry: we keep it for as long as we operate Maye and do not use it for anything else.
- Subscription event identifiers: identifiers of store subscription events received from RevenueCat, with the link to your account removed, are kept so the same event is never processed twice.
- Server logs: technical server logs can include the account identifier for some security and subscription events. They are kept only for our hosting provider’s (Railway) log-retention period; we do not export or archive them.
- Provider backups and processing times: copies in our providers’ backups, where they exist, expire on the providers’ schedules; we do not restore deleted accounts from backups. PostHog and RevenueCat complete deletion requests within their own processing times. Apple’s and Google’s own purchase records are governed by their policies.
- Legal obligations: if the law requires us to keep specific information (for example, in response to a valid legal request), we keep it only for as long as that obligation applies.
