Privacy Policy

Overview

Stacked is a shoot planner and gear load-out app published by Sleeping Giant Marketing Services Private Limited ("we," "us"). You keep a kit of your own gear, plan shoots, and Stacked proposes what to pack and shows the sun and weather for the day. This policy explains what the app reads on your phone, what it stores, and the short list of things that leave your phone.

In the current version, Stacked has no Stacked account system and we do not operate a server that holds your gear, shoots, photos or reference images. That data stays on your device. A few features, listed under "What leaves your device," contact other services when you use them. If we add accounts, cloud backup or sync, or anything else that changes what we collect, we will update this policy before or when that feature ships.

What Stacked accesses on your device

Calendar. With your permission, Stacked reads events from the calendar accounts already configured on your phone (for example Google, Outlook, iCloud or a local calendar) and shows them next to your shoots, so you can plan around them. When you ask it to, it can also edit, duplicate, share or delete one of those events. If you turn on syncing in Settings, it writes each shoot to the calendar you choose, keeps that event and the shoot in step in both directions, updates the original event when you turn a calendar event into a shoot, and deletes the mirrored event when you delete the shoot (for a shoot made from one of your calendar events, that is your original event). Those are the only reasons the permission is requested. Calendar events are read and written through your phone's calendar system. See "What leaves your device" for what can happen if the calendar you choose belongs to a cloud account.

Contacts (optional). If you type a name while editing a calendar event, Stacked can match it against your contacts to suggest a phone number or email. The match happens on your device, contacts are only read after you grant the permission, and Stacked sends them nowhere itself. If you tap a suggestion, it is added to that event's notes and saved with the event, so if the event is on a cloud calendar such as Google or iCloud, your phone syncs that note to it. You can decline the permission and use the rest of the app normally.

Camera. Used to scan barcodes on your gear, to photograph gear and reference images, and for the camera mode in Plan the light. Pictures you take are saved in the app's own storage on your phone. Stacked does not record audio. On Android, the app's store listing may also show a biometric (fingerprint) permission, because a library the app uses declares it by default. Stacked does no biometric authentication.

Photo library. If you choose to add pictures from your photo library (for example to a reference deck), Stacked reads the pictures you select, and only those.

Location. Stacked turns the place name you type for a shoot or a scouted location into map coordinates, so it can work out the sun and weather. For a shoot it does this once: when you add the shoot, and again only if its place changes (for example when the location of a synced calendar event changes) or an earlier lookup didn't work. The coordinates are saved with the shoot on your phone. A scouted place is looked up each time you scout it, and is not saved. On Android the lookup needs location permission. Stacked asks for it only when you act: when you add a shoot or scout a place, or when you tap a shoot's Light row after its place couldn't be looked up. Just opening a shoot never asks. If you decline, or you are offline, the shoot is still saved, says that its light is unavailable, and you can try again later. The app does not track your position and does not read your phone's current location.

Motion sensors. The compass in Plan the light's camera mode uses your phone's magnetometer and motion sensors while that screen is open. When you open camera mode, your phone asks for motion access until you have allowed it: on iPhone this is the “Motion & Fitness” prompt, and on Android 10 and later it is “Physical activity”, because the motion-sensor library the app uses asks for that permission. Stacked does not count steps or track your activity, and if you decline, the compass does not work. The readings are used live and are not stored or sent anywhere.

Notifications. Pack and wrap reminders are scheduled on your phone by your operating system. There is no push-notification server.

What's stored, and where

Your gear, cases, shoots (including each shoot's place name and the map coordinates Stacked looked up for it), load-outs, shot plans, reference images, gear photos and preferences are stored in the app's own storage on your phone. Preferences include your theme, sound and haptics settings, time format, reminder settings, your crash-report choice, which calendar shoots sync to, which calendars you show or hide and how they are emphasized, whether you have finished onboarding, recent searches, and the gear-catalog additions you have accepted or that catalog updates have downloaded. If you enter an Anthropic API key for the optional AI gear lookup, it is kept in your phone's secure keystore. None of this is sent to us.

If your iPhone is backed up to iCloud or a computer, that backup includes this storage. That backup is controlled by your device and your device account, not by us. Android's own app backup does not currently include Stacked's gear, shoots, photos or settings. Uninstalling Stacked removes its local data. It does not remove your calendar events, which belong to your phone's calendar system. On iPhone, an API key can outlive an uninstall, so remove your key in Settings first to be sure it is gone.

What leaves your device

These are all the ways data leaves your phone because of something Stacked does. Every service the app contacts directly also sees your phone's IP address, as any web request does.

• Crash reports. When the app crashes or hits an error, it can send a crash report, unless you turn that off. See "Crash reports" below.
• Barcode lookups. When you scan a barcode in Kit setup, Stacked sends the barcode number to UPCitemdb to find the product. Scanning a barcode onto an item you already have stays on your phone.
• AI gear lookups. Only when you ask for one, and only if you have entered your own Anthropic API key, Stacked sends the item to Anthropic's API so it can search the web for the product and its weight. The request carries the item name as you typed or pasted it. For a scanned barcode it carries the product title the barcode database returned, or the barcode number itself if no title was found, plus any hint the database gave (such as brand, model, category and listed weight). Your use of your own key is also subject to Anthropic's terms and privacy policy. Tapping the source of an AI result opens it in your phone's browser.
• Weather. For a shoot or a scouted location that has a place set, Stacked sends that place's coordinates and the date to Open-Meteo to fetch the forecast.
• Catalog updates. In the background, Stacked downloads a public file of gear-catalog additions hosted on GitHub Gist. The request carries no information about you or your kit.
• Reference-image links. If you paste an image link into a reference deck, Stacked downloads the picture from whatever website the link points to. The request carries nothing about you or your shoots beyond the link itself and the standard details any download sends.
• Place names to your phone's geocoder. A shoot's place name (typed by you, or taken from a calendar event you turn into a shoot or keep in sync) and a scouted location's name are handed to your phone's built-in geocoding service (Apple's or Google's), which may send them to its own servers. For a shoot this happens once, and again only if its place changes or an earlier lookup didn't work. A scouted location's name is sent each time you scout it. The app has no control over what the service does with it.
• Barcode scanning on Android. On Android, the camera's barcode reader is Google's ML Kit. It reads the barcode on your phone. Under Google's ML Kit terms it may send Google metrics about how the scanner performs and is used, together with device and app details. It does not send the picture or the barcode.
• Events you share. If you tap Share on a calendar event, its details go to whichever app you choose in your phone's share sheet.
• Shoots you mirror to a calendar. If you turn on syncing in Settings, each shoot's title, call time, wrap time and location are written to the calendar you chose (with no wrap time set, the event ends 12 hours after call). Shoot notes are not included. If that calendar belongs to a cloud account such as Google or iCloud, your phone syncs the event to that account. That is your calendar provider's service, and we have no say in it.

Crash reports

Stacked uses Sentry, hosted in Sentry's EU region, to receive crash and error reports so we can find and fix bugs. Sharing is on by default and you can turn it off at any time with Settings → Share crash reports. When it is off, the app does not send them.

Before an error report leaves the app, Stacked strips it down to technical details: the type of error and where in the code it happened, when it happened, the app version, your operating system and its version, a short label saying which part of the app was involved (and, for a failed gear lookup, a short code saying why), and a short timeline of what the app did just before: when it opened or went to the background, and which web addresses it contacted, without the part of an address that carries coordinates, barcodes or dates. Error messages are removed, so the names of your gear, your shoot locations, your notes and your file paths are not sent. The app does not attach your IP address, name or email to a report, and Stacked has no account system to link one to. As with any web request, your phone's IP address reaches Sentry's servers when a report is sent. We have set up our Sentry project not to store it, nor the approximate location (city and country) Sentry would otherwise work out from it. How Sentry handles the data it receives is covered by its own privacy policy.

Crashes caught by your phone's native crash handler, rather than by the app's own code, are reported by Sentry's native component and are not stripped down in the same way. A report from an Android phone carries technical details about the phone and the app: the device's model and manufacturer, operating-system version and build, screen size, memory and storage figures, battery level and charging state, language and time zone, the type of network connection, whether the phone is rooted or the app was installed outside the store, which of the app's permissions are granted, and an installation identifier Sentry generates. It also carries a short list of system events from just before the crash, such as the app coming to the foreground and battery or network changes. Reports from an iPhone carry similar device details, and we have switched off Sentry's native logging of the app's web requests there. Stacked does not add your gear, shoots, locations, notes or photos to these reports.

We have switched off Sentry's session tracking and, on iPhone, its tracking of app hangs and background terminations, so nothing is sent on an ordinary launch. On Android, a report is still sent when the system flags the app as frozen ("App Not Responding"); like a native crash, it is not stripped down by the app.

Sentry's handling of the data it receives is covered by its own privacy policy.

What we don't do

• No advertising, and no advertising identifiers.
• No product-usage analytics or behavior tracking of our own. Apart from crash reports, the only diagnostic data is what Google's ML Kit barcode scanner may send to Google on Android (see above).
• No account, email address or password is requested in the current version of the app.
• No audio recording, and no tracking of your location or movements.
• No sale or sharing of your personal data with anyone for their own purposes.

Third parties

The services described above are the only third parties involved, and each receives only what is listed for it: Sentry (crash reports), UPCitemdb (barcode numbers), Anthropic (AI lookups, only with your own key), Open-Meteo (coordinates and dates for the weather), GitHub (the public catalog file), Google (metrics from its ML Kit barcode scanner, on Android), any website whose image link you paste, and any app you pick in your phone's share sheet, which receives what you share. Your phone's operating system (calendar, contacts, notifications, geocoding and camera) and the app stores (Google Play and the Apple App Store, which may collect information about installs and updates) operate under their own privacy policies, separate from this one. We do not control those third parties and they are not limited by this policy.

Emails you send us

If you email us, whether for support or to ask to be told when Stacked launches, we use your address and message only to reply or to send that launch notice. We don't share them or add you to any other list, and if you ask, we will delete them. This website has no analytics, ads or tracking cookies. It remembers your light or dark choice in your own browser, and it loads its typeface from Google Fonts, so your browser contacts Google when you open a page.

Your choices

Calendar, contacts, camera, photo library, location, motion and notification access are standard operating-system permissions. You can review or revoke any of them at any time in your phone's Settings app. You can turn crash reports off in Stacked's own Settings. You can avoid barcode and AI lookups by not scanning barcodes in Kit setup and not entering an API key, and you can avoid image downloads by not pasting links. Weather and place lookups happen for any shoot or scouted location you give a place (a shoot's place is looked up once, and again only if it changes or an earlier lookup didn't work; a scouted place is looked up each time you scout it), and the catalog download runs in the background. Uninstalling the app erases its local data.

Children's privacy

Stacked is a professional planning tool and is not directed at children under 13. We do not knowingly collect personal information from children.

Changes to this policy

If this policy changes, we will update the "Last updated" date above and, for any change that materially affects what the app accesses or sends, describe it here. Continued use of the app after an update means you accept the revised policy.

Contact

Questions about this policy or how Stacked handles data can be sent to hello@sleepingiantmarketing.com.