Privacy Policy

Information used by the service

Account and organization information can include your email, membership role, location details, screen names and group assignments. The service also processes uploaded media, playlist choices, ad settings and schedules that you provide.

Device records can include installation and device identifiers, pairing or activation records, software capabilities, heartbeat/connectivity status, delivery state and playback-event metadata. Technical request identifiers, source-address information and security/audit records support operation and abuse prevention.

Public contact and account setup forms collect the name, email, business details, optional phone number and message you submit. An account setup request does not itself create an account or activate a trial.

Why information is processed

Information is used to authenticate accounts, enforce organization permissions, pair screens, prepare and deliver content, evaluate schedules, report device activity, troubleshoot issues and respond to requests. Playback reporting concerns device activity; it is not a system for identifying the people who view a screen.

Camera and permissions

With your permission, the mobile app uses the camera to read a TV's public pairing or maintenance QR code. The current app does not intentionally save camera frames or upload a camera video feed. The current setup flow also offers manual pairing-code entry.

The current app does not request microphone, contacts or GPS access for this setup flow. You can manage camera permission in your device settings; disabling it does not prevent manual code entry.

Cookies and local storage

The web panel uses session and CSRF cookies for sign-in and request protection. The mobile client keeps session cookies in memory and locks private screens when it is backgrounded. The TV player stores protected credentials, verified media and operational/playback records locally to support offline operation.

Public form details are sent to the server when you submit them. An unconfirmed request is held in the current page's memory for exact retry; it is not presented as a completed registration or email delivery.

Access and service providers

Organization access follows authenticated membership and action permissions. Public visitors cannot list private account data or contact enquiries. The present app does not include third-party advertising-tracker or data-broker integrations.

Hosting, object storage, connectivity and other service infrastructure can process information needed to provide the service. Production provider names, hosting locations and any transfer arrangements need to be documented by the confirmed operator before the final notice is adopted.

Retention and deletion

Retention depends on the information involved, active account/content references, operational history and backup requirements. Removing an ad placement or screen does not automatically erase its media, historical records or every offline copy. Final retention schedules and backup-deletion arrangements still require operator review.

Contact contact@skydivine.in to request access, correction, deletion or information about your data. Identity and organization authority may need to be verified, and any information that must be retained should be explained in the response. The current app does not provide automatic account deletion.

Security and sensitive information

The service uses authenticated requests, organization/action permissions, protected TV credentials and verified media activation. These measures do not establish an absolute security guarantee. Avoid including passwords, payment-card information or unnecessary sensitive personal information in contact messages or display content.

Signova Hub is designed for business display management rather than a child-directed service. Check with the operator before using it for workflows involving children's or other sensitive personal information.

Contact and updates

For privacy questions or requests, email contact@skydivine.in or call +91 89830 01321. The update date above identifies this content version. This draft requires operator and legal review; it is not a statement that all deployment-specific privacy requirements have been met.