Back to Home

Data Compliance Policy

Version 2.0 | Effective Date: April 1, 2026 | Last Updated: March 2026


1. Overview

KnitTrace is a B2B SaaS platform for the Indian textile industry, operated by Time In Software. This document defines how we collect, process, store, and protect user data in compliance with India's data privacy regulations. It supplements our Privacy Policy with technical and regulatory detail.

Applicable Regulation

CountryRegulationKey Requirements
IndiaDigital Personal Data Protection Act (DPDPA) 2023Consent, data localization, breach notification 72 hrs

2. Data We Collect

2.1 Categories of Personal Data

CategoryData FieldsPurposeLegal Basis
Account DataFull name, email, password (hashed via bcrypt)Account creation, authenticationContract performance
Business DataCompany name, GST/Tax ID, address, phone, contact email, business type, verification tierCompany onboarding, identity verification, tax complianceContract performance + Legal obligation
Configuration DataTop role, knitting types, production modes, billing period preferenceService configuration, subscription managementContract performance
Production DataOrder details, quantities, timestamps, stage logs, machine assignmentsCore traceability serviceContract performance
Location DataFactory lat/lng (production units)Factory mappingLegitimate interest + Consent
Financial DataSubscription plan, billing period, billing history, payment transaction IDs, Razorpay subscription IDBilling and subscription managementContract performance
Communication DataChat messages, RFQ content, support ticketsP2P messaging, marketplace, supportContract performance
Usage DataActivity logs, login timestamps, IP addresses, device infoSecurity monitoring, anomaly detectionLegitimate interest
Media DataCompany logos, gallery photos, garment images, DC imagesProduct showcasing, document verificationContract performance

2.2 Data We Do NOT Collect

  • Credit card numbers or bank account details (handled entirely by Razorpay/Stripe)
  • Biometric data
  • Personal health data
  • Political or religious affiliation
  • Data from minors (platform is B2B, 18+ only)

3. How We Use Data

PurposeData UsedRetention
Provide traceability serviceProduction data, order dataDuration of account + 7 years (tax compliance)
Authenticate usersAccount dataDuration of account
Process paymentsFinancial data (transaction IDs only)7 years (tax/accounting compliance)
Manage subscriptions & trialsPlan selection, billing period, trial dates, Razorpay subscription IDDuration of account + 7 years
Textile Passport (public)Aggregated journey data, company names, city namesIndefinite (public document)
Smart notificationsCompany capabilities, RFQ criteriaReal-time (not stored)
Security monitoringActivity logs, IP addresses, device fingerprints1 year
Customer supportSupport tickets, chat historyDuration of account + 1 year
Analytics (aggregated)Production volumes, marketplace trendsIndefinite (anonymised)

4. Data Storage & Security

4.1 Where Data is Stored

ComponentProviderRegionEncryption
Primary DatabaseSupabase (AWS)Mumbai, India (ap-south-1)AES-256 at rest, TLS in transit
File StorageSupabase Storage (AWS S3)Mumbai, IndiaAES-256 at rest, TLS in transit
CachingUpstash RedisMumbai, IndiaTLS in transit
CDNVercel Edge NetworkGlobal (edge nodes)TLS in transit
Payment ProcessingRazorpay (India) / Stripe (Global)India / USPCI-DSS Level 1
EmailResend (AWS SES)USTLS in transit

4.2 Security Measures

MeasureImplementation
Encryption at restAES-256 (Supabase/AWS default)
Encryption in transitTLS 1.3 (all connections)
Field-level encryptionpgcrypto on GST numbers, phone numbers, emails
Access controlRow Level Security (RLS) on all 24 database tables
AuthenticationSupabase Auth with bcrypt password hashing
Two-Factor AuthTOTP (mandatory for Admin, optional for Exporter/VI)
Session managementSingle active session per user, 30-min timeout for sensitive roles
Input validationZod schema validation on all inputs
Rate limitingVercel Edge Middleware (100 req/min per IP)
DDoS protectionCloudflare (volumetric attack absorption)
File scanningMagic byte validation on all uploads
Audit trailImmutable activity_logs (append-only, no UPDATE/DELETE)
Anomaly detectionFlags suspicious login patterns, bulk exports, rapid API calls
API key rotationQuarterly rotation of Supabase keys
Webhook verificationCryptographic signature validation (Razorpay/Stripe)
BackupDaily automated backups (7-day retention)

5. Data Transfers

All primary data is stored in India. Limited data is transferred to third-party service providers as described below.

From > ToMechanismCompliance
India > IndiaNo transfer (primary data stays in Mumbai)DPDPA compliant
India > USLimited: only email delivery (Resend) and payment processing (Stripe)Standard contractual terms

5.1 Data Localization

All data is stored in the Mumbai, India region (ap-south-1), ensuring compliance with India's DPDPA data localization requirements.


6. User Rights

6.1 Rights Available to All Users

RightDescriptionHow to ExerciseResponse Time
AccessRequest a copy of all personal data we holdSettings > Privacy > Download My Data30 days
RectificationCorrect inaccurate personal dataEdit Profile / Company SettingsImmediate
ErasureDelete account and all personal dataSettings > Privacy > Delete Account30 days
Data PortabilityExport data in JSON/CSVSettings > Privacy > Export Data30 days
RestrictionRestrict processing of personal dataEmail timeinsoftware@gmail.com30 days
ObjectionObject to processing based on legitimate interestEmail timeinsoftware@gmail.com30 days
Withdraw ConsentRevoke previously given consentSettings > Privacy > Manage ConsentImmediate

6.2 Additional Rights (India — DPDPA)

Right to nominate — designate a person to exercise your data rights in case of death or incapacity.


7. Data Retention & Deletion

7.1 Retention Schedule

Data TypeRetention PeriodReasonDeletion Method
Account dataDuration of accountService provisionHard delete on account deletion
Business/company dataDuration of accountService provisionHard delete on account deletion
Production logs7 years after order completionTax/legal compliance (India GST Act)Auto-delete after 7 years
Activity logs1 yearSecurity audit trailAuto-archive, then delete
Chat messagesDuration of accountCommunication recordHard delete on account deletion
Financial/billing records7 yearsTax/accounting complianceAuto-delete after 7 years
Textile PassportsIndefinite (public documents)End-consumer transparencyAnonymise company names on account deletion
Support ticketsDuration of account + 1 yearSupport historyHard delete
Media/filesDuration of accountService provisionHard delete from Supabase Storage

7.2 Account Deletion Process

  1. User initiates deletion via Settings > Privacy > Delete Account.
  2. 30-day cooling-off period begins. Account is deactivated, data preserved.
  3. User can cancel deletion during the cooling-off period.
  4. After 30 days:
    • Delete: profiles, company galleries, chat messages, support tickets, uploaded media
    • Anonymise: orders (company name replaced with “Deleted Company”), production logs
    • Retain (anonymised): Textile Passports, activity logs (legal requirement)
    • Revoke: all auth sessions and API tokens
  5. Confirmation email sent to registered email.
  6. Data is irrecoverable after this point.

Restriction: If the user is the sole owner of a company with active subscriptions or pending orders, deletion is blocked until ownership is transferred or orders are completed. Yearly plan financial obligations (see Terms of Service Section 5.2) remain in effect regardless of account deletion.

7.3 Subscription Expiry Data Handling

  • If a subscription enters “halted” status due to payment failure, data is retained for 30 days.
  • After 30 days without payment resolution, we reserve the right to delete account data with prior email notice.

8. Consent Management

ActionConsent TypeRequiredRevocable
Account creationTerms of Service + Privacy PolicyYes (mandatory)Deleting account
Factory location pin (Google Maps)Location data consentNo (optional)Yes (clear lat/lng)
Marketing emailsEmail marketing consentNo (opt-in)Yes (unsubscribe link)
Analytics cookiesCookie consentNo (opt-in for EU)Yes (cookie settings)
Textile Passport (public)Public data consentYes (per passport)Yes (toggle is_public off)

9. Third-Party Data Sharing

9.1 Sub-Processors

Sub-ProcessorData SharedPurposeDPA in Place
Supabase (AWS)All dataDatabase, auth, storage, realtimeYes
VercelRequest logs, IP addressesHosting, CDN, Edge FunctionsYes
CloudflareIP addresses, request headersDDoS protection, DNS, TurnstileYes
UpstashCached query results (no PII)Redis cachingYes
RazorpayTransaction IDs, company namesIndia payment processingYes
StripeTransaction IDs, company namesInternational payment processingYes
Resend (AWS SES)Email addresses, email contentTransactional emailsYes
GSTZenGST numbersGSTIN validation (India only)Yes
Google MapsLat/lng coordinates, addressesPlaces Autocomplete, DirectionsYes

9.2 Data We Never Share

  • We never sell personal data to third parties.
  • We never share production data between competing companies.
  • We never provide bulk data access to advertisers.
  • We never share individual user behaviour with analytics platforms (only aggregated).

10. Breach Notification

10.1 Notification Timeline (India — DPDPA)

  • Authority notification: Within 72 hours to the Data Protection Board of India.
  • User notification: Without undue delay via email.

10.2 Breach Response Process

  1. Detection — Anomaly detection system flags suspicious activity, or security team discovers breach manually.
  2. Containment (within 1 hour) — Isolate affected systems, revoke compromised credentials, enable Cloudflare “Under Attack” mode if needed.
  3. Assessment (within 24 hours) — Determine scope, identify affected users and regions, assess risk level.
  4. Notification (within 72 hours) — Notify relevant data protection authorities. Notify affected users via email.
  5. Remediation — Fix the vulnerability, enhance monitoring, update security measures.
  6. Post-Mortem (within 7 days) — Document incident, root cause analysis, preventive measures, update this policy if needed.

11. Cookie Policy

CookieTypePurposeDurationConsent Required
sb-access-tokenEssentialSupabase auth sessionSessionNo (essential)
sb-refresh-tokenEssentialSupabase auth refresh7 daysNo (essential)
themeFunctionalLight/Dark mode preference1 yearNo (functional)
cf_clearanceEssentialCloudflare Turnstile bot check30 minNo (security)

KnitTrace does not use advertising cookies, tracking pixels, or third-party analytics cookies.


12. Children's Privacy

KnitTrace is a B2B platform designed for business use only. We do not knowingly collect data from anyone under 18 years of age. If we discover that a minor has created an account, we will immediately delete it and all associated data.


13. Policy Updates

  • This policy is reviewed quarterly and updated as needed.
  • Material changes are communicated via email to all registered users 30 days before taking effect.
  • Continued use of the platform after the effective date constitutes acceptance.
  • Previous versions are archived and available upon request.

14. Contact

For all compliance, privacy, and security inquiries:

Email: timeinsoftware@gmail.com

Phone: +91 88708 72911

Registered Address:
Time In Software
B2, 4F1, Parsn Antara, Nanjundapuram Road,
Ramanthapuram, Coimbatore, Tamil Nadu, 641036
India

Website: timeinsoftware.com