Privacy Policy

Last Updated: September 13, 2026

This policy covers Studio 3000's apps, website, newsletter and guide. Start with the section for the product you use, then read the shared information about service providers, retention and your choices.

1. Who We Are and What This Policy Covers

Studio 3000 LLC ("Studio 3000," "we," "us," "our") operates Blades, Mirror, studio-3000.com, the This Week in the Lab newsletter, and the Ship Your iPhone App guide. This policy describes the information we process, why we use it, who helps us process it, and your choices. Product-specific sections apply only to the named product. Other Studio 3000 apps are covered when they link to this policy and their data practices are described here.

Our apps do not require a Studio 3000 account or ask for your name, email address or phone number to use their core features. App identifiers, purchase records and diagnostic information can nevertheless be personal data, even when they do not include your name. If you contact support or subscribe to the newsletter, we receive the information you choose to provide.

2. Blades: Screen Time and Notifications

Screen Time permission. Blades requests individual Screen Time authorization through Apple's Family Controls system to restrict the apps, categories and websites you select. Apple supplies protected selection tokens, which Blades stores locally and shares with its own on-device extensions to apply shields and run scheduled blocks. We do not send those tokens, selected app or website names, or your Screen Time usage history to Studio 3000, Mixpanel, RevenueCat or Sentry. Blades does not read your system-wide Screen Time usage history.

Your plans and history. Presets, routine schedules, names you enter, onboarding answers, protection state, time protected and streak history are stored on your device. Blades measures its own protection sessions; its history is not a copy of Apple's Screen Time report. A Screen Time estimate you enter during onboarding is your estimate, not a reading from iOS. Product analytics can include permission results, counts of selected apps/categories, broad ranges for estimates, goals and protected duration, motivation choices, and events such as starting or ending a block or opening a reminder. These events do not include selection tokens, chosen app/website identities, names you enter, or raw grass-touch coordinates.

Notification permission. Blades asks your permission to show notification alerts and play sounds for the reminders and nudges you choose. These are local notifications scheduled on your device and delivered by iOS. Blades does not register a remote push-notification device token or upload your reminder schedule to a push server. Notification permission does not give Blades access to notifications from other apps, and it does not subscribe you to our newsletter. Product analytics may record reminder setup and opening events as described above.

Permission controls. You can change Blades' Screen Time access in iOS Settings and its notification permission in Settings > Notifications > Blades. Removing Screen Time access prevents Blades from enforcing app restrictions. Turning off notifications stops visible reminders; automatic blocks use separate Screen Time permission. You can also edit or disable individual routines in Blades.

Other permissions and the App Clip. Blades does not request camera, microphone, contacts, photo-library, HealthKit or device-location access. Its Mixpanel configuration disables IP-derived geolocation and automatic SDK events. The Blades App Clip provides the grass ritual and an action to open the full app's App Store page; it does not request Screen Time or notification access and does not initialize our analytics, crash-reporting or purchase SDKs.

3. Mirror: Camera and Captures

Camera permission. Mirror requests camera access to display a live mirrored view and capture a photo when you ask it to. Camera frames and image processing stay on your device. We do not upload your camera feed or captured images to Studio 3000 or our analytics and diagnostic providers. You can revoke access in iOS Settings; Mirror's camera features then become unavailable.

Captured photos. Captures may exist in memory and as temporary image files in Mirror's storage on your device. If you save or share an image, iOS presents the available destinations and sends it to the destination you choose. Copies you save to Photos, Files or another service are governed by that destination's settings and policies and are not removed by uninstalling Mirror. Mirror does not browse your photo library or request microphone, contacts, HealthKit, Screen Time or notification access.

Preferences and usage. Mirror stores preferences and onboarding state locally. Its Mixpanel configuration records app lifecycle and feature-use events, such as opening the camera, using a control or viewing an offer, together with technical app/device information and pseudonymous identifiers. Mixpanel may derive approximate city, region or country from the request's IP address. Mirror does not request GPS or other device-location permission.

4. Shared App Services: Analytics, Diagnostics and Purchases

Blades and Mirror use the following services when configured in the app version you use:

Mixpanel: Product-interaction events and properties help us understand feature use, onboarding and purchase flows. Events can include app version, device model, operating system, event times, and persistent SDK/device identifiers. The app-specific differences are described above.
Sentry: Crash and error reports, stack traces, app/device information, diagnostic breadcrumbs, session information and performance measurements help us fix faults and improve reliability. Our apps do not attach camera images, Screen Time selections or user-entered plan names to these reports.
RevenueCat: Purchase and subscription records, transaction identifiers, product identifiers, purchase/renewal dates, trial and entitlement status, and app/device information help us provide paid access and restore purchases. Both apps also use it for the Apple Ads attribution described below; Mirror uses it for optional tips.

Apple Ads attribution. Blades and Mirror enable Apple's AdServices attribution through RevenueCat. The app sends an Apple attribution token to RevenueCat, which obtains available install and campaign information from Apple and associates it with the app's customer record. This helps us measure which Apple Ads campaigns lead to installs and purchases. Available information can include campaign, ad group, keyword and country or region identifiers. This integration does not send subscription lifecycle events to Apple Ads. Neither app requests App Tracking Transparency permission or collects the advertising identifier (IDFA); this configuration uses Apple's standard attribution information.

Identifiers are pseudonymous, not fully anonymous. RevenueCat generates an anonymous App User ID when an app is configured without a user-supplied account ID. That ID is not your Apple Account email and is not an identifier Apple supplies to us. Each app also uses its current RevenueCat App User ID to identify its Mixpanel activity and Sentry diagnostics. This links records within that app across sessions and services, even though we do not attach your name or email. Restore operations can associate purchase records with more than one app-generated ID.

Our providers receive network information, such as an IP address, when an app connects to their services. They process information to deliver, secure and operate those services. Disabling location enrichment in Blades does not prevent the network connection itself from carrying an IP address.

Payments. Apple processes App Store payments. We do not receive your full payment-card details or billing credentials. RevenueCat receives purchase information needed to manage access; it does not receive only an identifier. Subscriptions and purchase history can remain with Apple and RevenueCat after you uninstall an app. See Apple's privacy policy.

Neither app displays third-party advertising, collects IDFA, or sells app data to data brokers. We do not use your camera images or Screen Time selections for advertising. Apple Ads measurement is described above. Downloading an app does not sign you up for marketing emails.

5. Website and Support

Cloudflare hosts and protects studio-3000.com and may process request information such as your IP address, user agent and security signals. We do not use advertising cookies on the website.

Project inquiries. The services form sends the name, email address and project details you enter to a Cloudflare Worker that Studio 3000 operates. The Worker verifies a Cloudflare Turnstile check, then emails the inquiry to Studio 3000 through Cloudflare Email Routing. The Worker does not store a separate copy of your inquiry. Turnstile may process your IP address and browser signals to distinguish people from bots.

Support messages. If you email us, we receive your email address, message and any attachments you choose to send. We use them to respond and provide support. Please avoid sending camera images, Screen Time selections or other sensitive information unless it is necessary for your request.

The website includes Beehiiv forms and attribution tools for newsletter signups and guide delivery. Turnstile and embedded Beehiiv services may use cookies or local storage for security, form functionality and referral attribution. The newsletter section below explains those practices.

This Week in the Lab is delivered through Beehiiv. When you subscribe, Beehiiv collects your email address, subscription date and source, campaign/referral information, and technical request details such as IP address and browser. Emails may include engagement tracking that reports opens and link clicks to us in aggregate and per subscriber.

We use this information to send the newsletter and occasional updates about Studio 3000 products and services, administer subscriptions, and understand what readers find useful. We do not sell subscriber information or share it with advertisers. Unsubscribing stops future marketing sends; a message already being delivered may still arrive. Unsubscribing and deleting your subscriber record are separate actions.

Requesting the free Ship Your iPhone App guide through its signup form subscribes you to the newsletter and provides access to the download. The form explains this before you submit it. You can unsubscribe at any time and keep the guide. App purchases do not enroll you in the newsletter.

We use service providers for the purposes described in this policy. Providers processing data for us must protect it consistently with this policy and applicable law. Their own notices explain additional details of how their services operate: Mixpanel, Sentry, RevenueCat, Cloudflare and Beehiiv.

Information may be processed in the United States or other countries where we and our providers operate, subject to applicable data-protection requirements. We may also disclose information when legally required, to protect people's rights or safety, or as part of a business transfer subject to applicable law and privacy protections.

8. Data Retention

We retain information for as long as needed for the purposes described here, including providing access, understanding app use, resolving faults, responding to support, and meeting legal obligations. Retention depends on the type of data, our service-provider settings, and whether it is still needed.

Local app data: Preferences, Blades plans/history and Mirror's temporary captures remain in device storage until removed by the app, iOS or an app deletion. Offloading an app retains its data. Device backups, shared app storage, keychain identifiers and copies you explicitly save or share may persist separately, so uninstalling is not a complete deletion request.
Analytics and diagnostics: Retained according to our configured provider retention and deletion processes for product analysis and fault investigation. Deleting an app does not automatically delete records already sent to these services.
Purchases: Apple and RevenueCat may retain transaction and entitlement records to restore access, handle subscription changes, prevent fraud and meet legal obligations.
Support and inquiries: Retained in our email systems as needed to respond, manage the relationship and meet recordkeeping obligations.
Newsletter: Subscriber and engagement records remain in Beehiiv until removed under our account settings or in response to a deletion request. A limited unsubscribe/suppression record may be retained to respect your choice not to receive further email.

9. Your Rights and Choices

Device permissions: Use iOS Settings to change camera, Screen Time or notification permissions for the relevant app. Revoking a permission affects the associated feature; it does not delete information already processed by our providers.
Analytics: Apple's Settings > Privacy & Security > Analytics & Improvements controls Apple analytics, not our Mixpanel or Sentry collection. The current versions of Blades and Mirror do not provide a separate in-app switch for these services. Contact us about your applicable objection, consent-withdrawal or deletion rights; we will explain the available steps and any limits.
Subscriptions: Manage or cancel app subscriptions in your Apple Account subscription settings. Uninstalling an app, revoking a device permission or making a data request does not cancel an Apple subscription.
Newsletter: Use the unsubscribe link in each newsletter email to stop future marketing messages. Email us separately if you want your subscriber record deleted.
Data requests: Depending on where you live, you may have rights to access, correct, delete or receive a copy of your personal data, object to or restrict processing, withdraw consent where processing relies on it, or complain to a data-protection authority. Email support@studio-3000.com with the product and request. We may need information to verify the request and locate the relevant app-generated ID or transaction. If we cannot identify your records, we will explain that limitation. Do not send your Apple Account password or full payment-card details.

10. Children's Privacy

Our apps and newsletter are not directed at children under 13. We do not knowingly collect personal data from children under 13. If you believe a child has provided us with personal data, contact us so we can investigate and delete it as appropriate.

11. Changes to This Policy

We update this policy when our products or data practices change and show the revision date above. We will provide additional notice or request consent where required by law. Publishing a revised policy does not by itself authorize a new use of your data that requires your consent.

12. Contact Us

For privacy questions or requests, contact Studio 3000 LLC at support@studio-3000.com.