Privacy Policy
Version 8 · Last updated
TL;DR: No login is required to look up a parcel. Tracking numbers are used for the lookup and the cache, are excluded from analytics and advertising URLs, and are kept permanently (encrypted in operational logs). Google Analytics sets its _ga cookies (about 2 years) and AdSense may use Google's advertising cookies to personalise ads, with no consent prompt; Section 4 lists the opt-outs. Businesses using TrackParcel for Business should also read the business notice below.
1. Who We Are
TrackParcel (trackparcel.in) is a free, independent parcel tracking platform for India, and TrackParcel for Business (app.trackparcel.in) is its service for businesses. It is operated by Tejas Telkar and is not affiliated with any courier company. The legal entity's name and registered address are on our contact page. Our contact email is tejas.telkar [at] trackparcel.in, and privacy requests go to support [at] trackparcel.in.
2. What Data We Collect
TrackParcel is designed to minimise personal data.
Tracking queries: When you enter a tracking number, it is sent in a private POST request to our server, and our server then sends the tracking number to the selected courier, which is necessary to retrieve your tracking result. For one courier (Shree Anjani), the official tracker only supports plain HTTP, not encrypted HTTPS, so that carrier's docket number is sent to its own server without TLS in transit. Only if the operator explicitly enables an optional fallback, used when the official tracker is unreachable, will the tracking number instead be sent to an unaffiliated third-party data source for that carrier; this is separate from, and unrelated to, advertising. For one courier offered only through the TrackParcel API, when the carrier's own tracker cannot be read for a lookup (because it fails, times out or rate-limits us, or because our capacity to query it is momentarily used up and we have no earlier result to show), the tracking number is automatically sent to ParcelsApp, an unaffiliated tracking provider, to retrieve a fallback result. This API courier fallback does not require a separate user opt-in and is unrelated to advertising. The tracking number may be used as the key for a temporary private cache entry, but it is not attached to a TrackParcel account or placed in analytics or advertising page URLs. For troubleshooting and carrier-health diagnosis, operational scrape logs store the tracking number encrypted at rest and keep it permanently, as part of the permanent tracking record. It can be decrypted only in an authenticated administrator view. See Section 5 for cache duration.
Server and security logs: Infrastructure providers may process ordinary request metadata such as IP address, browser type, requested page and timestamp. TrackParcel's carrier-health logs do not store an IP address beside an encrypted tracking number, and they are kept permanently. A separate security-event log may retain an IP address for up to 365 days when automated abuse is detected; it does not contain tracking numbers.
Speed and error reports: One page load in ten, on this website and in the TrackParcel for Business app, sends our own server a report of how fast the page was, and every page of the app also reports any page errors; the reports send no cookies and no account or device identifier, and we keep only whether a report came from the website or the app, the kind of page (with tracking numbers, workspace names and every identifier removed), how the page was loaded, the timings and how each one rates; for the slowest interaction, whether it was a tap or click or a key press, the three parts of its time (input delay, processing time and presentation delay), and the tag, id and class names of the element it was on and of up to five elements that contain it, never its text or value; and, for an error, its type, the app script file, line and column it came from, Next.js's error code, and its text with anything resembling a tracking number, email address or code removed; never an IP address. They are kept with the web app's server logs, as the "Server logs" row of the retention table in Section 7 describes.
Contact form: If you contact us via email or the contact form, we store your name, email address, and message to respond to your enquiry and as part of our support history.
Analytics: Google Analytics measures how the public website is used. It sets its first-party cookies, _ga and _ga_<container-id>, which last about 2 years, without a consent prompt; Section 4 says how to opt out. Tracking-result identifiers are excluded from analytics URLs.
Advertising: We use Google AdSense to deliver, measure, and optimise advertising. Google and its advertising partners may use cookies, local storage, device identifiers, and similar technologies for ad delivery, frequency control, measurement, fraud prevention, and—where permitted—personalisation. See Section 4 for details.
3. What We Do Not Collect
We do not: - Require you to create an account or sign in to look up a parcel - Link your public lookups to an account - Sell your tracking numbers or contact-form data - Send tracking numbers to Google Analytics or AdSense
Tracking numbers are shared outside TrackParcel as described in Sections 2 and 5: with the courier you select, with ParcelsApp when the automatic API courier fallback runs, and with an unaffiliated data source when the operator-enabled Shree Anjani fallback is active. These tracking requests are separate from analytics and advertising.
4. Cookies
TrackParcel uses the following cookies and local storage:
Essential and preference storage: "trackparcel-dark" remembers your colour preference. "tp_browser" is a Secure, HttpOnly, SameSite=Strict cookie that expires after 24 hours and binds anti-automation tokens to one browser; the token itself is kept in sessionStorage as "tp-track-token", for the current tab only. A recent-search list ("trackparcel-recent") may be stored in sessionStorage for the current tab only and expires when the tab closes; entries older than 24 hours are discarded.
Google Analytics and AdSense
TrackParcel uses Google Analytics to measure site usage and Google AdSense to show advertising on the public website. Both run with Google's analytics and advertising storage allowed by default, and there is no cookie banner or consent prompt. Google Analytics sets the first-party cookies _ga and _ga_<container-id>, which last about 2 years and tell one browser's visits apart. AdSense, and Google's advertising partners, may use Google's advertising cookies and similar identifiers to personalise ads, and to deliver, limit and measure them. Google may also process IP address, browser and device information, approximate location, referring pages, and interactions for measurement, delivery, security, and fraud prevention.
Google may use and share advertising data with its advertising partners in accordance with Google's Privacy & Terms.
You can review or change how Google personalises ads at My Ad Center, opt out of participating companies through the Digital Advertising Alliance or the Network Advertising Initiative, stop Google Analytics from measuring your visits with Google's Analytics opt-out browser add-on, and block or clear cookies through your browser settings.
5. How Tracking Works
When you submit a tracking number, our server makes a request to the relevant courier's public tracking API or website on your behalf and returns the result to you. Your IP address may be visible in the request to the courier.
Result caching: To improve performance and reduce load on carrier systems, tracking results are temporarily cached on the private TrackParcel server using self-hosted Valkey. Cache duration varies by shipment status — from 5 minutes (out for delivery) up to 30 days (delivered) — and an entry may still be served, clearly labelled as stale, for up to 24 hours past its freshness window when the carrier cannot be reached. Cached data contains the tracking number and shipment-status information returned by the courier. Cache entries expire automatically and are never sold.
Result display: Searches remain on the current page and do not put the tracking number in the browser address bar or history. Legacy share links under /t/ are retired and redirect to the homepage without reading or displaying parcel data.
6. Third-Party Services
TrackParcel uses the following third-party services: - Hosting: Our website is hosted on a private server and proxied through Cloudflare for traffic delivery and CDN caching. The database, sign-in and file storage of TrackParcel and TrackParcel for Business run on our own private server too, using the open-source Supabase software, which we operate ourselves. Cloudflare may process request metadata as per their privacy policy at cloudflare.com/privacypolicy. TrackParcel does not use Cloudflare Turnstile for parcel searches. - Google Analytics and AdSense: Analytics sets the _ga cookies described in Section 4 and receives measurements of how the site is used, and AdSense may use Google's advertising cookies to personalise ads. Google may process device, usage, approximate-location, and advertising-interaction data for measurement, delivery, personalisation, security, and fraud prevention. See Google's advertising privacy information and Google's Privacy Policy. - OpenStreetMap and CARTO: When a tracking result contains enough recognised scan locations to show the optional approximate journey map, the browser requests map tiles from OpenStreetMap, or from CARTO (basemaps.cartocdn.com) when the page is in dark mode. That request reveals the visitor's IP address and the approximate map area being viewed to the provider serving the tiles. The map uses city-centre estimates, not live parcel GPS coordinates.
7. Data Retention
Tracking numbers are kept permanently. Encrypted carrier-health logs are kept permanently and are available only to an authenticated administrator. Security events created when automated abuse is detected are kept for up to 365 days. Contact form messages are kept as part of our support history, because they often include tracking numbers. Tracking-result cache entries expire automatically according to Section 5, including the 24-hour stale window; TrackParcel does not link public lookups to an account. The retention table below covers every kind of data, including TrackParcel for Business.
8. Your Rights
You have the right to: - Request a summary and a copy of the personal data we hold about you - Ask us to correct or erase your personal data, as the retention table below describes - Opt out of personalised advertising through the NAI or DAA links in Section 4
To exercise any of these rights, email support [at] trackparcel.in. "Your rights" below gives the response times and our contact for privacy requests and grievances.
9. Children's Privacy
TrackParcel is not directed at children under the age of 13. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us and we will delete it.
10. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will update the version and the "Last updated" date at the top of this page. For a material change to TrackParcel for Business, Owners get 30 days' notice in the app. Continued use of TrackParcel after changes constitutes your acceptance of the updated policy.
11. Contact
For any privacy-related questions or requests, contact us at:
support [at] trackparcel.in
12. TrackParcel for Business: privacy notice
This notice is for people who sign up to TrackParcel for Business at app.trackparcel.in, and for the businesses they act for. It lists what we collect, why, our role under India's Digital Personal Data Protection Act, and how to use your rights.
| What we collect | Our role | Why |
|---|---|---|
| Your account: name, email address, sign-in and session details (IP address, browser, how you signed in), two-step sign-in factors and preferences | Data Fiduciary | To run your account and keep it secure. You give this when you sign up. |
| Billing details: the business's legal name, billing contact and payments | Data Fiduciary | To bill the business and keep a record of its payments and refunds. |
| Support tickets, messages and attachments | Data Fiduciary | To answer you, and as our support history. |
| Your customers' details that a business adds (names, phone numbers, email addresses, addresses), shipment notes and labels | Data Processor for the business | To track the business's shipments on its instructions. The business is the Data Fiduciary and gives its customers its own notice; our Data Processing Addendum applies. |
| Tracking numbers, courier events and statuses of a workspace's shipments | Data Processor for the business; Data Fiduciary for service data (section 13) | The same. Tracking numbers and their courier history are kept permanently, as the Terms say. Section 13 (Service data) sets out the one exception: our own use of courier results and de-identified, aggregated statistics. |
Withdrawing consent. You can delete your account from your account page in the app. Withdrawing consent doesn't affect what we did before. A business's customers withdraw through that business, which is their Data Fiduciary.
Your rights and complaints. “Your rights” below explains how to ask for a summary, correction or erasure of your data, raise a grievance or nominate someone. If our answer doesn't resolve your concern, you may complain to the Data Protection Board of India.
13. Service data
When a business tracks a shipment with TrackParcel, we fetch the courier's result for its tracking number and keep it in a shared cache. A public lookup of the same tracking number on trackparcel.in may be answered from that result. A public lookup never shows the business's name, its customers' details or any other contact field.
We also build de-identified, aggregated statistics. Some, such as carrier health and refresh metrics, help us run and secure the service and spot a courier outage. Two of them pool shipments from all workspaces: delivery times by courier and lane, for delivery estimates, and each courier's delivery figures, for the “Network median” in analytics. These two hold no tracking numbers and no names, phone numbers, email addresses or address lines, and name no person and no business. We use them to run, secure and improve the service.
A lane is a courier's deliveries from one state to another, or within one state, over the last 180 days, counted across all workspaces. A delivery's origin comes only from the courier's booking details; its destination comes from them or, failing that, the state or PIN code of its delivery address. A delivery whose booking details give no origin is on no lane. When a courier gives no expected delivery date, TrackParcel can show an estimated date range for a workspace's own shipment, but only from a lane of at least 30 deliveries. A lane has no minimum number of workspaces, so it may come from a single business's deliveries; an estimate shows only dates and, in the app, how many of that courier's deliveries between the lane's states it is based on.
On plans that include it, the analytics Couriers table can show the “Network median”: each courier's median transit time and delivery rate for all workspaces combined, next to the workspace's own. We pool each courier's figures day by day, and a day counts only when at least 6 workspaces had shipments with that courier on it. A courier's Network median is shown only when the chosen date range holds at least 200 such shipments from at least 6 workspaces, and only the median and the delivery rate reach the page, never the pooled counts or how many workspaces they came from.
No workspace sees another workspace's tracking numbers, customers or individual shipments through these statistics. The rules above make it hard to trace a pooled figure back to one workspace, but they can't rule it out: comparing overlapping date ranges could isolate one day's pooled figures, and a day may pool as few as 6 workspaces.
For this service data, TrackParcel acts as a Data Fiduciary for its own purposes: operating, caching, securing and improving the service. Businesses agree to this use in our Data Processing Addendum. Service data never includes the names, phone numbers, email addresses or address lines a business adds for its customers. It is TrackParcel's own data and is kept after a workspace closes.
14. How long we keep data
Tracking numbers are kept permanently, everywhere they appear. Personal details a business adds about its customers can be erased without touching them. Backups and caches are copies: when they expire, the live tracking record is unchanged.
| Data | Where | Kept for | Why | On erasure |
|---|---|---|---|---|
| Tracking numbers | Shipments, the shared courier record, public lookup logs (encrypted at rest), API request logs, import errors, webhook payloads, in-app notifications, exports, server logs and error messages | Permanently, except an API key's request log: if we delete the API key, its request log is deleted too | The tracking record is permanent, and we say so plainly here and in the Terms | Kept |
| Courier events and statuses | Each shipment's scan history and status changes, and the courier's latest result | Permanently | Part of the tracking record | Kept. A person's name inside a courier's own result is handled on a verified request from that person |
| Your customers' contact details | A shipment's customer name, phone number, email address and address line | While the workspace exists | The business's own purpose, under our Data Processing Addendum | Erased |
| Pincode, city and state | A shipment's customer details | Permanently | Coarse location for the workspace's own analytics, and de-identified delivery-time statistics (service data) | Kept |
| Labels and notes | A shipment's label and its notes | While the workspace exists | Free text may name a person | Erased |
| Order IDs and tags | Shipments | Permanently | Business identifiers | Kept |
| Your account profile | Your name, email address, sign-in details and preferences | Until you delete your account | To run your account | Erased when you delete your account |
| Memberships and invitations | Who belongs to which workspace, and the invitations sent | Permanently (history) | The workspace's audit trail | A deleted person shows as "Deleted user"; an invitation's email address is replaced by a short hint |
| Audit logs | The workspace's activity log and our admin audit log (append-only) | Permanently | Security and accountability | Kept: they hold ids and non-personal values only, never names, emails or phone numbers |
| Erasure ledger | A record of each erasure (append-only) | Permanently | Proof of erasure, and re-applying it if a backup is ever restored | Holds which fields were erased, never the erased values |
| Product analytics events | In-app usage events | Permanently | Understanding how the product is used; they hold ids only | Kept |
| Public lookup logs | Carrier-health logs of lookups on trackparcel.in, with the tracking number encrypted at rest | Permanently | Diagnosing carrier problems, and the permanent tracking record | Kept |
| Security events | Records of detected abuse, which may include an IP address and never a tracking number | Up to 365 days | Security, and the one-year log duty under the DPDP Rules | Kept until the period ends |
| API request logs | Each request made with an API key, including the caller's IP address | Permanently, unless we delete the API key, which deletes its request log too | The permanent tracking record, and billing evidence | Kept |
| In-app notifications | Alerts and notices shown to members in the app | Permanently | Your team's alert history | Kept |
| Webhook events, deliveries and attempts | What we sent to your systems, each attempt and its response | Permanently | Delivery evidence and replays | The customer's personal fields and the shipment's label are cleared in each event and its payload, so a replay can't send them again; the tracking number is kept, and so are the responses your systems sent back |
| Billing records | Payments, refunds, billing events and activation codes (with who entered each) | Permanently | Payment records | Kept |
| Support tickets and contact messages | Tickets, messages, attachments and contact-form messages | Permanently (they hold tracking numbers) | Service history | The requester's email address is replaced by a short hint; free text is redacted on request |
| Data exports and import files | File storage (stored files have no backup copy) | Permanently (never removed automatically) | So an export you made stays available | Rewritten without the erased fields. In an import file, the erased shipments' rows are emptied in the columns the import matched to customer name, phone, email, address, label and note, on the sheet it read; columns it didn't match and the file's other sheets are kept as uploaded. Tracking numbers are always kept |
| Result cache | Our private cache server | 5 minutes to 30 days, by shipment status, plus up to 24 hours as a labelled stale result | A copy of a lookup, to answer quickly | Expires on its own |
| Database backups | Our own nightly encrypted copy of the database, kept on our server; there is no provider or off-server copy | 30 days, then deleted (the 7 newest copies are always kept) | Recovery after a failure | Erased fields can survive in a backup copy for as long as it is kept; a restore re-applies every erasure first |
| Server logs | The web app's and background worker's logs | Permanently | Diagnosis, security, and the permanent tracking record | Kept: the logs leave customers' contact details out |
15. Your rights
Email support [at] trackparcel.in to use any of these rights. If you have a TrackParcel for Business account, you can also ask from your account page or from your workspace's Data and privacy settings. We answer within these times:
| Right | Response time |
|---|---|
| Access to your personal data | Within 30 days |
| Correction | Within 30 days |
| Erasure | Within 30 days |
| Grievance | Acknowledged within 2 business days; resolved within 30 days, and never later than 90 days (DPDP Rules, rule 14) |
| Nomination | Within 30 days |
Nomination: you may name someone to use your rights if you die or can no longer act yourself. Requests about a business's customers' details go to that business, because it is their Data Fiduciary; if you write to us, we pass your request to the business within 2 business days. Each final answer we give says that you may then approach the Data Protection Board of India.
Privacy requests and grievances
- support [at] trackparcel.in
16. Sub-processors
The services that process data for us, what each one sees and where it processes data, are listed on our sub-processors page.
17. Google sign-in
“Continue with Google” gives us your name and email address, and nothing else from your Google account. TrackParcel's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.