Overview
ReCreate is an account-free app. Analytics are optional: you choose whether to enable them in the app, and you can withdraw your consent at any time by turning analytics off.
If you opt in, ReCreate sends limited analytics and crash diagnostics to PostHog EU Cloud. We use this information only to understand how ReCreate is used, improve features and reliability, and diagnose crashes.
Pseudonymous installation ID
After consent, ReCreate uses a random persistent installation ID. This is a pseudonymous ID for this installation, not an account identifier. It lets us correlate analytics events and crash reports from the same installation so that we can investigate reliability issues.
We do not create accounts, and this analytics ID is not linked to advertising, vendor-wide, or cross-app identity. We do not use this ID to identify you outside ReCreate. Rewarded ads work differently: Google receives an advertising identifier for the ads it serves, as described in Advertising below.
What we collect and do not collect
With your consent, analytics may include app interactions, feature usage, app version, operating-system version, and device characteristics. On Android they also include how the install was acquired, recorded as one of a few fixed categories — an organic Play listing, a Google ad, our own website, a promotion inside another of our apps, a tagged link from elsewhere, a plain install, or unavailable. This comes from Google Play’s install referrer. We never store the campaign text itself, the click identifier, or the referring address. Crash diagnostics may include exception and error details, app state relevant to an error, and those same technical details. These categories support analytics and reliability and crash diagnostics.
Analytics also include an approximate location derived from your IP address, described under IP and geography. We do not collect photos, camera frames, user-content filenames, photo-library or generated-result paths, user text, or any location from your device: ReCreate asks for a location permission only after you switch photo geotagging on yourself, and the coordinate it then reads is written into that photograph on your device only — it is never sent to us, never stored as a place history, and never included in analytics. Native crash diagnostics may include executable or module names or paths and debug-image paths needed for crash diagnosis. ReCreate does not use analytics for advertising.
Purchases and subscriptions
ReCreate uses RevenueCat to process in-app purchases and determine subscription status. RevenueCat receives an anonymous app user identifier and purchase and entitlement information. ReCreate does not send photos, email addresses, advertising identifiers, or PostHog identifiers to RevenueCat. Purchases are processed by Apple or Google and do not transfer between platforms because ReCreate has no account system.
For questions or deletion requests about RevenueCat purchase and entitlement information, contact ilia.savinkov.cyprus@gmail.com. We will route the request to RevenueCat and, when the store controls the record, to Apple or Google.
For purchases made through Apple, see the Terms of Use (Apple Standard End User License Agreement).
Advertising
Free users can watch a rewarded ad from Google AdMob to earn one extra photo per ad, up to five extra photos per day. Watching an ad restores only the daily photo allowance.
To serve these ads, Google may receive an advertising identifier and coarse location derived from your IP address. Google uses that information to select and measure ads, including ads shown to you in other apps. See how Google uses information from sites or apps that use its services.
In the European Economic Area, the United Kingdom, and Switzerland, ReCreate shows a Google consent form before any personalised ad. On iOS you can reopen that choice later from Ad privacy options in ReCreate settings.
On iOS, the system tracking prompt controls the advertising identifier. Declining it does not remove ads and does not change how many free photos you get.
The advertising consent choice and the analytics choice described above are separate. Neither one answers or overrides the other.
IP and geography
Our ReCreate PostHog project discards stored client IP data: your IP address is never saved with your events.
Before it is discarded, the IP address is used once to derive an approximate location, and that derived location is stored with consented analytics events and with the pseudonymous installation record. It includes country, region, city, postal code, time zone, and approximate coordinates. This location comes from the IP address only, is approximate, and is often no more precise than the city or region of your network provider. We use it to understand where ReCreate is used. It cannot be narrowed to the country alone, and it is collected only while you have analytics enabled.
Retention and deletion
We retain consented analytics and crash data only under the active ReCreate PostHog project retention setting and while it is needed for the purposes above. There is no fixed legal retention period. You may request deletion of data associated with your Analytics Installation ID, and we will process the request through PostHog and confirm completion by email.
Turning analytics off stops application telemetry calls immediately and denied crashes are prevented from transmission. The native handler may still write a denied crash report locally in the already-running process; it is dropped before transmission. The native handler is not installed on a later launch while consent remains off. Withdrawal does not retroactively erase data that was already consented to and is queued, in-flight, or retained; use the deletion-request process below for that data.
Request deletion
- Turn analytics off in ReCreate.
- Copy the Analytics Installation ID shown in the app.
- Close ReCreate.
- Email the ID to ilia.savinkov.cyprus@gmail.com and request deletion.
- Keep analytics off until we confirm completion.
- Before any later opt-in, delete and reinstall ReCreate. This prevents an old consented SDK disk queue from uploading again under the deleted ID.
Contact
For privacy questions or deletion requests, contact ilia.savinkov.cyprus@gmail.com.