Strange Signal Studios — official logo

Privacy & information

Privacy Policy.

Last updated: October 30, 2026

About this policy. Strange Signal Studios explains how the website and Signal Contact handle information, including on-device investigations, external services, user-controlled sharing, and support communications.

1. Introduction

This policy explains the privacy practices of the Strange Signal Studios website and the reviewed Signal Contact Android implementation. Signal Contact is an experimental sensor-based application. This policy covers website visits, app functionality, user-directed sharing, and support communications.

This policy distinguishes implemented functionality from planned features. Describing a future feature does not mean it is active.

2. Information We Collect

The reviewed website has no registration, contact form, analytics, advertising tags, third-party embeds, or application database for visitor information. Its own scripts do not set cookies or use browser local/session storage for tracking. Your browser may cache page assets as part of normal browsing.

Copy Email writes the displayed public support address to your clipboard only when you select that control. It does not send your clipboard contents or personal information to the studio.

Signal Contact does not require an app account or personal contact details for local investigations. Session names, custom words, and anything you choose to send in a support message can contain personal information. Avoid entering or sending information you do not want retained.

3. Website Hosting and Technical Data

When this website is served through Cloudflare Pages, Cloudflare processes the technical connection and request information needed to deliver and protect the site.

If served through Cloudflare, requests involve technical information such as IP addresses, requested resources, and traffic-routing information. Cloudflare describes its processing of end-user traffic and customer logs in its Privacy Policy. Security features can set cookies depending on which services are enabled; see Cloudflare's cookie documentation.

Hosting-provider processing is separate from app investigation records. The provider's applicable settings and practices govern technical logs and security cookies; no fixed hosting-log retention period or guarantee of zero hosting cookies is asserted here.

4. Signal Contact and Device Sensors

Depending on hardware, feature, and mode, Signal Contact accesses acceleration, magnetic field, ambient light, air pressure, proximity, and angular velocity (gyroscope). Readings, calibration, and interpretation are processed on your device. No continuous saved raw-sensor stream or automatic sensor/session upload feature was identified.

Environmental Response and Signature Interpretation use sensor activity and defined software rules to generate experimental responses. Proximity is not used for Signature detection. These responses are not scientific evidence of communication.

The reviewed app requests internet access, notifications, foreground-service/media-playback permissions, and wake-lock support. Existing merged build manifests also include network-state and boot-completion permissions for dependency-supported background work. A speech-service query identifies compatible installed text-to-speech engines. No microphone, camera, location, broad-storage, or advertising-ID permission was identified in the reviewed manifests.

Bundled meditation and tone audio plays from app resources; the app does not record conversations or ambient audio. Spoken responses pass selected words to the installed Android text-to-speech engine. The app selects installed English voices reported as non-network voices and rejects network-voice/download fallback. Android and the chosen engine have their own practices.

5. Saved Sessions and Exports

App-private saved sessions can contain a chosen name, random local identifier, start/end times, settings, selected words/responses, and accepted sensor-derived evidence. Signature evidence includes processed feature information and a snapshot of the complete word bank used, potentially including custom words not selected in a response.

The app also stores current custom words, detection/presentation/speech preferences, narrator and Beacon choices, and a separate Guided Contact checkpoint containing setup, stage, session identity, and audio position.

You can save or share TXT/CSV session exports containing names, identifiers, times, settings, selected responses, and measurement/Signature evidence. Session exports include bank count/fingerprint rather than complete historical word-bank text. A separate custom-word export contains the current custom-word list.

Sharing creates a cached export copy and uses Android's chooser with temporary file-read access for the recipient app. Cancelling can leave the cached copy. Save/import/export operations use your selected document provider. The app requests local-only selection, but providers may still synchronize or be cloud-backed. Review files before sharing; recipient apps, people, and providers control copies they receive.

6. Third-Party Services

The app uses HTTPS for news feeds from UFOUAP, The Debrief, The Black Vault, and NASA, plus publisher/feed-specified image or CDN hosts. Opening News or refreshing can request feeds; displaying uncached images can request thumbnails.

Expanding the Joe Rogan Experience group requests its YouTube feed and may load YouTube thumbnails. Optional episode notifications are off by default. When enabled and permitted, background feed checks are scheduled approximately every 12 hours, subject to Android network, battery, and scheduling conditions.

These requests expose normal connection/request data such as your IP address, requested URL, timing, and generic client headers to receiving hosts. The reviewed feed/image client does not attach sensor readings, session names, saved responses, or custom words. Provider logging, retention, and onward processing are governed by their own practices and were not independently verified.

Choosing an article, video, podcast, or external meditation/tone resource opens an external app or browser. Destinations may use cookies, account associations, or tracking under their policies. Signal Contact does not guarantee tracking parameters are removed from opened links. Android, Google Play, device vendors, speech engines, browsers, and document providers are separate services.

7. Advertising and Future Features

No active advertising, analytics, crash-reporting, billing SDK, or embedded WebView was identified in the reviewed app source and dependency declarations. Runtime libraries include AndroidX interface, lifecycle, and background-work components. The website includes no advertising or analytics scripts.

Planned advertising, premium functionality, releases, or future services are not described as active. Material changes to data practices require an updated policy and any applicable notices or permissions before those practices begin.

The practices described here refer to the reviewed implementation. Android, Google Play protection features, device vendors, and external providers have their own practices; the absence of an app advertising or analytics SDK does not establish that those services process no information.

8. Support Communications

Selecting Email Support opens a mailto link addressed to [email protected] in your configured email application. The website does not send a message automatically. If you send it, the studio and involved mail services receive your email address, message, attachments, and associated mail information.

Support communications are used to respond to questions and investigate issues. Include only necessary details; do not send passwords, financial information, or unnecessarily private investigation records.

Strange Signal Studios keeps support emails while they are needed to handle the request and related follow-up, then deletes them manually from the mailbox used for support. This is not an automatic deletion schedule or fixed deadline. Copies held by mail providers or recipients are subject to their own practices.

Support correspondence is separate from app records. Deleting app data does not delete email or attachments you have sent. The confirmed public address uses email forwarding; mail delivery and any reply workflow involve the configured mail services.

9. Data Retention and User Choices

Saved investigations, current words/preferences, Guided progress, and session-export caches have no fixed age-based expiry in the reviewed implementation. Feed/image caches can be replaced, evicted, or cleared by Android; the news display window is not a universal deletion deadline.

  • Use History confirmation controls to delete an ended session or all eligible ended sessions. Active-run restrictions apply.
  • Editing/deleting a current custom word does not rewrite historical Signature snapshots, saved responses, or earlier exports.
  • Deleting a session does not delete current word banks, unrelated settings, cached exports, separate Guided progress, or copies shared/saved elsewhere.
  • Android app-storage controls or uninstalling provide broader removal of app-private information. They do not remove externally saved, synchronized, or sent copies. Manage those at their destination.
  • Turn off optional episode notifications to cancel scheduled checks and active alerts; this does not itself erase local seen-episode history.

Automatic Android app backup is disabled and cloud-backup/device-transfer exclusions are declared. This is not a guarantee about independent device/provider copies. There is no app-account cloud sync or remote deletion service. Hosting data follows provider practices; support-email retention and manual deletion are described above.

10. Security

The app uses Android app-private storage and HTTPS for its built-in feed/image requests. It does not add app-specific file encryption or secure erasure. Exports have the protections of the chosen location, provider, recipient, and device settings.

Keep your device and email account protected, review what you share, and avoid including sensitive information unnecessarily. No method of storage or transmission is guaranteed completely secure.

11. Children's Privacy

Signal Contact is intended for teenagers and adults aged 13 and older. It is not intended for, and does not intentionally target, children under 13.

Signal Contact does not require an app account or request your age or date of birth. This audience statement does not mean the app verifies users' ages. The information practices described in this policy apply to use of the app.

If you have a concern about a child's information, contact [email protected] without sending unnecessary sensitive details.

12. Policy Updates

This policy was last updated October 30, 2026. We will review it when website, app, hosting, or support practices materially change. The policy will show its updated date, with any additional notices required for those changes.

13. Contact Information

For questions about this policy or the privacy practices described here, contact Strange Signal Studios at [email protected].

You can also read our Contact & Support guidance before sending an issue report.