RUPTUREOPS iOS
Privacy policy
Effective August 2, 2026The short version
RuptureOps iOS 1.0 works without an account. It has no advertising, tracking SDK, or cross-app tracking. The app sends catalog searches and production-calculation requests to ruptureops.com so it can return current results.
Data the iOS app and its infrastructure process
| Data | Why it is processed |
|---|---|
| Search history | Search terms are sent to return matching StarRupture catalog entries. |
| Product interaction | Requested catalog and calculator routes identify which API feature should respond. |
| Coarse location | Infrastructure providers may derive an approximate region from an IP address for request delivery and abuse prevention. |
| Diagnostic data | IP address, user agent, timestamp, route, response status, byte count, edge region, timing, and request identifiers help operate and secure the service. |
These data can be associated with a device or network address while retained in infrastructure logs. RuptureOps uses them only for app functionality, reliability, and security—not advertising, marketing, profiling, or tracking across other companies’ apps or websites.
What is not collected by iOS 1.0
The released iOS app has no Profile or account feature and does not collect a name, email address, Discord identity, contacts, precise location, photos, save files, payment information, or advertising identifier. Production-calculator request bodies are used to return a result and are not stored in the RuptureOps application database or copied into access logs.
On-device preferences
The app stores small production-calculator preferences, such as the selected machine scope, in Apple UserDefaults on the device. Removing the app removes those preferences. RuptureOps iOS 1.0 does not request notification permission.
Service providers and retention
Cloudflare delivers and protects ruptureops.com traffic. Railway hosts the API and database. Railway platform HTTP logs for the current service plan are retained for up to 30 days. Cloudflare may temporarily retain network and security metadata under its service-specific retention schedules. RuptureOps does not create a separate advertising or user-profile database from these logs.
Your choices
You can stop network processing by not using the app, and remove local preferences by deleting the app. RuptureOps iOS 1.0 does not create or use an account. If you have a separate RuptureOps website account or used an earlier development build, contact [email protected] about its records. For an operational-log request, we may need a request identifier and approximate time to locate a record; logs otherwise expire automatically.
Changes and contact
This page will be updated before a released app version changes its data practices. Questions can be sent to [email protected] or through the RuptureOps support page.
RuptureOps is an independent, unofficial StarRupture companion and is not affiliated with Creepy Jar.