Legal
Privacy policy.
What Infotech.Works collects when you use this site or the ScreenQube platform, why, and what happens to it.
Who we are. ScreenQube is a digital signage platform built and operated by Infotech.Works, a software engineering company based in Pune, Maharashtra, India. Where this policy says "we", "us" or "our", it means Infotech.Works. Where it says "the platform" or "ScreenQube", it means the ScreenQube console, the Android player application and this website together.
- Registered entity: registered legal name, company registration number and GSTIN pending
- Address: Iris, Laxman Nagar, Balewadi, Pune, Maharashtra 411045, India
- Contact: contact@infotech.works
- Applies to: visitors to this website, people who contact us through it, and organisations and users of the ScreenQube platform
We are a Data Fiduciary under India's Digital Personal Data Protection Act, 2023 for the data described in section 2, and we handle personal data in line with that Act and the Information Technology Act, 2000 and its Reasonable Security Practices rules. Where a visitor is in the EEA or the UK, we also honour the rights the GDPR gives them.
1. Two roles, and the partner in between
ScreenQube is sold and supported through partners. That changes who is answerable for your data, so it is the first thing this policy states rather than a footnote.
- We are the Data Fiduciary for people who visit this website, send us an enquiry, apply to become a partner, or hold a login to the ScreenQube console. This policy governs that data.
- Your partner is normally the Data Fiduciary for the organisation account they sell you. They set your plan, hold the commercial relationship and decide who in your organisation gets access.
- We are a Data Processor for the content you publish to your own screens — images, video, menus, rosters, anything you upload. We hold and transmit it to run the service; we do not decide what is in it. That processing is governed by your contract and by our data processing addendum, not by this policy.
If your screens display personal data — a visitor's name on a welcome board, a photograph of staff, a queue token tied to a person — you are responsible for having a lawful basis for it and for telling those people. We cannot do that on your behalf, because we cannot see what your content means.
2. What we collect, and why
Everything below is collected because you typed it into a form or because the service cannot run without it. There is no profiling, no enrichment from third-party data brokers, and no advertising use of any of it.
| Data | Where from | Why | Ground |
|---|---|---|---|
| Contact details | Name, work email, company, phone and country, typed into the contact, support, hardware or partner forms | To answer you, and to route you to the partner who covers your region | Your consent, given by submitting the form |
| What you asked about | The topic, message, fleet size, venue type or fault description you write | So the person who picks it up can answer without asking you again | Consent |
| Submission context | The page you submitted from, the referring URL, your browser locale and a timestamp | Operational routing — it tells us which partner should receive the enquiry and which page prompted it | Legitimate business need. No cookie and no identifier are involved, and this is not used to build a profile |
| Account and login | Name, email and a hashed password, held by the ScreenQube console | To create and secure your account and authenticate you | Performance of your contract |
| Screen and player data | Device registration code, online/offline state, last-seen time, screenshot on request, facility name, orientation | To show you whether your screens are working and to let you fix them remotely | Performance of your contract |
| Your content | Media and playlists you upload to your own account | To store, schedule and play it on your screens | Processed on your instruction — see section 1 |
| Billing | Billing contact and transaction records | Invoicing, tax and accounting | Contract and legal obligation. Card details are handled by Stripe and never reach us |
| Consent choice | One cookie, set only after you answer the notice | To remember your answer so we stop asking | Strictly necessary — it exists only to record a refusal or an agreement |
3. What this website does not do
This is unusually short for a privacy policy, and it is the section worth checking against the page source rather than taking on trust.
- No analytics. No Google Analytics, no Plausible, no heatmaps, no session recording. We do not know which pages you read.
- No advertising or tracking pixels. No Meta pixel, no LinkedIn Insight tag, no remarketing of any kind.
- No third-party scripts at all on the marketing pages.
- Typefaces are served from this domain, not from Google Fonts. Loading a font from a CDN discloses your IP address to that CDN before you have agreed to anything; self-hosting means no request leaves this origin as the page loads.
- We do not sell personal data, and we do not share it for cross-context behavioural advertising.
- No dark patterns in the consent notice. Refusing is one click, styled identically to accepting, and nothing optional runs until you answer either way.
4. Cookies
This website sets no cookies. Not analytics cookies, not advertising cookies, and not a consent cookie either — there is nothing to consent to, so you are not asked. No local storage is used to identify you and no fingerprinting of any kind is attempted.
That is a deliberate position rather than an oversight, and the consent machinery is built and switched off rather than absent: if a tag is ever added it will sit behind a notice and will not run until you allow it, and this section will be rewritten before that happens. The ScreenQube console you sign into is a separate application and sets its own session cookie, which is what keeps you signed in there.
5. The partner application form
The Register buttons open an application form that is hosted on the ScreenQube console, not on this website. It is embedded in a frame, so it looks like part of this page, but what you type there is submitted to the console and handled under this policy as account data rather than as a website enquiry. This site does not read, store or intercept it.
6. Who we share it with
- The partner who covers your region. If you ask to be introduced, or ask about buying, your enquiry goes to a partner so they can answer it. That is the point of the enquiry, and it is the main disclosure this policy makes.
- Stripe, for payments. Card details go to Stripe directly and are not stored by us.
- Service providers who host and run the platform, under contract and confidentiality. The current list is published at sub-processors, where only Stripe is confirmed so far.
- Authorities and advisers, where the law requires it or to establish or defend a legal claim.
- A buyer, if the business or the product is ever sold or reorganised. This policy travels with the data.
That is the whole list. We do not pass personal data to anyone else, and we do not licence it for any purpose of theirs.
7. Where it is held, and for how long
We are an Indian company and the platform is operated from India. Where a service provider processes data outside India, we require contractual protection at least equivalent to what this policy promises; for transfers out of the EEA or the UK we rely on the European Commission's standard contractual clauses.
Retention periods have not been set yet. The principle we will hold to is that an enquiry is kept only while it is live and for as long as we must keep a record of it, account data for the life of the account plus the statutory tax and accounting period, and content you upload until you or your partner delete it. The exact figures will be published here rather than left to judgement.
8. Your rights
Under the Digital Personal Data Protection Act, 2023 you may ask us to:
- confirm what personal data of yours we hold, and give you a summary of it;
- correct, complete or update anything inaccurate;
- erase it, where we are not required to keep it;
- hear a grievance, through the officer named in section 10;
- nominate someone to exercise these rights for you if you die or become incapable.
Where you gave consent, you can withdraw it at any time and we will stop the processing that relied on it — that may mean we can no longer answer an open enquiry. If you are in the EEA or the UK, you additionally have the GDPR rights of access, rectification, erasure, restriction, portability and objection, and you may complain to your supervisory authority.
Ask by writing to contact@infotech.works. We will respond within the period the law allows, and we will not treat you differently for asking.
9. Security, stated honestly
We use TLS in transit, hashed passwords, role-based access within the console and access control on the systems that hold customer data. The session that signs you in belongs to the console and is set as an HttpOnly cookie there — this website never reads or writes it, and stores no token that a script on the page could reach.
We hold no security certification and we are not claiming one. No ISO 27001, no SOC 2, no penetration test report we can show you. What is actually verifiable is set out on the security page, including the parts we could not evidence. No system is perfectly secure, and a policy that says otherwise is not worth reading.
10. Breaches, and who to complain to
If a breach affects your personal data we will notify the Data Protection Board of India, and you where the law requires it, without undue delay — telling you what happened, what data was involved and what we are doing about it.
Grievance Officer. No officer has been appointed and named yet; the Act requires one, and the name and direct address will be published here. Until then, write to contact@infotech.works marked for the attention of the Grievance Officer. If we do not resolve it, you may complain to the Data Protection Board of India.
11. Children
ScreenQube is a business product. We do not offer it to children and we do not knowingly collect the personal data of anyone under 18. If you believe a child has given us personal data, tell us and we will delete it.
12. Changes
If this policy changes we will post the new version here with a fresh date, and for anything material we will say so to account holders directly rather than relying on you noticing. A consent given against an older version is not consent for a materially different one, so where that happens we will ask again.