SchemeClock

Privacy notice

Last updated

SchemeClock is a tracker for Indian electronics registrations under BIS CRS, WPC ETA and TEC MTCTE. It is run by Harsh Thakar. This notice says what information it keeps, why, who else handles it, and what you can ask for. Questions go to schemeclock.hq@gmail.com.

What we keep

  • Your account: your email address and a password. The password is stored only as a one-way hash by our sign-in provider; we never see it.
  • Your organisation's records: what you and your colleagues enter. That means model names, SKUs, manufacturers, factories, authorised Indian representatives, critical components, applications and their stage history, registration numbers, grant and expiry dates, and notes.
  • Invitations: the email address of anyone invited to your organisation, so the invitation can be sent and accepted.
  • Visit counts: for the pages anyone can read without an account, which public page was opened and when. No IP address is stored with it, and nothing that says who you are. If you allowed the visitor cookie described below, its random number is stored with the visit, so one returning browser is counted once. Pages you see after signing in are not counted.
  • An address you leave for updates: if you type your email into the invitation on a public page, we keep that address and when you left it, so we can write to you. It is not linked to which pages you read or to the visitor cookie.
  • Operational logs: our hosting providers keep technical logs, which can include IP addresses, to run and secure the service.

We do not ask for or store payment details, government ID numbers or uploaded documents.

What we use it for

  • To run the service: showing your records to the people in your organisation.
  • To send the emails the service exists for: sign-in and invitation emails, and renewal reminders 180, 90, 30 and 7 days before a registration expires. Reminders go to owners and members of the organisation, not to viewers.
  • To answer you when you write to us, including feedback you send.
  • To fix problems and keep the service secure.
  • To know how many people read the public pages, and which ones.
  • To tell people about the service: if you allowed the visitor cookie and come back a few times, the site offers you an account or updates by email, once. We write only to addresses people gave us for that, a few times a year, and every email has a link that stops them.

We do not sell your information, show advertising, or use your records to train AI models.

Who can see it

  • People in your organisation, according to the role an owner gives them. Each organisation's records are separated in the database itself, so one organisation cannot read another's.
  • Harsh Thakar, who runs the service and can access the database to operate and repair it. We look at an organisation's records only to fix a problem, to answer a request from that organisation, or where the law requires it.
  • Service providers who host or deliver the service for us, and use your information only for that:
    • Amazon Web Services, which runs the application server, in Mumbai.
    • Supabase, which provides the database and sign-in, in Mumbai.
    • Resend, which delivers our emails and may process email addresses and email contents outside India.

We will disclose information to an authority only where the law requires it.

Cookies

The cookies the service needs to do what you ask of it, and two more only if you allow them. Nothing from another company is loaded into the pages, and no cookie here is shared with or sold to anyone, advertisers included.

  • Sign-in (names beginning sb-): keeps you signed in. Removed when you sign out; otherwise it lasts at most 400 days.
  • Organisation (active_org): remembers which organisation you last had open. Lasts one year.
  • Appearance (theme): set only if you choose Light or Dark in Settings, and removed if you go back to System. Lasts one year.
  • Your answer about visit counting (visit_consent): remembers whether you allowed the visitor cookie or said no, so you are asked once and not on every page. Lasts one year.
  • Visitor (visitor_id): set only if you allow it. A random number that says nothing about you, used to count one returning browser as one visitor. Lasts one year, and is removed as soon as you change your answer to no. Visits already counted keep the number, which from then on matches no cookie anywhere.
  • Visit count (visit_count): set only if you allow it. How many times this browser has come to the public pages and when it last did, kept in the cookie and not on our servers. On a third visit it brings up the offer of an account or updates by email, once. Lasts one year, and is removed as soon as you change your answer to no.

You have not answered about the visitor cookie on this browser. You can change that here at any time:

How we protect it

  • Every connection is encrypted: between your browser and the site, and between the site and the database.
  • Each organisation's records are separated by rules inside the database, not only by the app, so a fault in one page cannot show one organisation another's records.
  • Passwords are stored only as one-way hashes, by our sign-in provider.
  • Access to the servers is limited to Harsh Thakar, by key rather than password.

No system is perfectly secure. If a breach affects your information, we will tell you.

How long we keep it

For as long as your organisation's account is open. Stage history and registrations are kept rather than overwritten while it is open, because a record of what happened and when is part of what the service is for.

If you ask us to close your organisation's account, we delete its records within 30 days, except anything we are required by law to keep. Copies inside our providers' backups are removed when those backups expire.

What you can ask for

You can ask for a copy of your information, for it to be corrected, or for it to be deleted, and you can raise a complaint about how it has been handled. Write to schemeclock.hq@gmail.com. We will reply within 30 days. Most of your organisation's records can also be corrected directly in the app by an owner or member.

Grievance officer

Harsh Thakar, schemeclock.hq@gmail.com. Any complaint about how your information is handled is answered within 30 days.

Children

SchemeClock is a business tool and is not meant for anyone under 18.

Changes

If this notice changes in a way that matters, we will email account holders before the change applies, and the date at the top will change. The terms of use cover the rest of how the service works.

We count visits to these pages. If you allow it, one cookie lets us count a returning visitor once instead of every time, and, if you come back a few times, offer you an account or updates by email. We only write to people who give us their address, and nothing is shared with anyone. What we keep