Your HOME library
HOME saves title, lyrics, style and exclusions together with your notes, tags, source information and version history. A device copy is stored in this browser’s IndexedDB. Signed-in libraries also sync to Supabase through account ownership checks. The example workspace has a separate device-only library and does not upload its examples to your member account.
“Saved on this device” means the local save completed. “Synced” means the server acknowledged the current work and the library finished its sync check. A cloud interruption does not prevent editing an already open workspace. Browser data can be cleared or evicted; export your library for a separate copy of your work.
Device copies remain in this browser after sign-out, separated by account. Returning to an account reopens its library. View preferences, searches and scroll positions are also kept on the device so you can resume your work.
History, archives and exports
Keeping or copying a version snapshots all four fields. Restoring preserves the later work in history. Archiving removes an idea from the main library while keeping it available to restore; it does not delete the content or its history.
A library export includes your complete prompts, source text, notes, tags and kept versions. Copying puts the selected field or package on your device’s clipboard. HOME does not send that clipboard text to Suno or an assistant. When you paste it into another service or share an export, that destination receives the material you selected.
Research and AI
Your library does not contribute to research by default. Optional contributions let you preview selected fields from a kept version. Patterns include character counts, recognized section-tag order and instruction categories from a fixed vocabulary. Unknown free-text tags are excluded. Selected-text contributions retain the exact wording of only the fields you choose. Personal notes, original pasted source, model notes and take links are not included.
A contribution is linked privately to your account, source prompt, immutable version and permission record. It also records the source type, extraction version and review state. It is not anonymous. Contributions enter a restricted research queue and require both source-eligibility and research review before shared retrieval. This permission does not authorize public display or model training, and HOME does not send contributions to an AI provider.
You can separately include future kept versions of an individual prompt, using the same fields and mode. Other prompts, duplicates and new imports do not inherit that permission. Earlier versions are not automatically backfilled. Replacing a future-version permission withdraws the contributions made under its previous scope.
Your contributions provides withdrawal for one version, one prompt, or everything you have contributed. Withdrawing one version leaves a separate future-version permission in place; withdrawing a prompt or everything stops the corresponding future contributions too. Withdrawal clears contributed payloads from the active database and removes them from the restricted retrieval view. Permission and withdrawal records remain, without the contributed payload. Your own library and its history remain intact. Marking a prompt private has the same effect for that prompt after the change syncs; an offline device cannot immediately withdraw remote copies.
This build does not send prompt fields or search text to an analytics provider. Optional research contributions are separate from using your private library.
Public tools and workshop drafts
The public prompt builder assembles descriptions in your browser. It does not send your song topic to an AI service or submit anything to Suno. The workshop keeps up to five recent experiments in this browser’s local storage, including source release data, output links and unfinished listening notes. These workshop drafts are separate from HOME and are not synced to your account. The builder uses temporary tab storage to transfer an experiment to the workshop.
The written mini-course stores completed lesson numbers in this browser. Clearing the site’s browser data removes local workshop drafts, course progress, view preferences and device copies of HOME documents. Work already acknowledged by HOME’s cloud sync remains in your account.
Sign-in, hosting and external links
Member authentication uses Supabase and Google sign-in. Hosting and authentication providers may process routine connection and service logs. Ordinary application logging does not include your prompt fields or search text. Opening Suno or another external site brings that service’s policies into effect. These pages do not include advertising trackers or a newsletter collection form.
Support and requests about your data
For help, an account-data export, or a request to delete your HOME data, email contact@maxfilmatic.com from the address you use to sign in. We verify requests before changing account data. Archiving a prompt keeps its contents and is not deletion.
HOME data removal is handled manually. An approved removal can cover your cloud prompts, their revisions, and associated contribution permissions, payloads and processing records. Removing HOME data does not automatically delete the shared sign-in identity or records used by other SunoPrompting tools; we confirm the scope of your request.
Device copies and backups
Cloud removal does not remotely erase browser copies, downloaded exports or clipboard contents. Close HOME on your devices and clear the relevant site data when removing device copies. Clearing site data also removes that site’s local preferences and course or workshop progress. Reimporting an export or syncing new work can create new cloud copies.
Our current Supabase plan provides daily database backups with a seven-day retention window. These backups can contain earlier copies after removal from the active database, until the backups expire. Recent changes may not yet be included in a daily backup. You can export your complete HOME library for a separate copy you control.