iPhone & iPad
Privacy policy
Effective and last updated:
This policy covers the Curse of Strahd iOS and iPadOS game and its promotional website, curseofstrahd.app. The game is an unofficial fan project developed by Ashwin Mahesh (referred to as “I” below).
1. What stays on your device
The game stores campaign progress, characters and their names, save notes, save thumbnails, recovery saves, and preferences such as audio and controls in its local app storage. It also keeps local logs and error reports to help diagnose problems. An error report may include a copy of the latest save.
The game does not automatically upload these files to me or to a game server. It does not require your real name, email address, or an account to play, and does not access your contacts, precise location, camera, or microphone. It does not sell personal data or track you across other apps or websites.
Your device or iCloud backup may include app data according to your Apple settings. The game does not operate its own cloud-save service, and I cannot access your device or iCloud backups.
2. Files you choose to share
Save import uses Apple's Files picker to copy the file you select into the game. Save export and “Share diagnostic report” open Apple's share sheet. You choose the destination, app, or recipient; opening the sheet does not send the file to me automatically.
A shared save contains campaign data, including character names and any save notes you entered. A shared diagnostic report contains recent errors and log messages, which may include details of your game session or file paths. Review files before sharing and avoid putting personal information in character names, save notes, or reports.
If you send me a report or a support request, I receive the content and attachments you provide, along with the contact or profile information supplied by the service you use. I use that information to respond, investigate problems, and improve the game. I do not use it for advertising or sell it.
Copies saved to iCloud Drive, another file provider, or a messaging service are handled by the service you choose. Their privacy and retention policies apply to those copies.
3. Apple services and TestFlight
Apple handles App Store distribution and may provide developers with app analytics or crash information under Apple's privacy controls. You can review available sharing choices in your device's Settings under Privacy & Security → Analytics & Improvements. See Apple's privacy policy.
If you install a beta through TestFlight, Apple automatically collects crash logs and usage information and shares them with the developer. Feedback you submit may include screenshots, device and app details, and your comments. Your name and email may be visible to the developer depending on how you joined the test. This beta collection is separate from the game's local storage and cannot be switched off within the game.
I use TestFlight information to investigate issues and improve the game. Apple's TestFlight privacy notice explains the data, retention, and choices that apply. You can stop beta participation using TestFlight's Stop Testing option.
4. Visiting the website
The promotional site does not include advertising or analytics scripts and does not set its own tracking cookies. Visiting it still involves ordinary web requests: the hosting providers receive information such as your IP address, requested page or file, and browser details to deliver and secure the site.
The site uses GitHub Pages, and desktop downloads are served through Cloudflare. Most pages load typefaces from Google Fonts, which receives font requests from your browser. This privacy page uses system fonts and does not request Google Fonts.
For their handling of those requests, see the GitHub privacy statement, Cloudflare privacy policy, and Google privacy policy. Following an external link takes you to a service with its own privacy practices.
5. Retention, deletion, and your choices
- Local saves: use Delete in the game's saves screen to remove an individual save and its thumbnail. Autosaves, recovery files, backups, and diagnostic copies may remain separately.
- All local app data: use Delete App in iOS or iPadOS to remove the app and its local data. Offloading the app keeps its data. Export any saves you want to keep first.
- Exported files and backups: delete them separately in Files, your chosen service, or your device's backup settings. Removing the app does not remove copies already shared with others.
- Local diagnostics: the game retains up to 20 error-report sessions, removing older sessions as new ones are recorded. Local logs and temporary transfer copies may remain until overwritten or the app's data is deleted.
- Information sent to me: support correspondence and diagnostic files are retained only as needed to address the request, investigate related issues, or meet legal obligations. You can request access, correction, or deletion using the contact route below. Public GitHub posts and copies held by Apple or other services also follow those services' retention policies.
You can decline optional sharing and continue playing. Where processing is based on your consent, you can withdraw it by contacting me; this does not undo processing already carried out. Depending on where you live, you may also have rights to object to or restrict processing and to complain to your local data-protection authority.
6. Children's privacy
This horror role-playing game is not directed at children under 13. I do not knowingly collect personal information from children under 13. If you believe a child has sent personal information through a support request, please contact me so I can address it.
7. Changes to this policy
Updates will be posted on this page with a revised date. If the game's data practices change, this policy will be updated to describe them.
8. Questions or privacy requests
Contact Ashwin Mahesh through the game's GitHub issue tracker. GitHub issues are public: please do not post personal information, private saves, or diagnostic attachments there. You can use an issue to ask for a private way to follow up on a privacy request.
If you are a TestFlight tester, you can also use Send Beta Feedback in TestFlight to contact the developer without posting to the public issue tracker.