Dreadcam has no accounts and no sign-up, so there is no account to close. This page says what Dreadcam stores, how to ask us to delete it, and what is deleted. It follows the Privacy Policy (sections 2 to 8).
To request deletion: e-mail support@neron.app with the subject "Dreadcam data deletion" and include the share link of your picture or its job ID, if you have it. Result files are also deleted automatically 30 days after they are made.
What Dreadcam stores
On our server (Google Firebase, region europe-west1):
Result files for each picture made: a preview, a still image and a short GIF. They are made from your photo, so they show what is in it. They are kept in Google Cloud Storage behind time-limited private links.
A job record for each picture: type of figure, time, cost, technical checks, and the number of faces your phone found (a count only).
Counts tied to a hashed identifier. There are no accounts. The App sends a device identifier, and a purchase identifier is made from it; our server stores both only as salted, one-way hashes, with counts such as free pictures used and paid single pictures used.
Reports you send from inside the App: the picture's job ID, type of figure, random seed, your reason, an optional note, the hashed device identifier and the time.
Daily totals with nothing about you: how many times shared links were opened per day, and our daily spend.
We do not store the photo you choose, and we do not store or log the AI model's picture. We do not use your photos to train any model.
On your phone: a device identifier, a flag that onboarding was seen, and small counters for the review prompt. If you chose to save a result to your photo library, that copy is a file on your phone and is not stored by us.
What gets deleted when you ask
The result files for the pictures you name (the share link or job ID tells us which).
The job records for those pictures.
Any reports you sent about them.
Result files are deleted automatically 30 days after creation. The storage service has soft-delete protection on, so a deleted file may stay recoverable by us for a limited time before it is permanently removed. The job record and any report are not deleted automatically; we delete them on request.
What we may not be able to find or delete
Because the stored identifier is hashed and the App does not show it to you, we usually cannot find your results by device. Without a share link or job ID, we may not be able to match a request to your pictures, and if we cannot, we will tell you so.
Hashed counters (free pictures used, purchase counts) hold only numbers, no photo. They exist to enforce one free picture per device and to count paid single pictures.
Daily totals (shared-link opens, spend) are not linked to you.
Uninstalling the App deletes what is on your phone but does not delete result files on our server.
Data held by service providers
fal.ai receives the photo for the safety check and for finding where people are, and, in some pictures, a second copy with people and faces painted over and the model's answer. It keeps uploaded files under its own terms: fal.ai/privacy.
RevenueCat holds the hashed purchase identifier and your purchase information: revenuecat.com/privacy.
Google Firebase Analytics and Crashlytics hold usage events and crash traces under a random app-instance identifier: firebase.google.com/support/privacy.
Apple App Store and Google Play process payments under their own policies; we never see your card. Deleting the App does not cancel a subscription; cancel it in your App Store or Google Play settings.
Tell us in your e-mail if your request also concerns these providers and we will reply with what we can and cannot do. Depending on where you live (EEA/UK GDPR, California CCPA, Turkish KVKK No. 6698 or other laws) you may also ask about, correct or delete information we hold, and you may complain to your local data protection authority.