Privacy Policy

1. Who we are and scope

This Privacy Policy describes how NecroTube ("we", "us", or "our") handles information in connection with its paranormal investigation app and related services at www.necrotube.com. The developer/operator responsible for this processing is identified below.

Developer/operator: Cortical Labs
Contact email: corticalabs@yahoo.com

Governing jurisdiction: Québec, Canada. This does not limit mandatory privacy rights that apply where you live.

NecroTube includes tools involving camera input, audio and device sensors. Live streaming, social account connections, multistreaming and server-side archives described below are planned or optional features, not a statement that they are currently released. Their availability depends on your app version, device, region and connected platform. Additional information and choices must be provided before a new feature collects information.

The current Google Play app code reviewed for this policy saves recordings on the device and uses Firebase Analytics. It does not implement remote media uploads, a cloud recording archive or Live broadcasting. The descriptions of future Live features below apply only if those features become available and you choose to use them.

2. Camera access and SLS processing

Where available, camera permission enables camera-based investigation tools, including SLS-style visual processing, and video capture or Live streaming that you choose to start. Camera frames can be processed to display visual overlays or estimates of shapes and movement. Such output is not proof of a person, spirit or paranormal event, and is not intended to identify people.

The current app passes camera frames to Google ML Kit pose detection for SLS-style processing and saves captured video through Android's local media storage. No remote camera-frame or video upload is implemented in the app code. Granting camera permission is not consent to publish footage. If a future feature sends camera content to a service for processing, the feature must explain the recipient and purpose before that transfer. You can deny or revoke camera access in your device settings; dependent features will not function.

3. Microphone access and EVP recordings

Microphone permission enables audio-based tools, electronic voice phenomenon (EVP) recording and, where available, sound in a Live broadcast. Recordings may contain your voice, other people's voices and background sounds. Start recording only when you have the necessary permissions and consent from those involved.

EVP and radio-sweep audio recordings are saved as local WAV files. Recordings and user-created media remain local to the device unless you explicitly share or export them, or choose to use a future Live feature; device or third-party backup settings may separately copy local files. The current app's audio-sharing control opens Android's share chooser, allowing you to select another app to receive the file. No automatic upload of these recordings to a NecroTube server is implemented. Microphone permission alone does not authorize publication on NecroTube's channels. You can revoke microphone access in device settings, which disables features that require it.

4. Device sensors and EMF-related tools

Compatible tools use available sensor readings, such as magnetic-field measurements from a magnetometer and motion or orientation readings from an accelerometer or related sensors, to calculate and display investigation outputs. Availability and precision vary by device. EMF-style readings describe sensor responses and are not scientifically verified paranormal detections.

The current app sends selected tool outputs and derived sensor values to Firebase Analytics: emitted words, intensity, trigger reasons, magnetic-field change, combined energy and a fusion-trigger indicator. This telemetry is distinct from uploading raw audio or video recordings. Sensor information may also appear in local session logs or overlays. Any additional collection or transfer of sensor history must be described when offered. Manage relevant permissions through your device where supported.

5. Local data and information you provide

App settings, preferences, custom lexicon files, session logs and audio recordings are stored locally. Captured videos are saved in Android's media storage. The app allows Android backup, so device or cloud backups may copy app data according to your device settings. Exported files, shared media and backups may persist separately after uninstalling or clearing app data. Use your device's file and backup controls to manage those copies.

If you contact us, we receive the contact details, message and attachments you provide to handle your request. Do not send account passwords, authorization tokens or unnecessary sensitive information. Website hosting may process request information such as IP addresses, browser details and access times to deliver and protect the site.

6. Analytics and crash diagnostics

NecroTube uses Firebase Analytics, initialized when the app starts. The app sets device model, language, country from the device locale and app version as analytics properties. It logs app/session events, tool use, language selections, website clicks, sharing actions, trial/paywall interactions and purchase results. Event parameters include selected subscription type, displayed price and currency, purchase order ID when available, billing error codes, trial-screen timing, and the tool outputs and derived sensor values described above. The app's analytics event code does not attach raw audio, video, images or recording files.

The reviewed app code does not implement an analytics consent screen, an in-app analytics opt-out or an analytics-data reset control. It does not specify Firebase's server-side analytics retention settings, so this policy does not assign a retention period to those records. See Firebase privacy and security information for service-specific practices.

Firebase Crashlytics is not integrated in the reviewed app code or declared dependencies, and no other dedicated analytics or crash-reporting SDK is declared alongside Firebase Analytics. The app writes local Android diagnostic logs and sends billing error codes as analytics events; these are not Crashlytics crash reports. This does not describe diagnostics that Android, Google Play or third-party SDKs may handle independently.

7. Google Play Billing and subscriptions

For purchases made through Google Play Billing, Google processes payment information under its own terms and privacy policy. Subscription administration may involve purchase tokens, product identifiers, transaction history and entitlement status to verify access, restore purchases and handle support. NecroTube does not need your complete payment-card details to verify a Google Play purchase.

The current app uses Google Play Billing directly. Cancelling a subscription and deleting app data are separate actions.

8. Optional Google, YouTube, Facebook and Instagram connections

Where available, you may authorize a Google/YouTube or Facebook/Meta account connection to use supported Live features. Instagram connections may be offered if and when supported. An account connection is optional and must use the platform's authorization process; do not provide your platform password to NecroTube.

The permissions shown during authorization determine what can be accessed, such as account/channel identifiers, basic profile information and permissions to create or manage the broadcasts you request. Information obtained through a connection is used to provide the authorized functionality, not to authorize unrelated posting or publication on NecroTube's official channel.

9. OAuth tokens and authorization security

Access tokens and, where issued, refresh tokens allow a connected feature to act within the permissions you grant. For a future connection feature, authorization data must be protected with encrypted transport, protected device storage or encrypted server storage as appropriate, restricted access and exclusion from public pages and diagnostic logs. These are requirements for the planned feature, not a claim that a Live authorization backend already exists.

You can revoke Google access through your Google account permissions, and Meta/Instagram access through the relevant platform's connected-app settings. Where an in-app disconnect control is offered, you may also use it. Revocation stops future authorized access; request deletion of retained connection data separately using the contact details above. Tokens should be removed when no longer needed, and connected-platform data must be deleted or refreshed as required by that platform's rules.

10. Optional Live streaming and multistreaming

If you choose to use NecroTube Live, where available, Live video and audio may need to be transmitted to servers and third-party platforms selected by you. Broadcast titles, destination identifiers and technical connection information may also be transmitted to those platforms and any disclosed streaming service needed to deliver the broadcast. These features are not currently released. Additional retention, processing and platform-specific disclosures will apply when those features become available. Viewers and destination platforms may see your content and associated account information according to your broadcast settings.

Optional multistreaming sends a broadcast to more than one selected destination. Each destination has its own audience controls and data practices. Choose destinations carefully: a private setting on one platform does not make another destination private. Viewers may record or redistribute public content, and stopping a stream cannot retrieve copies already made.

11. Optional archives and official-channel publication

NecroTube may offer recording or archiving of Live sessions. Before you enable a NecroTube-hosted archive, the feature must explain what is saved, where it is stored, who can access it, how long it is retained and how to delete it. No fixed hosted-video retention period is promised while that feature is unimplemented. A retention period and deletion process must be specified before it launches.

If a future feature offers publication or archiving of your completed Live session on the official NecroTube YouTube channel, separate, explicit user consent will be required before any such publication or archiving. Recording or streaming alone does not authorize it. The request must identify the recording, intended use, any editing and the agreed publication scope and duration. Refusing is not consent and does not transfer ownership. Contact us to withdraw permission for future use or request removal of an official-channel copy; third-party copies may remain beyond our control.

A destination platform may create its own replay or archive according to your settings and its rules, independently of a NecroTube archive.

12. Purposes, data sharing and third parties

Information is used to provide requested tools and services, manage purchases, respond to support, maintain security and, where enabled, improve reliability. Depending on applicable law, processing may rely on performing our agreement with you, your consent, legal obligations or legitimate interests in operating a secure service, subject to your rights.

Information may be shared with service providers only as needed for those purposes, with destinations you authorize, to comply with valid legal requirements, or to protect people and address fraud or misuse. A business transfer involving personal information would remain subject to applicable safeguards and notice requirements. This policy does not authorize selling personal information or using connected-platform data for advertising.

Third-party platforms control their own services. Review Google's Privacy Policy (including Google Play and YouTube), Meta's Privacy Policy and Instagram's Privacy Policy, as applicable. Removing information from NecroTube does not automatically remove a platform's separate records.

13. Retention and deletion requests

No NecroTube server-side media retention applies to current recordings, audio, video, images or other user-created media because the current app does not upload or archive them on NecroTube servers. The app does not implement timed expiry of saved recordings or session-log files. Its recording-list delete action removes the selected local audio file. Temporary PCM files and failed or empty EVP output are cleaned up during recording processing, and video processing removes the original silent video after combining it with audio. Temporary session audio uses a reusable cache file. The in-memory session log keeps up to 100 entries and is cleared when a new session starts; this is separate from saved session-log files.

Local files remain subject to device storage, app-data deletion and backup settings. These local-content rules do not determine retention of Firebase Analytics, store purchase records or copies held by an app you choose for sharing. No fixed server-side retention period for those services is established in the reviewed app code. If a future Live archive is offered, its retention period and deletion process must be disclosed before you enable it. Support and purchase records may need to be kept where legally required; any applicable reason and retention period should be explained when responding to a deletion request.

To request access or deletion of information held by NecroTube, contact the email above with enough information to identify your request and relevant account or session. We may ask for proportionate identity verification. Do not send passwords or tokens. We will address requests within applicable legal deadlines and explain any lawful limits. For media stored only on your device, use local deletion controls; for platform-hosted copies, also use that platform's controls.

14. Security and international users

Safeguards should be proportionate to the information processed and include access restrictions and secure transmission for online services. No storage system, device or network can be guaranteed completely secure. Protect your device and connected accounts and report suspected unauthorized use using the contact details above.

Depending on the providers and destinations used, information may be processed outside your province, state or country, where privacy laws differ. Where legally required, appropriate transfer safeguards must be used. International use does not waive mandatory privacy protections in your country.

15. Children’s privacy and your rights

NecroTube is not directed to children under 13, or a higher minimum age where local law requires it, and should not knowingly collect their personal information. A parent or guardian who believes a child has provided information should contact us so it can be investigated and removed where required. Social and Live platforms may impose higher age requirements.

Depending on your location, you may have rights to access, correct, delete or obtain a copy of your information, restrict or object to processing, withdraw consent and complain to a privacy regulator. Withdrawing consent does not affect prior lawful processing. Exercise rights using the contact details above; mandatory rights apply regardless of the wording of this policy.

16. Changes and contact

We may update this policy as the app, providers or applicable requirements change. The date above identifies the latest revision. Material changes require appropriate notice and, where necessary, renewed consent before new processing begins. Planned-feature descriptions do not replace the disclosures required when those features launch.

For privacy questions, deletion requests or concerns about a recording, contact:

Developer/operator: Cortical Labs
Contact email: corticalabs@yahoo.com