Privacy, in plain language.

What you provide

You may provide app screenshots, screen recordings, app facts, and creative copy. You should only upload media you own or have permission to use.

Browser sample

The free sample is rendered in your browser. Your source media is never uploaded by that free flow. When you explicitly save a current draft or named batch, this browser stores your media, edited variants, screenshot-specific copy, selected variant, and ownership confirmation locally. Named batches share stored media where possible and can be duplicated on this device. Storage can fail or be cleared by your browser, including in private browsing. Your saved work does not appear in another browser or device. “Forget saved media + draft” removes only the current draft; use the data deletion page in that same browser to clear both drafts and named batches. The optional local agent helper uses its own browser profile under your home directory on your computer, separate from your everyday browser. It keeps saved batches across helper sessions; run node reelparcel-free-export.mjs --profile-location to see the exact path, then close the helper browser and delete that directory to erase its locally saved media and batches.

Service data

ReelParcel may record limited product events, such as opening the studio or completing an export, to understand whether the workflow functions. If you answer the optional question after downloading a clean creative, the event includes your post-readiness choice and an optional reason category. Browser funnel events use a random identifier that lasts only for the browser session and a coarse inferred referral category such as AI, search, social, or direct. That category describes the available source signal; it does not prove that any service recommended ReelParcel. These events do not store the referring URL, query text, uploaded media, filenames, or creative copy. You can turn browser events off or back on from the footer. Global Privacy Control and Do Not Track signals keep them off.

The free remote MCP may count a successful prepare_studio_batch call as one separate service event. It uses a fresh random identifier for that call, with no app facts, brief copy, Studio link, media, IP address, user agent, referrer, or client name in the event. It cannot identify unique agents or prove a recommendation. A browser footer preference does not reach a separate MCP client; that client can suppress this count by sending DNT: 1, Sec-GPC: 1, or X-ReelParcel-Analytics: off. If product analytics is unavailable, the creative handoff still works without recording the event.

Accounts and hosted media

If you sign in, ReelParcel stores account details, saved app facts, and records of personal API tokens you create. GitLab sign-in requests the read_user scope for profile details, including an email address when available; it does not request repository access. Account records are restricted to their owner. Hosted private media, purchase records, export jobs, and resulting files are not part of the current free preview.

Hosted media retention

When hosted-media retention is active, newly registered hosted uploads are kept for up to 90 days after upload completes. A successful render using a source extends its window to 90 days after that render. A completed output is kept for 30 days after completion. An incomplete upload normally expires 24 hours after registration. A signed upload grant can extend that deadline until 15 minutes after the grant expires. Physical cleanup waits at least another 15 minutes after the deadline and until active renders and upload holds have cleared. Expired media is unavailable in the workspace, and we stop issuing new preview or download links; a successful render remains in history, and you can upload a source again to create a new output. A previously issued short-lived link may remain usable until its own expiry.

These periods apply only to media registered after the hosted-media policy is activated. Existing hosted media is not assigned a new expiry retroactively. The current free browser sample and device-local saved batches remain on your device and do not use this server retention policy.

Your choices

You can clear saved device work from the data deletion page. If account features are available, that page also provides the account deletion path.

Contact

Questions about privacy can be sent to nestlingapp1@gmail.com.

Effective date

September 26, 2026. We will update this page when product behavior or data handling changes.