thynkOS

Privacy Policy

Your privacy matters to us. Please read how we collect, use, and protect your information.

Who this notice covers

This notice is for thynkOS, provided on thynkOS. It describes the television account, device, subscription, and support records used to run the service. Notice version 2026-10-03.

Account notice

Notice version 2026-10-03.

A vendor may create the account so the television service can be activated. That basis is service provision. The customer is asked to accept this notice when signing in on the web.

Purposes

Create and run your TV account
Link devices, subscriptions, and support requests
Send service email, including a temporary password when one is issued

How long records are kept

Device analytics: 90 days.
Device graphs: 90 days.
Screenshots: 30 days.
TV events: 90 days.
Analytics backup files: 7 days.
Account and device inventory rows stay while the service is active.

Children

A kids profile stores a display name and content limits, not a contact address. Consent is recorded only when a parent confirms it. Creating the profile without that confirmation does not count as consent.

Your rights

Download a copy of your personal data from the customer home page.
Erase your personal data from the customer home page. Your account and the device and finance rows linked only to you are removed. Other customers are not affected.
Ask the privacy contact to correct data or to raise a complaint.

If data is exposed

Stop the affected processor or mailbox.
Rotate the related key or password.
Email the privacy contact and the people whose data was involved.
Keep the security log entry for the event.

Questions go to Privacy contact at no-reply@thynkos.in.

Information we keep

Account name and email. Email stays readable because sign-in and vendor search use it.
Phone, street address, and pincode on the customer record. Those fields are encrypted.
City, which the service can use for location features such as weather.
Device MAC address, serial number, and service location on the device record. Those identify the box for inventory and activation. Phone, street address, and pincode are not copied into the device login payload.
Subscription invoices, including the account email and billed amounts.
Support tickets. An erase request blanks the personal fields on tickets linked to that customer.
A kids profile stores a display name and content limits, not a contact address.

Cookies

The site stores a sign-in cookie so the portal can keep you logged in. It is not used for advertising. The cookie is httpOnly and SameSite=Lax. It is marked Secure only when the site is served over HTTPS.

How to reach us

Privacy questions go to Privacy contact at no-reply@thynkos.in. You can also email thynkOS at no-reply@thynkos.in. You can also download or erase your data from the customer home page.

The services that receive data are listed below.

Platform processors

thynkOS sends the data below to these services. To report a breach or ask for erasure, email no-reply@thynkos.in.

Firebase Cloud Messaging

Purpose. Deliver push messages to a registered device.

Data. Device push token, notification title, and notification body.

Transfer. The token is sent to Google when a push is dispatched.

Breach. Revoke the Firebase service account, issue a new one, and email the grievance contact.

Stripe

Purpose. Record subscription invoices for the customer account.

Data. Invoice body, including the account email and billed amounts.

Transfer. Invoice payloads arrive from Stripe and are stored in the private webhook log.

Breach. Stop the webhook, rotate the Stripe secret if one is configured, and email the grievance contact.

Mail host (smtp-relay.brevo.com)

Purpose. Send account, password, and service email.

Data. Recipient name, email address, and the message body.

Transfer. Messages are submitted to the configured SMTP host.

Breach. Pause outbound mail, rotate the mailbox password, and email the grievance contact.