Fomibee
1. Keep what you need first
Deletion is permanent. Export any individual notebook pages you want to keep as PDF or images before clearing a workspace. A page export is a separate file, not a complete account backup.
Deleting an account does not cancel a subscription. You can delete an account independently of its store subscription. If you also want to stop future billing, cancel through the original store. Uninstalling the app or signing out does not cancel billing either.
2. Delete a guest workspace on this device
- Open Fomibee in the guest workspace you want to remove.
- Open Profile → Privacy & support → Delete guest data.
- Read the confirmation, then choose Delete.
- Wait for the app to confirm that the workspace was deleted. If device cleanup fails, retry it in the app.
This clears that guest workspace’s local notes, handwriting, plans, study records and settings, and attempts to remove the notebook photos it can still identify, on the current device. It is not a deletion request for a signed-in cloud account or another device’s workspace.
Photo files no longer referenced by a note may remain after this cleanup. To remove those local files, clear the app's or browser's storage using the device controls, or remove the app, and review any device or cloud backups separately.
3. Signed-in account controls
The current test build exposes Profile → Privacy & support → Delete account. It asks for the current password and a separate deletion confirmation. If the same identity is used in another app, stop before confirming while the safety limit above remains unresolved.
For a test account used only for Fomibee, read the confirmation, enter the current password inside the app, then choose Delete. Keep the app open until it reports completion. Signing out is not account deletion.
If cloud deletion succeeds but the current device cannot finish cleanup, the app shows Finish device cleanup. Retry that cleanup. A generic network error or an unfinished confirmation screen is not evidence that all data was deleted.
Never send a password, one-time code, recovery code or payment-card number in a support or privacy request.
4. What the action is designed to remove
On a successful configured account-deletion flow, the app removes the account’s private notebook photos from cloud storage and deletes the sign-in identity and its associated Fomibee notes, planner tasks, study records and subscription-access records. The app then clears the current device’s account workspace.
The server also attempts to remove the associated RevenueCat customer when that integration has been configured. This does not erase the original store’s purchase history or cancel its subscription. A public-release deletion flow still needs end-to-end validation, including a separate sign-in identity for Fomibee.
5. Information that may remain elsewhere
- Exports and shared copies: PDFs, images and files you saved or sent elsewhere remain in those locations. Delete them there if desired.
- Other devices and backups: an offline device or a device/browser backup may contain an older copy. Review its local storage and backup controls separately.
- Store and provider records: Apple, Google and service providers may retain transaction, security, fraud-prevention or legally required records under their own rules.
- Operational backups and logs: provider-managed copies may remain for their configured backup or security lifecycle. This development service has not published a fixed completion time for those copies.
See the privacy policy’s retention section for the broader handling of saved work and connected services.
6. Requests when you cannot open the app
A monitored web deletion-request channel is not available yet. This page provides instructions; it does not collect account details, submit a request or perform deletion. The support and privacy contact will be published at Fomibee support before public app release.
The public release needs a working request route for people who cannot use the in-app controls. Publishing these instructions alone does not provide that route. The account-safety limitation and monitored request channel must both be resolved before this page is used as a store account-deletion request URL.
If you can open the app but cannot sign in, use its password-recovery option. You do not need to create a new account to recover access to an existing one.