Privacy Policy
This policy describes how the intellidip website and apps (together, "the services") handle information. The services are published by intellidip ("we", "us"), and you can reach us at intellidip@gmail.com.
Summary
- No account is needed, and we do not sell your personal information. Where an app shows personalized ads, though, Google uses device advertising data, which some laws treat as a sale, sharing, or tracking.
- Ads, app analytics, and crash reporting follow the choices you make in the app.
- Most entries stay on your device. The app-specific features below explain when choices go to our server, a public lookup service, your calendar provider, or a recipient you choose. Advertising, diagnostics and purchase services also receive the information described below.
Information on your device
What you enter or create in an app, and your settings, are stored on your device. Uninstalling the app or clearing its data removes them, except for any copy made by your device's backup service (such as iCloud or Google backup) under your device settings.
Some apps let you move or share what you saved, such as a list of items you watch, by showing a QR code or creating a code you send yourself. The code holds that list, including anything sensitive in it, and goes only where you scan or send it. We never receive it.
How this differs by app
- Options Pricing Suite, Nightwick, Renewal Day, Shiftfolk and Nightjar. Calculator entries and portfolios, sound mixes, renewal records, shift schedules and game progress are stored locally rather than uploaded to an intellidip product backend. Ads, diagnostics, purchases and user-initiated sharing remain separate flows. Nightwick and Nightjar play audio; they do not record through your microphone.
- Only Breaking. Reading public news uses our Supabase-hosted service. An anonymous installation record and preferences sync even when push alerts are off; notification permission and the alerts setting control push delivery, not that storage. Authorized editorial staff sign in to separate internal tools; consumer apps need no login.
- Recall Bell. Public notices and source-check metadata can be downloaded with alerts off. Only while recall alerts are on does the alert service receive normalized watch topics, a random installation identifier, time zone and push token. Topics can include allergens or medicine/device categories. The Consumer Health Data Privacy Policy describes those choices. Source-check times are public operational information, not a guarantee that every recall is present or that an item is safe.
Features that use our server
Supabase hosts the Only Breaking and Recall Bell services. Push delivery uses Expo's push service and Apple's or Google's push service. These services process installation, preference, topic, time-zone, token and delivery information as applicable to the app above. We do not ask consumer app users for a name or email address to register an installation.
Use the app's data-deletion control to delete the server registration. Recall Bell also deletes it when alerts are turned off and rotates its local installation identifiers. If you are offline, deletion waits and retries until acknowledged; turning off a switch does not instantly erase an unreachable server. Only Breaking's alerts switch stops pushes but does not delete its preferences; use Delete my data instead. Support can help with the request code under Settings → Your data.
These services expire inactive installation records after 12 months without use; deletion can take up to three more days. Delivery and ingestion operational records have their own retention rules, including a 90-day operational-log period in Recall Bell. Copies in the hosting provider's backups expire under that provider's backup schedule rather than disappearing instantly.
Public lookups and notice photos
Recall Bell can send a barcode to Open Food Facts, vehicle make/model/year to NHTSA or vPIC, or brand and product search words to CPSC. These optional requests can run with recall alerts off; they send ordinary network metadata but no Recall Bell installation ID, push token or VIN. Public agency product photos can load from CPSC when a notice opens. Scanning a barcode or QR code does not upload the camera image. The selected vehicle or product may still be saved on your phone, and a confirmed watch's normalized topics go to the alert service only while alerts are on.
Device permissions
Apps ask for a permission only when you use a feature that needs it, and the rest of the app works without it. They may ask for:
- Camera to scan a barcode or QR code. Images are not saved or sent.
- Calendar to add events to a calendar the app creates for itself. Your other calendars' events are not read. Your device or calendar-account provider may sync the events you publish under its own settings and policy.
- Notifications to show alerts and reminders you turn on.
Analytics and crash reporting
The apps use Google Firebase Analytics and Firebase Crashlytics to understand usage and fix crashes. They may receive device and app information (such as device model, operating system, app version, language, and approximate location from your IP address), usage events (such as screens viewed, features used, and purchases or restores), and crash diagnostics. App code does not attach the text, names or contents of your saved entries to those reports. Event collection differs by app: Recall Bell adds no custom events or automatic screen reports. Public content or a device identifier is different from the personal entries you save.
The website uses no analytics, cookies, or tracking.
Advertising
Apps with ads use Google AdMob. Google may collect your device's advertising ID (where permitted), approximate location from your IP address, ad views and taps, and diagnostic information. Ads are personalized only where your choices and local law allow. Otherwise, where ads are permitted, Google is asked for non-personalized ads; where they are not permitted, no ad is requested. We never give Google what you enter, save, or view in an app for ad targeting.
On iOS, apps ask for tracking permission before using the advertising ID. In U.S. states that give you the right to opt out, the app's Privacy options let you opt out of the sale or sharing of personal information and of targeted advertising. Where ads are personalized, Google may collect information about your activity across apps and websites over time. The services do not respond to browser Do Not Track signals, so use the choices described here instead. See how Google uses information from apps that use its services and Google's Privacy Policy.
Purchases
Purchases, such as removing ads, are processed by Apple or Google; we never see your payment details. RevenueCat, which manages purchases for us, receives its own generated app-user identifier and the store's purchase record so that purchases can be restored.
Your choices
- Consent. Where the law requires it, apps ask before showing personalized ads or collecting analytics and crash reports, and analytics and crash reporting stay off until you choose. You can change your choices at any time under Privacy options in the app, where shown.
- Effect of a change. Changes apply to new data; turning crash reporting off takes effect the next time the app starts. A crash report may remain queued locally and be sent if collection is later enabled. Changing a choice does not delete data already sent; contact support about deletion requests.
- Device settings. You can reset your advertising ID or limit ad personalization in your device's privacy settings.
Declining ads personalization, analytics, crash reporting, or tracking never limits an app's features.
Retention and security
Firebase retains analytics and crash data under its product policies and each app project's retention settings. Google and RevenueCat retain advertising and entitlement information under their own policies. Contact us to request access or deletion; removing the app or withdrawing consent does not automatically erase data those services already received. Purchase management may operate independently of advertising or analytics consent to recognize an entitlement.
Data sent to our servers or providers is encrypted in transit. Local storage and backup differ by app: Recall Bell's watch-list files are excluded from OS backup; Nightjar includes game progression in OS backup. Other apps' backup and export controls follow their device and app settings. Deleting an entry does not recall a copy you already shared or a device/provider backup. QR/text transfers, files and reports go to the recipient or share-sheet service you choose; intellidip does not receive those exports.
Links to other websites
Other websites you open from an app or this site are governed by their own privacy policies.
Children
The services are not directed at children under 13. If an app store supplies an age range, the app uses it on the device to limit ads and analytics; the age range itself is not sent to us. When the store indicates a user is under 13, the app requests no ads and turns Firebase Analytics off. When it indicates a user is 13 to 17, apps request only non-personalized ads.
Crash reporting follows the consent choices described above, not the age range, so Firebase Crashlytics can receive crash and error reports from any user, including one the store indicates is under 13. A report carries a random installation identifier, device and app details, and the technical details of the failure. We use these reports only to support the apps' internal operations: to find, diagnose and fix crashes and errors and keep the apps working. We do not use them to contact anyone, build a profile, select or measure ads, or for any other purpose. Our app code does not add your names, entries or other content to these reports, and access to them is limited to the people who maintain the apps.
A parent or guardian can email us with the subject "Privacy request" to ask about a child's information or request its deletion.
Your rights
Depending on where you live, you may have the right to access, correct, delete, or receive a copy of your personal data, and to object to or restrict its processing. Email us to make a request; for data held by Google or RevenueCat, we pass the request on where we can, and Google's own privacy controls also apply.
California residents
In the past 12 months, the services collected these categories of personal information: identifiers (a random installation ID, the advertising ID, push tokens, and IP address); app and website activity (usage events and ad interactions); approximate location derived from IP address; purchase records; and the choices you make for a feature (such as a region, topics, or items you watch). It comes from you and your device, is used for the purposes described above, and is kept as described under Retention and security.
We disclose these categories to our service providers (Google Firebase, Supabase, Expo, and RevenueCat) for those purposes. Where an app shows personalized ads, identifiers, app activity, and approximate location are made available to Google for advertising, which California law treats as selling or sharing. We do not knowingly sell or share the personal information of consumers under 16.
You have the right to know what personal information we collect, use, disclose, sell, or share; to delete it; to correct it; and to opt out of its sale or sharing, without being treated differently for using these rights. To opt out, use Privacy options in the app. For other requests, email us; because we hold no names or accounts, we may ask for details from the app to find your data. You may use an authorized agent, and we may ask the agent for proof of your permission. The website does not sell or share personal information, so browser opt-out signals such as Global Privacy Control have nothing to act on there.
Changes to this policy
When our practices change, we update this page and its effective date.
Contact
Email intellidip@gmail.com, or see Support.