Obserc — Beta Privacy Policy

Last updated: August 8, 2025

Thank you for participating in the Obserc Beta Program. This page explains what data we collect during beta testing, how we use it, who we share it with, and how you can control or delete your data. Obserc is an AI-powered personal safety system focused on detecting and responding to emotional, verbal, and physical danger signals. Because the beta includes experimental audio/video detection and device-level integration, we aim for clear, conservative handling of test data.

Quick summary

Short version: For Beta testing we collect only the data needed to evaluate and improve Obserc’s models and features — e.g., audio snippets, device telemetry, crash logs, and feedback you provide. We keep this data secure, use it only to improve Obserc, and do not sell it. You can opt out of beta testing at any time; contact privacy@obserc.com to request data deletion.

Scope & legal basis

This policy applies to data collected while you participate in Obserc’s Beta Program and while using Obserc beta builds and devices (collectively “Beta Services”). By accepting an Auth Code and installing a beta build you consent to the data practices described here. Where additional legal bases are required (e.g., in the EU), we rely on consent and legitimate interests for improving product safety and reliability.

What data we collect in beta

We minimize collection wherever possible. Typical categories collected during Beta include:

• Audio captures and derived signals: Short audio snippets or features extracted from audio (voice activity, tone, emotional-signal embeddings) used for detection research. Raw audio is kept only when needed and subject to stricter retention rules.
• Video / camera captures (if enabled): When testing device camera features, we may collect video frames or derived metadata (motion, object detections). Raw video is collected only if you explicitly enable a camera build and consent to camera testing.
• Device metadata: Device model, OS version, app version, battery level, sensor availability, and connectivity logs (no access to unrelated files).
• Events and labels: Timestamps, detection events, model confidence scores, and tester-provided labels (e.g., “false alarm”, “true alarm”).
• Performance & reliability logs: Crash reports, stack traces, CPU/memory usage, and network performance metrics.
• Feedback submissions: Anything you send through the built-in feedback form (text, screenshots, attachments, email if provided).
• Auth code usage: We log which Auth Codes are used and when to manage access and revoke codes where necessary.

What we do not collect

• Your full contact list or arbitrary files stored on your device.
• Any content beyond what the app explicitly captures for detection (we do not upload your photos, documents, or unrelated media).
• Payment information (we do not process payments in Beta).

Why we collect this data

We use Beta data for limited, explicit purposes:

• To evaluate and improve our detection models (accuracy, latency, false alarms).
• To fix bugs, reduce crashes, and optimize battery and network usage.
• To analyze feature adoption and user workflows during Beta.
• To audit decisions during escalations and to improve safety outcomes.

How we process and protect your data

We implement technical and organizational measures to protect Beta data, including encryption in transit (TLS) and encryption at rest for sensitive data. Access to raw audio, video, and identifiable logs is restricted to a small group of authorized engineers and analysts who have signed confidentiality agreements.

Note: For safety research we sometimes use human review of short segments for labeling and model improvement. All reviewers follow strict access, retention and redaction rules.

Anonymization & aggregation

When possible we store and analyze data as aggregated metrics and anonymized feature vectors rather than raw audio/video. Raw files are purged or truncated unless retaining them is necessary to debug a reported issue or investigate model failures.

Sharing & third parties

We do not sell or rent your personal data. We may share data only with:

• Service providers who help host and operate Beta (storage, analytics, crash reporting). They process data on our behalf under contract and are required to protect it.
• Trusted research partners under strict data-use agreements and only with explicit additional consent if required.
• Law enforcement or authorities if required by law — we will notify you unless prohibited.

Feedback and support uploads

Anything you submit via the feedback form (text, attachments, screenshots) can be used by Obserc to diagnose issues and improve models. Do not include information you do not want to be used for research. If you send sensitive personal information by mistake, contact privacy@obserc.com to request redaction or deletion.

Data retention

Retention balances utility and safety with privacy:

• Evaluation & metrics: Aggregated metrics and non-identifying telemetry are retained for product analytics (typically 2–5 years).
• Raw audio/video & detailed logs: Retained only as long as necessary to investigate issues or improve models — usually no longer than 90–540 days unless you consent to a longer retention for debugging a specific problem.
• Feedback submissions: Retained until resolved plus 1 year for product improvement unless you request deletion.

If you need a specific retention exception (for debugging an important issue), contact privacy@obserc.com.

Your choices & controls

As a Beta tester you have these options:

• Leave the Beta: Stop using Beta builds. Uninstall the beta app and revoke your Auth Code by emailing privacy@obserc.com.
• Opt-out of specific data collection: Where feasible, toggle features off in the app (for example camera testing). Note some telemetry is required to diagnose critical failures.
• Access & deletion requests: Request a copy of the personal data we hold about your participation, or request deletion by emailing privacy@obserc.com. We will respond in accordance with applicable law.

Children

The Obserc Beta Program is not intended for children under 16. If you are a parent or guardian and believe your child under the age threshold has enrolled, contact us at privacy@obserc.com and we will remove the child’s data promptly.

Security incidents

In the event of a data breach affecting Beta data, we will notify impacted testers and any required regulators as soon as possible and will provide remediation steps. We maintain an incident response process and perform regular security testing.

International data transfers

Obserc may store and process Beta data in locations outside your country. When we transfer data internationally, we rely on appropriate legal safeguards (e.g., standard contractual clauses) to protect your rights.

Legal & governing law

This Beta Privacy Policy is governed by the laws of the country in which Obserc is domiciled for operational purposes. Where local privacy laws provide greater protections, we will comply with them. If you have specific jurisdiction questions, contact privacy@obserc.com.

Changes to this policy

We may update this policy as the product and legal environment evolve. Material changes will be communicated on this page and via major beta communications. We recommend you check this page occasionally.

Contact & requests

For privacy questions, data access or deletion requests, or to revoke your Auth Code, contact:

Email: privacy@obserc.com

Please include your tester Auth Code (if available) and the email you used for the Beta so we can locate your data quickly.

Acknowledgement

By participating in the Obserc Beta Program you acknowledge that you have read and understood this policy and consent to the described data practices for the purposes of product testing and improvement.

Thank you for helping build Obserc. Your care, time, and feedback make the product safer and more reliable for everyone.