FrigoSense Privacy Policy
Effective date: July 15, 2026
Contents
- Who we are
- Data we collect
- How we use data
- Sharing and processors
- App permissions
- Retention and deletion
- Security
- Your choices and rights
- Children
- Changes
1. Who we are
FrigoSense provides cold-chain and food-quality monitoring using IoT sensors, a cloud dashboard, notifications, and diagnostic tools.
Privacy contact: info@frigosense.com. Account deletion requests can also be submitted at /delete-account.php.
2. Data we collect
| Category | Examples | Purpose |
|---|---|---|
| Account data | Name, email address, password credential metadata, account ID, organization membership, role, Google or Apple sign-in identifiers when used. | Account creation, sign-in, organization access, support, and security. |
| Device and telemetry data | FrigoSense device ID, device name, firmware version, battery/supply status, signal timestamps, temperature, humidity, pressure, door status, CO2, NH3, H2S where installed, raw gas resistance channels gas1/gas2/gas3, diagnostics, device events, and analysis outputs. | Dashboard display, monitoring, alerts, diagnostics, quality analysis, model validation, and service reliability. |
| Provisioning data | Bluetooth scan/connect events and Wi-Fi network information entered during setup. | Connecting a FrigoSense device to Wi-Fi. Wi-Fi credentials are sent to the device during provisioning and are not used for advertising. |
| Notifications | Push notification tokens, platform, notification preferences, delivery state, and notification history needed for deduplication. | Sending service, quality, safety-risk, and device-status notifications when enabled. |
| Usage, diagnostics, and security data | Session cookies, refresh tokens, IP-derived security logs, browser or app user agent, device management actions, account deletion requests, error logs, service worker/cache state, and rate-limit records. | Security, abuse prevention, troubleshooting, audit, and service operation. |
| Analytics and conversion events | Limited website events such as registration or install-conversion events, where analytics or conversion tags are enabled on the public website. | Measuring product adoption and improving web onboarding. The mobile app does not run FrigoSense advertising conversion tags, and sensor telemetry is not used for advertising personalization. |
| AI and service diagnostics | Telemetry summaries, deterministic verdict context, and diagnostic state that may be used to generate FrigoAI explanations or operator briefings. | Explaining already-computed results where FrigoAI is enabled. The current mobile app does not run FrigoAI requests. AI text does not make the primary freshness, safety, or device verdict. |
3. How we use data
- Provide the FrigoSense app, dashboard, device list, charts, history, and account features.
- Receive and process telemetry from FrigoSense devices.
- Generate deterministic monitoring, spoilage, device-health, and safety-risk diagnostics.
- Send push notifications when enabled by the user or organization.
- Support device provisioning, troubleshooting, customer support, account deletion, and audit workflows.
- Improve algorithms, product reliability, and data quality using telemetry, replay sets, labeled lifecycle runs, and aggregated or de-identified datasets where possible.
- Protect the service from abuse, unauthorized access, and data loss.
4. Sharing and processors
We do not sell personal data. We do not use food-sensor telemetry for advertising personalization.
We may share data with service providers that help operate FrigoSense, including:
- hosting, storage, backup, database, monitoring, and security providers;
- authentication providers, including Google and Apple, when you use their sign-in services;
- Firebase Cloud Messaging or equivalent push providers for notification delivery;
- email, support, and operator-notification tools;
- analytics or conversion-measurement providers when those tags are enabled on the public website;
- AI service providers for explanation or briefing features, when enabled on the web dashboard. The current mobile app does not run FrigoAI service-provider requests.
If your account belongs to an organization, organization administrators and authorized members may see account, device, telemetry, alert, and role data needed to operate that organization. We may also disclose data if required by law, to protect users or the service, or as part of a business transfer with appropriate notice.
5. App permissions and device access
Bluetooth
The mobile app uses Bluetooth to find and configure FrigoSense devices during setup. On iOS, FrigoSense requests Bluetooth permission for this purpose.
Location on Android
Android may require a location permission before apps can scan for nearby Bluetooth devices. FrigoSense uses this permission for Bluetooth provisioning only. FrigoSense does not use it to track precise location or movement.
Notifications
If you enable notifications, the app registers a push token with the server so FrigoSense can send device and monitoring alerts. You can disable notifications in the app or operating-system settings.
Cookies, local storage, and service workers
The web dashboard and app webview use cookies, local storage, and service workers for sign-in, app shell caching, preferences, language, and session continuity.
6. Retention and deletion
Data is important to FrigoSense because historical telemetry is needed for diagnostics, safety records, model validation, and replaying algorithms. We keep data only as long as it is needed for these purposes, legal obligations, security, backups, or legitimate business needs.
- Account data is kept while the account is active and then deleted, deactivated, or anonymized according to the account deletion workflow.
- Authenticated account deletion requests deactivate the account, revoke sessions and push tokens, remove memberships, and unlink device claims controlled only by that account.
- Public deletion requests require ownership verification before processing.
- Telemetry may be retained in de-identified or organization/device-history form to preserve diagnostics, safety records, model validation, and aggregated product quality analysis.
- Heavy derived analysis cache may be pruned after 12 months because it can be recomputed from raw telemetry.
- Raw telemetry is normally retained for up to 48 months in the primary system when storage allows, then moved to encrypted archive or aggregates where feasible instead of being deleted by default.
- Aggregates and anonymized statistics may be retained for longer periods for reporting, research, and service improvement.
- Encrypted backups follow daily, weekly, and monthly retention schedules and may persist for a limited time after operational deletion.
To delete your account, use the in-app deletion control or visit /delete-account.php. You can also contact info@frigosense.com.
7. Security
FrigoSense uses HTTPS/TLS for network transmission, authenticated sessions, signed or authenticated device ingestion where supported, access controls, operator audit trails, encrypted backups, and separation of backup keys from backup storage. No system can be guaranteed perfectly secure, but we work to protect data against unauthorized access, loss, misuse, and alteration.
8. Your choices and rights
Depending on where you live, you may have rights to access, correct, export, restrict, object to, or delete personal data. To make a request, contact info@frigosense.com.
- You can sign out, disable push notifications, or revoke app permissions in the operating system.
- You can request account deletion from inside the app or from the public deletion page.
- Organization access may also be managed by organization administrators.
9. Children
FrigoSense is intended for business, professional, and adult household use. It is not directed to children and should not be used by children without appropriate adult or organizational supervision.
10. International transfers
FrigoSense and its service providers may process data in countries other than your own. Where required, we use appropriate safeguards for cross-border processing.
11. Changes
We may update this Privacy Policy when the app, data practices, service providers, or legal requirements change. The effective date at the top of this page shows when this version took effect.