Privacy & Telemetry Architecture
Engineered transparency, zero third-party surveillance, and mathematical guarantees of visitor anonymity.
Architecture at a Glance
Most privacy policies are lengthy legal shields designed to excuse invasive tracking. This document describes the architectural controls engineered directly into our codebase to make user surveillance technically impossible.
Zero Ad Trackers
No Meta Pixel, Google Ads, TikTok beacons, or marketing scripts. We do not track you across the web or monetize your behavior.
Daily SHA-256 Salt
Raw IP addresses are never written to disk or database. Every IP is salted with the current calendar date and hashed, unlinking records every 24h.
No Cookie Banner Needed
100% compliant with the ePrivacy Directive and GDPR Recital 30. We only use strictly functional preference cookies (theme, audience, region).
Zero-Knowledge Payments
Invoicing and payments execute directly via Razorpay's PCI-DSS Level 1 vault. We never intercept, transmit, or store card or UPI numbers.
PostgreSQL RLS Isolation
Client workspaces and Retriever RAG embeddings are isolated via Row-Level Security (RLS). Cross-tenant queries are blocked at the database engine level.
Automated 90-Day Purge
Anonymous telemetry visits are automatically evicted from Supabase storage after 90 days by probabilistic database maintenance triggers.
Foundational Commitment & Scope
This Privacy & Telemetry Architecture governs the digital properties operated by Prateek Sharma (trading as Prateeq Studio), including:
- Portfolio & Engineering Lab:
https://prateeq.in - Project Scoping Lab & Instant Quote Engine:
https://prateeq.in/scoping - Client Workspace & Dashboard:
https://prateeq.in/dashboard - Interactive Diagnostics Terminal:
https://prateeq.in/terminal - Retriever AI SaaS Engine & Admin Studio:
https://rag.prateeq.in&https://admin.rag.prateeq.in
Our foundational design principle is Privacy by Architecture: we minimize data ingestion at the network perimeter, enforce mathematical irreversibility on analytics data, and eliminate cross-site tracking entirely.
Edge Telemetry & Cryptographic Anonymization
To monitor site availability, prevent distributed denial-of-service (DDoS) attacks, detect malicious scanning probes, and evaluate real-world performance, requests are processed server-side via Next.js proxy middleware (src/proxy.ts).
src/lib/security.ts)Mathematical Guarantee: Because the salt rotates automatically at 00:00 UTC each day, the resulting hash rotates. It is mathematically impossible to correlate a visit made on Monday with a visit on Tuesday, eliminating persistent user tracking while maintaining accurate daily unique visitor counts.
Telemetry Fields Recorded vs. Deliberately Discarded
| Data Field | Action | Purpose & Engineering Rationale |
|---|---|---|
| Raw IP Address | Never Stored | Cryptographically hashed with rotating daily salt; raw IP discarded immediately. |
| Path Visited | Stored | Aggregated to identify high-traffic pages and broken 404 routes. |
| Country Code | Stored (Coarse) | Read from Vercel edge header (x-vercel-ip-country) to serve regional currency (INR/USD). |
| City & Sub-Region | Deliberately Discarded | Headers (x-vercel-ip-city, x-vercel-ip-country-region) are discarded and stored as null to prevent intrusive ISP geolocation. |
| Referrer URL | Sanitized Domain Only | Stripped down strictly to root hostname (url.hostname). Private paths, query tokens, and session IDs in referrers are destroyed before saving. |
| Device & Browser Engine | Stored | Coarse device type (desktop/mobile/tablet), OS family, and browser name to guide responsive CSS rendering budgets. |
| Exploits & Bot Probes | Bypassed & Discarded | Known vulnerability scans (.php, wp-admin, .env, actuator) and search crawlers are filtered before database writes. |
Public Transparency: You do not need to take our word for it. You can inspect live aggregate visitor numbers, country distributions, and device stats on our publicly accessible Telemetry Dashboard (/analytics) or by querying system-info in the Diagnostics Terminal (/terminal).
Contact Inquiries & Scoping Lab Submissions
When you submit a message through the contact form or configure a custom technical build in the Project Scoping Lab (/scoping), we collect only the information required to evaluate your requirements and generate an itemized quote:
- Identity & Contact: Full name, organizational email address, and optional phone number.
- Technical Specifications: Selected base engine (Landing, Multi-page, SaaS), architectural feature modules, brand asset selections, and ongoing maintenance tiers.
- Project Artifacts: Optional uploaded Request for Proposal (RFP) documents, design briefs, or inspiration links.
- Rate Limiting: Inbound contact submissions are limited to a maximum of 5 requests per 60 seconds per IP to mitigate spam flooding.
- Google reCAPTCHA v3: Submissions are score-evaluated server-side. Requests scoring below 0.3 are automatically rejected to block automated bots without forcing human visitors through friction-heavy puzzles.
- Encrypted Transmission: Messages and attached PDFs are transmitted via Resend's TLS-encrypted API directly to our administrative inbox (
notifications@prateeq.in). - Zero List-Selling: Your contact information is never added to automated marketing drip campaigns, shared with recruiters, or sold to third parties.
Client Workspace, Authentication & Razorpay Invoicing
Clients who engage Prateeq Studio for engineering advisory or custom software development access the private Client Workspace Dashboard (/dashboard).
Authentication Security
Workspace accounts authenticate using Google OAuth 2.0 PKCE via Supabase Auth. We receive and store only your verified Google email address, display name, and avatar picture URL. We never access your Google password, contacts, Google Drive files, or broader Google Account data.
Zero-Knowledge Financial Architecture (Razorpay)
When you pay milestone invoices, retainers, or SaaS subscriptions on prateeq.in, all financial transactions are processed directly by Razorpay Software Private Limited, an authorized payment aggregator compliant with Reserve Bank of India (RBI) mandates.
Payment credentials (credit/debit card numbers, CVVs, expiration dates, UPI PINs, netbanking passwords) are collected directly within Razorpay's PCI-DSS Level 1 compliant secure iframe. Prateeq Studio never touches, transmits, logs, or stores raw payment instrument data on any server.
Accounting & Tax Compliance Data: Under Indian tax regulations (Goods and Services Tax Act) and SAC Code 998314 (Information Technology Software Consulting and Development Services), we are legally obligated to retain records of completed transactions, including:
- Invoice number, date of issue, and settlement timestamp.
- Client billing name, billing address, and GSTIN (for Indian commercial entities).
- Razorpay order ID, payment ID, and currency amount (INR or USD equivalent).
These commercial accounting records are retained for the statutory period of 7 years as mandated by law.
Retriever AI SaaS & Vector Data Isolation
Users and enterprise clients leveraging the Retriever Cognitive Engine (rag.prateeq.in) and its Web Admin Studio (admin.rag.prateeq.in) are protected by strict tenant boundary enforcement:
Strict Tenant RLS
Every document chunk, vector embedding, and chat thread is tagged with a cryptographically generated tenant_id. PostgreSQL Row-Level Security policies physically prevent cross-tenant vector leakage.
Zero Public Model Training
Uploaded enterprise knowledge, proprietary PDFs, and chat queries are never used to train, tune, or improve public foundation models (OpenAI, Anthropic, Gemini, or Ollama).
Local-First Embeddings
Embeddings run locally by default via self-hosted Ollama (nomic-embed-text) on our dedicated Oracle Cloud infrastructure, preventing vector data transmission to external APIs.
Immediate Tenant Purge
When a tenant deletes a document or tears down a workspace, all associated vector chunks and OCR text are immediately purged from database indexes.
Third-Party Sub-Processors Directory
We partner exclusively with enterprise infrastructure providers that meet rigorous security benchmarks (SOC 2 Type II, ISO 27001, and GDPR compliance):
| Sub-Processor | Role & Service | Data Transferred | Data Region | Privacy & Security |
|---|---|---|---|---|
| Supabase Inc. | Managed PostgreSQL Database, Auth & Storage | Encrypted client scopes, telemetry hashes, auth sessions | AWS Global (ap-south-1 / us-east-1) | Supabase Privacy |
| Vercel Inc. | Edge CDN, Next.js Hosting & Cookieless Web Analytics | Incoming HTTP headers, edge routing requests | Global Edge Network | Vercel Privacy |
| Resend Inc. | Transactional Email Delivery | Contact form messages, inbound client briefs | United States (AWS) | Resend Privacy |
| Razorpay Software Pvt. Ltd. | Payment Gateway & Billing Settlement | Payment instrument tokens, invoice settlements | India (RBI Regulated) | Razorpay Privacy |
| Google LLC | reCAPTCHA v3 & OAuth Authentication | Client IP (transient), OAuth user profile | Global | Google Privacy |
| Oracle Cloud Infrastructure | Dedicated VPS Hosting for Retriever Engine | Encrypted pgvector database, local Ollama embeddings | India / Singapore | Oracle Privacy |
Legal Bases for Data Processing
Under Article 6 of the General Data Protection Regulation (GDPR) and Section 4 of the Digital Personal Data Protection Act (DPDP Act 2023), our processing activities are grounded on clear statutory legal bases:
- Legitimate Interests (Art. 6(1)(f) GDPR): Operating server-side anonymous telemetry, detecting honeypot attacks and unauthorized scraping, measuring performance budgets, and maintaining server stability.
- Performance of a Contract (Art. 6(1)(b) GDPR): Authenticating client workspace accounts, generating tailored engineering proposals in the Scoping Lab, delivering technical milestone deliverables, and processing invoices.
- Explicit Consent (Art. 6(1)(a) GDPR): When you voluntarily submit personal information through the contact form or opt into email correspondence.
- Legal & Statutory Obligation (Art. 6(1)(c) GDPR): Retaining financial transaction ledgers, GST invoices, and settlement proofs for mandatory statutory audits.
Global Regulatory Compliance (GDPR, DPDP 2023, CCPA)
Regardless of your geographic location, we adhere to the world's strictest privacy protections:
Digital Personal Data Protection Act, 2023 (India)
Prateek Sharma acts as the Data Fiduciary under the DPDP Act 2023. We ensure that personal data is processed solely for lawful purposes for which you have provided consent or for legitimate uses recognized by the Act. Data Principals in India enjoy statutory rights of grievance redressal, correction, and erasure.
General Data Protection Regulation (EU / UK GDPR)
European Union and United Kingdom visitors enjoy full data protection rights, including the right not to be subjected to automated profiling, the right to data portability, and the right to lodge complaints with a supervisory authority (such as the DPC in Ireland or the ICO in the UK).
California Consumer Privacy Act (CCPA / CPRA)
We do NOT sell personal information, nor do we share personal information for cross-context behavioral advertising. We have not sold or shared any consumer personal information in the preceding 12 months.
Your Rights & Data Erasure Protocol
You hold complete sovereignty over your data. You may exercise any of the following statutory rights at any time without fees or discrimination:
How to Exercise Your Rights
To submit an access, correction, or erasure request, send an email directly to the Data Controller. Please specify the email address used during your inquiry or client engagement. Requests are confirmed and fulfilled within 30 calendar days.
Submit Data Rights RequestTechnical & Engineering Security Controls
Security is enforced using defensive architectural controls rather than relying solely on administrative policies:
- Cryptographic Transport Security: Mandatory TLS 1.3 encryption across all public web and API endpoints, enforced by modern HSTS policies.
- Service Role Key Isolation: Privileged database credentials (
SUPABASE_SERVICE_ROLE_KEY) are strictly confined to server-side Node.js execution environments and are never shipped in client-side bundles. - Database Row-Level Security (RLS): Direct public anonymous write access to telemetry and intake tables is blocked at the database engine level.
- Input Sanitization: All user inputs across contact endpoints, terminal query parsers, and scoping wizards are sanitized against Cross-Site Scripting (XSS), SQL Injection, and CRLF injection.
Governance & Controller Contact Information
This policy is reviewed quarterly or upon the launch of new technical capabilities. Material revisions will be highlighted on this page with updated version numbers and change summaries.