Our Privacy Policy describes what happens to your data. This page states the rules we hold ourselves to when we handle it — the commitments, not just the disclosures.
1. Five principles
- Collect less. We ask for a field only when something breaks without it. We do not collect gender, income, marital status, occupation, or any other profiling attribute, because none of them is needed to sell a shirt.
- Say what we take. Every category we store is named in the Privacy Policy, including the ones that are inconvenient to admit — the browser identifier, the truncated IP, the city.
- Never sell. Personal data is not a revenue line at STEM and never will be.
- Ask before tracking. Analytics are off until you accept them. Declining costs you nothing and hides nothing from you.
- Delete on request. One click in your account, no retention team, no exit survey, no dark pattern.
2. Our lawful basis for each purpose
| What we do | Basis |
|---|---|
| Taking, fulfilling and delivering your order | Performance of a contract |
| Invoices and tax records | Legal obligation |
| Account creation and sign-in | Performance of a contract |
| Website analytics | Your consent — withdrawable at any time |
| Newsletter and marketing | Your consent — double opt-in, one-click unsubscribe |
| Fraud prevention and site security | Legitimate interest |
| Responding to your support message | Legitimate interest |
3. How the data is protected
- Encrypted in transit. The site is HTTPS-only; there is no unencrypted route to it.
- Encrypted at rest. Our database and backups are encrypted by the provider.
- Row-level security. Access rules are enforced in the database itself, not only in application code, so a bug in a page cannot expose another customer's row.
- Passwords are hashed and cannot be read back by us or by anyone with database access.
- Separate admin surface. The admin panel is on its own hostname behind an additional identity gate, so a flaw in the shop cannot reach it.
- Least privilege. Integration credentials are scoped to exactly one job — our email sender, for instance, can send from two named addresses and do nothing else.
- Daily encrypted backups of schema and data, held in the Mumbai region.
- Audit log. Administrative actions on customer records are recorded.
4. Minimisation in practice
Three concrete examples, so this is checkable rather than decorative:
- We truncate your IP address before storing it. The last block is discarded at the moment of writing, so the full address never lands in our database.
- We do not store precise location. Our analytics table has latitude and longitude columns from an earlier design. They are deliberately left empty; no code writes to them, and we intend to drop them.
- We do not store card details. Not truncated, not tokenised, not at all. The payment gateway handles the card and returns us a result.
5. Retention, stated as periods
| Data | Kept for |
|---|---|
| Orders, invoices, payment references | 8 years (statutory) |
| Account and profile | Until you delete it |
| Analytics events | 24 months |
| Support messages | 24 months |
| Marketing consent records | Until withdrawn, plus 3 years as proof of consent |
| Deleted accounts | Purged after a 24-hour grace period |
6. If something goes wrong
If we discover a breach affecting personal data, we will notify the Data Protection Board of India as the DPDP Act requires, and tell affected customers directly — what happened, what data, what we have done, and what you should do. We will not wait to have a complete picture before telling you something has happened.
7. Sub-processors
The current list is in section 4 of the Privacy Policy. We do not add a processor that receives personal data without updating that list first.
8. Holding us to this
Write to our Grievance Officer, Nayak Kamal, at [email protected]. If we do not resolve your complaint, you may escalate to the Data Protection Board of India, and — if you are in the EU or UK — to your national supervisory authority.