We only ask for access we actually need. This policy explains every device permission and system access that Raketmo applications may request, exactly why we need it, and how you can revoke it at any time. We do not request access to permissions not described in this policy.

§01 Overview

Raketmo apps are designed with a privacy-first approach to permissions. We request access to device features and data only when necessary to deliver a specific feature you are actively using. We do not request permissions speculatively or in bulk.

Specific permissions required by any given Raketmo app are disclosed in that app's listing on the Apple App Store, Google Play Store, or other applicable platform. This policy describes the full set of permissions that may be requested across any Raketmo product.

All permissions are requested at the time they are needed, not at install. You will always be given a clear explanation of why a permission is needed before the system prompt is shown. Declining a non-essential permission does not affect your ability to use the core functionality of our apps.

§02 Permissions Overview

Location
Precise or approximate location to provide location-aware features. Requested only when using location-dependent functionality.
Optional
Camera
Access to device camera for capturing photos or video within supported app features (e.g., uploading profile photos or content).
Optional
Photos / Media Library
Access to your photo library to allow you to select and upload images or files. We request limited photo library access (selected photos only) where the platform supports it.
Optional
Files & Storage
Read/write access to device storage or external files for saving, opening, or exporting content created or managed within our apps.
Optional
Push Notifications
Permission to send push notifications for alerts, updates, and communications. You control notification types and frequency in your device settings.
Optional
Network / Internet
Required to connect to Raketmo servers to deliver app features, sync data, and serve content. This permission is required for all online functionality.
Required
Device State
Read basic device state (network connectivity, battery status) to optimize performance and adapt to device conditions. No unique hardware identifiers are collected via this permission.
Required
Advertising Tracking (ATT)
On iOS, App Tracking Transparency permission to access your IDFA for personalized advertising. Declining does not affect core app functionality — non-personalized ads are served instead.
Optional

§03 Location Access

Raketmo apps may request access to your location to provide location-aware features. We follow a tiered approach to location access:

  • Approximate location (coarse): City or region-level location used for contextual features and regional content. This is the least precise location type and our default where fine precision is not required.
  • Precise location (fine): GPS-level location requested only when a specific feature requires it and only while the app is in active use. We do not request "always on" background location access unless a specific active feature requires it and you are clearly informed.
  • Background location: Requested only for features that explicitly require it (e.g., location-based reminders). Background location access is requested separately and can be revoked independently.

Location data is used only for the feature that triggered the permission request. We do not share precise location data with advertising partners without explicit consent. See our Privacy Policy for full details.

§04 Camera & Photos Access

Camera access is requested only when you use a feature that requires capturing media — such as uploading a profile photo, scanning a document, or creating in-app content. The camera is never activated in the background or without your explicit action.

For photo library access, we request the minimum level of access necessary. On iOS 14+, we use the limited photo library picker (you select which photos to share with us) unless full library access is required for a specific feature, in which case we explain why and request it explicitly. On Android, we request media read permissions only for the specific media type needed (images, video, etc.).

We do not use camera or photo access to train machine learning models on your personal photos without separate explicit consent.

§05 Storage & Files

Storage access may be requested to allow you to: save content you create within our apps to your device, open files from your device for use within our apps, or export data in a format you can use outside our apps.

We do not scan, index, or monitor files beyond those you explicitly select or save through our app features. We do not access files outside of designated app folders or files you have actively shared with our app.

§06 Notifications

We may request permission to send push notifications. Notifications may include: app alerts, account security notices, feature updates, and promotional communications (where you have opted in separately to marketing). You can manage notification preferences at any time in your device settings (iOS: Settings → Notifications → [App Name]; Android: Settings → Apps → [App Name] → Notifications).

We do not send push notifications for advertising purposes without your separate opt-in to marketing communications. Security and account notices are always sent when needed regardless of marketing opt-in status.

§07 Device Identifiers

Our apps may collect the following device identifiers for the purposes indicated:

  • App instance ID / Install ID: A randomly generated ID created at app install, used to distinguish app sessions for analytics. Resets when the app is reinstalled.
  • Advertising ID (IDFA/AAID): See our Advertising ID Policy for full details.
  • OS-generated device ID: Used for security and fraud prevention only, not for advertising. Not shared with advertising partners.

We do not use hardware serial numbers, MAC addresses, or other permanent hardware identifiers for tracking or advertising purposes.

§08 Network Access

Network access is required for all online features of our apps. Our apps connect to Rakett LLC servers and, where necessary, authorized third-party service providers. All network communications use encrypted HTTPS/TLS connections. We do not transmit personal data over unencrypted connections.

§09 App Tracking Transparency (ATT — iOS)

On iOS 14.5 and later, we present Apple's App Tracking Transparency prompt before enabling any cross-app tracking or accessing your IDFA. We explain clearly why we are requesting tracking permission before the system prompt appears. Your choice is respected immediately. If you decline, all advertising-related tracking is disabled and you receive non-personalized ads only.

You may change your tracking preference at any time: Settings → Privacy & Security → Tracking → [App Name].

§10 How to Revoke Access

You can revoke any granted permission at any time using your device's system settings:

  • iOS: Settings → Privacy & Security → [Permission Type] → toggle off the Raketmo app.
  • Android: Settings → Apps → [App Name] → Permissions → toggle off the permission.

Revoking a permission may disable specific features that depend on it, but it will not affect the core functionality of the app or your account. We never penalize you for revoking optional permissions.

§11 Minimum Required Access

The minimum permissions any Raketmo app will request are those required for the app to function at all (typically network access and basic device state). All other permissions are optional and tied to features you actively choose to use. We commit to the principle of least privilege — we ask for nothing more than we need to deliver the feature in front of you.

§12 Contact

If you have questions about a permission request, believe an app is requesting access it should not need, or want to report a permission concern, contact us:

RAKETT LLC, 20422 Schoenborn St, Winnetka, CA 91306, United States.