← Back to Peek

Peek · Universal Parcel Tracker

Privacy notice

Effective 20 November 2026

Peek follows parcels, on the web and in its iPhone and Android apps. This notice says what the official service at peektracker.com processes to do that. Peek does not sell personal data, serve advertising, or use advertising analytics. The terms of use say what using Peek involves.

Data the service processes

Why and where data is processed

The service uses this data to authenticate you, store your delivery box, fetch carrier updates, synchronize devices, send requested notifications, prevent abuse, diagnose failures, and honor export or deletion requests. Following your parcels, with what you switch on, is the service you ask for. Abuse limits, diagnostics and usage analytics rest on a legitimate interest in keeping Peek safe and working. Keeping the emails you forward for 30 days rests on a legitimate interest in reading them better. The delivery email rests on your consent.

The app, its database and sign-in (self-hosted Supabase), its logs and its analytics run on a server rented from netcup GmbH, in Germany. Requests reach it through Cloudflare, which relays them and sees network metadata such as your IP address. Google provides Google sign-in and Apple Sign in with Apple. Resend delivers the service's emails, as described under "Emails". Cloudflare Email Routing receives the emails you forward to your Peek address and passes them to the service. An assistant you connect, such as Claude or ChatGPT, receives what you allowed it: your parcels' names, senders, carriers, tracking numbers, statuses, expected days, pickup points and scans, never the recipient's name, postcode or phone digits. Its provider's own privacy terms then apply to what it receives. A tool you give a personal token, such as Home Assistant, receives the same.

To check and improve how it reads the emails you forward, Peek may send some of the kept emails to Anthropic, PBC, in the United States, whose AI model Claude reads them. Anthropic keeps them for about 30 days under its own terms. This rests on the same legitimate interest in reading your emails better.

Cloudflare Turnstile checks the browser or an in-app verification sheet when you start a new parcel lookup to prevent automated abuse. It processes browser and network signals; Peek sends only its verification token to Cloudflare, not your parcel inputs. See Cloudflare's Turnstile Privacy Addendum. A successful check produces a proof kept for fifteen minutes in the current tab's session storage, so reloading the page keeps it (in memory on the iPhone). It is tied to the hostname and to a keyed hash of the network it was made on. It also works on up to two other networks, as when your device moves between Wi-Fi and mobile data; the service keeps keyed hashes of those networks in memory only, and forgets them after the proof expires. Existing parcel pages remain readable without a check. Daily account usage counters prevent bulk lookups. New requests clear counters older than seven days; deleting the account removes its counters.

When enabled for paid Apple builds, App Attest verifies the app without a browser check. Apple attests a key held on the device; Peek stores its public key, identifier, assertion counter and last-use time to prevent replay and limit anonymous lookups. New key registrations remove keys unused for ninety days and their usage counters. New verified requests clear daily counters older than seven days and expired challenges. The app signs signed-in requests with the same key; checking one updates its counter and last-use time and records nothing about the account. Keys are not linked to accounts or parcel inputs. Turnstile remains available when App Attest cannot be used.

The Android app verifies itself the same way with key attestation. The phone's secure hardware makes a key and certifies it with a certificate chain up to Google's attestation roots, which says whether the bootloader is locked, how the system booted and which app asked for the key. Nothing is sent to Google for this: Peek's server checks the chain itself and reads Google's public list of revoked certificates. The Google Play build also asks Google Play for an integrity verdict on the phone and the app when it registers the key, which Peek's server then has Google decode. Google sees one request per installation's key, and no parcel data goes with it. Peek stores and removes the same data as for App Attest. Where neither can vouch for the phone, as on an emulator, or while its key is not used, the app shows the Turnstile check in a web view each time it needs a new proof, and Cloudflare processes the same signals there as on the website.

To get a parcel's history, the service sends its tracking number to the carrier. When needed, it also asks other carriers the number could belong to, a carrier that takes the parcel over on its way, and universal tracking services such as ParcelsApp, Ship24, 17TRACK and the Universal Postal Union. The carriers and services it can ask are listed in the open-source Universal Parcel Scraper. A postcode or private link you supply goes to the carrier it is for; ParcelsApp and 17TRACK also receive the postcode, and 17TRACK the parcel's carrier. In an account, when a check finds that an open parcel saved without a postcode is with a carrier that shows more with one, such as DPD, the service gives it, once, the latest postcode you gave another parcel, preferring one for the same carrier. It then goes where a postcode you typed would, and you can change or clear it on the parcel. Dachser's link shows more than the journey: the service keeps the recipient's name and address it shows and discards its sender, contact and document fields.

J&T Express Mexico and J&T Express China show a parcel only with the last four digits of the recipient's or sender's phone, so their parcels have an optional field for them. If you fill it in, the service keeps those four digits with the parcel and sends them to that carrier with each check, and to no other carrier or tracking service. They never go into a link, a notification or analytics. Like tracking numbers and postcodes, server logs and error reports can include them. They are deleted when you clear the field, choose another carrier for the parcel, delete or forget the parcel, or delete your account.

Browser push services receive encrypted Web Push messages; Apple processes the iPhone app's notification and Live Activity payloads through APNs, and Google processes the Android app's notifications through Firebase Cloud Messaging. Without Google's services, the Android app's notifications go as encrypted Web Push messages to the UnifiedPush distributor you chose, or, without one, wait on the service in the app's inbox until the app fetches them, for a day at most. Those payloads can contain a parcel label, carrier, status, location, the time of the latest scan, and expected delivery text, but Peek does not put the tracking number in them.

Error reports go to Sentry (Functional Software, Inc.), which stores them in the United States for up to 90 days. Sentry is certified under the EU–US and Swiss–US Data Privacy Frameworks, and its data processing addendum includes standard contractual clauses.

The Android app sends no error reports of its own. Google Play passes on its crash and app-not-responding reports (Android vitals) to Peek, under Google's terms. The app may also show Google Play's in-app review prompt, which runs through Google Play.

Outside Switzerland and the European Union, data therefore goes to the United States (Cloudflare, Google, Apple, Sentry, Resend, Anthropic and your browser's push service), to the countries of the carriers and tracking services asked about a parcel, and to wherever the UnifiedPush distributor you chose runs.

The service places scan locations on its map itself, with GeoNames place data (CC BY 4.0) and sorting-centre locations from OpenStreetMap contributors (ODbL), kept on its own servers; no mapping service receives them. The Android app draws its map from data built into the app and fetches nothing for it. When you tap Directions or Show on map for a pickup point, in an app or in an email, Apple Maps or Google Maps receives that pickup point's name and address, and nothing else about the parcel.

The Android app from Google Play has a barcode scanner, which uses the camera only while it is open. Google's ML Kit model, built into the app, reads the frames on the phone; no image or barcode leaves the phone, and ML Kit's usage logging to Google is switched off. The build without Google's services has no scanner and no review prompt.

Emails

Peek sends two kinds of email, both through Resend (Resend, Inc., United States): the sign-in code you ask for and, only if you turn it on, an email when a parcel is ready for pickup and one when it is delivered.

The delivery email is off until you turn it on under Settings › Notifications, or accept the offer shown once after a delivery. It goes to the address you sign in with and contains the name you gave the parcel, the carrier, the time and a picture of the journey with its towns. For a parcel ready for pickup, it also names the pickup point the carrier gave, with its address and a link that opens it in Google Maps, as Directions or Show on map does. It never contains the tracking number. It has no tracking pixel, no tracked links and no remote images. Peek sends at most these two per parcel and nothing else: no newsletter and no promotion.

These emails rest on your consent. Turn them off at any time with the same switch, for one parcel in that parcel's notification settings, or with the link in every email, which works without signing in and takes effect at once. That link carries a token that tells the service which account it belongs to.

Resend receives your email address and the content of each email, and keeps messages and delivery logs in the United States for 30 days. The transfer relies on the EU–US Data Privacy Framework and on standard contractual clauses, with their Swiss additions, in Resend's data processing agreement. Resend publishes the companies that work on its behalf, such as Amazon Web Services, at resend.com/legal/subprocessors.

Usage analytics

The official public web service and connected iPhone and Android apps send screen views and named feature actions (including success/failure) to our self-hosted Umami at u.plhery.com. This helps us understand which features work and where actions fail. Events include the platform, demo/account/anonymous mode, language, and basic browser/device information. When you come to the website from another site or app, its first screen view also names the page that sent you, without the part of its address after a question mark or #, and the source, medium and campaign the link you followed was tagged with, if any. Umami processes IP address and user agent to derive approximate location and rotating visitor/session identifiers. We do not send account IDs, email addresses, parcel labels, tracking numbers, delivery postcodes, phone digits, invitation codes, search text, any other part of an address, or error messages. Events carry no identifier of yours and are not linked to your Peek account.

To tell visits that come back from one-time ones, the apps and the website also keep a random counting identifier on your device (on the website, in your browser's storage; it is not a cookie). It is made on your device and is unrelated to your account, your parcels and the device's own identifiers. Once a day when you open Peek, and again when you sign in, it is sent to the service on its own, with the platform, whether you are signed in and how many parcels the device follows; it never travels with another request. The service keeps only a keyed hash of it, with the first and last day it was seen, on how many days, the first day it was seen without an account and signed in, and that parcel count; never your IP address, an account, a link or a tracking number. The counts made from it only measure how Peek is used and are never combined with other data. Your device replaces the identifier after 13 months. The service deletes a hash not seen for 90 days, and every hash 25 months after it was first seen.

The identifier stays on your device until it is replaced, or until you delete the app's or the site's data: removing the app from an iPhone or iPad deletes it, as does removing the Android app or clearing its storage (Android may restore it from the phone's backup when you install the app again), and on the website, clearing this site's data in your browser. On a Mac it stays in the app's folder in your Library until you delete that folder. The website sends nothing, and deletes the identifier, when your browser asks not to be tracked (Do Not Track or Global Privacy Control) or when Umami's local opt-out is set. App versions from before the counting identifier send none. Historical analytics remain until operational cleanup and cannot be selected by account when you export or delete it because we do not send an account identifier. Local demo builds, simulators, emulators, and unconfigured self-hosted deployments do not collect.

Following a parcel without an account

You can follow a parcel without signing in. The service then stores its tracking number, the carrier, a postcode, tracking link or phone digits if the carrier needs them, the tracking history, and a link to the parcel. No account or email address is stored. A name you give the parcel stays in your browser or in the iPhone or Android app, and in the part of a link after #, which is not sent to the service, unless you share the parcel as a gift, as described below.

Your device keeps a key that shows it made the lookup; the service stores only a hash of that key. Anyone who has the link can see the parcel's status and history, with the tracking number masked to its last characters. Only the device holding the key sees the full number, can forget the parcel, and can keep it after signing in. The postcode, tracking link or phone digits you entered are never shown through a link.

Your browser, or the iPhone or Android app, keeps a list of the parcels you followed or opened this way: each link, its key if this device made the lookup, the name you gave it, whether you archived it and the last tracking history it showed, so the parcel is still there offline. For each parcel they looked up, the iPhone and Android apps also note whether you gave a postcode with the lookup, so they don't ask for one again. The note is a yes or no and never holds the postcode. The list stays on the device until the parcel is forgotten or kept in an account. In the browser and the iPhone and Android apps, a parcel it looked up stays in the list after the service forgets the lookup, marked as no longer updated, with its last tracking history and without its key, until you remove it or clear the site's or the app's data. To open the list on another phone or computer, the browser makes a link, or a code to scan, that carries each parcel's link, key and name after its #. Browsers don't send that part to Peek: the other device reads it and removes it from its address bar. Anyone given the link can follow those parcels and forget them.

Apart from that list, it keeps the last five postcodes you entered for these lookups, each with the carrier it was for, so the next parcel's postcode field can start from yours. They stay on the device after the parcels are forgotten, until you choose Forget this postcode beside one or clear the site's or the app's data.

To limit abuse, the service counts lookups, and numbers it asked carriers about, per day under a keyed hash of the network address and the date. The address itself is not stored, and the counters are deleted after seven days.

The same number looked up by several people, with the same carrier and details, is stored once; each lookup has its own link.

A lookup is forgotten 30 days after the parcel is delivered or returned, or 90 days after its last news (a scan, or the link being opened), or at once when you ask from the device that made it. The parcel's data goes with its last link. If you sign in and keep the parcel, it becomes part of your account. Diagnostic logs, Sentry reports and the review list can retain its tracking number as described above and under "Retention and control".

Sharing a parcel and notifications for a link

You can share a parcel through its link, with or without an account. Anyone who has the link sees the parcel's status and history. They never see a pickup code, a PIN, who signed for the parcel, a door number, a postcode, phone digits or the recipient's name or address: a delivery reads "Delivered" for them. They see the name you gave the parcel only if you choose to show it, and the tracking number stays masked unless you choose to show it. An app that previews the link, a chat app for instance, gets the parcel's status, carrier and estimate, never the number, a name or a place.

You can mark the link as a gift. Until the parcel is delivered, its viewers then see no sender, weight, size or pickup point, the number stays masked, and the scans made in the country the parcel comes from read "Left the sender" with that country and no town.

You can stop sharing at any time. The link then only says that the parcel is not shared anymore. A stopped link from an account is deleted 30 days later; deleting the parcel or the account deletes its links at once.

A name you choose to show travels in the part of the link after #, which is not sent to the service. A gift's link carries nothing there: the name you show, a note and who the gift is from go to the service, which keeps them with the link and shows them to its viewers only once the parcel is delivered. They are deleted with the link. The browser or app you share from remembers what you chose to send along, until the parcel is forgotten on that device.

Anyone who has a link can turn on notifications for that one parcel, without an account, in their browser or in the iPhone or Android app. The service then stores that browser's Web Push endpoint and encryption keys, or that phone's APNs device token, Firebase Cloud Messaging registration token, or installation token with its UnifiedPush endpoint and encryption keys, with its language, which updates to announce, and whether the device that made the lookup turned notifications on. This is deleted when the parcel is delivered or returned, when the browser or phone turns notifications off, its push subscription ends or Apple, Google or the distributor says the token or endpoint is no longer valid, when the link is forgotten, and, for everyone but the device that made the lookup, when sharing is stopped. The notifications carry the parcel's status and never its number or name; a gift's do not say where it is before it arrives.

Your browser is asked for notifications, and creates its push subscription, only when you choose "Turn on". Once they are on for a parcel, you can have them for every parcel in that browser: it then turns them on, with the same choice of updates, for each parcel it holds or adds that is still on its way, and passes over one whose notifications you turned off. The browser keeps that choice, and asks for nothing more. The iPhone app asks when a parcel first comes to it without an account, and keeps the device token beside the parcels it follows that way so that forgetting one turns its notifications off. The Android app asks for Android's notification permission only when you choose to turn notifications on, and keeps its token beside the parcels it follows without an account in the same way. Both apps pass over a parcel whose notifications you turned off on its page. Their Notifications page in Settings keeps on the phone which updates those parcels announce and whether you turned their notifications off there; turned off, the service deletes what it stored for their notifications on this phone, and no parcel is signed up again until you turn them back on. Adding a delivery to your calendar makes a calendar file in the browser; nothing is sent for it.

Answering whether a parcel is right

A parcel's page can ask whether what it shows is right, or which carrier has a parcel no carrier was found for. Answering is optional. An answer is stored with the parcel's tracking number, its carrier, the status and latest scans the service held at that moment, the app and language you answered in, and what you write: a note, or a carrier's name and its tracking page. It is used to find and fix what Peek shows wrongly.

An answer is stored without your account, the link you opened or anything about your device. It therefore cannot be found from an account, is not part of an export, and is not removed when the parcel or the account is deleted. Please leave personal details out of a note. Every answer is deleted 90 days after it was given. A gift's recipient is not asked.

Your browser, or the iPhone or Android app, remembers that you answered, so coming back from the carrier's site does not ask again about the same update. That stays on the device.

Friends is optional

Friends uses a nickname you choose, separate from your sign-in profile. There is no public directory or contact upload. Only people you connect with through a single-use invitation can see your friend card. Invitations expire after seven days. Current invitation keys are stored in an access-restricted table and removed when accepted or revoked. Anyone holding a link can preview your nickname and choose to accept after signing in; the link is an invitation credential. Older invitation formats use a separately hashed acceptance token.

You choose whether to share your delivered-parcel count, average journey rounded up to whole days, and earned Passport stamps. A separate setting, off by default, can show that a parcel arrived during the current week. Friends never receive parcel contents, labels, tracking numbers, carriers, locations, exact delivery times, or information about active shipments. Your email, Google name and photo are not part of your friend card.

Preview your card before saving. Changes apply to the next refresh, at most a minute while Friends is open. Friend cards are not saved for offline use. Removing a connection revokes access on both sides; turning off Friends deletes your friend profile, connections and invitations. Anyone who has already seen a card could still have kept a screenshot or copy.

Retention and control

Parcel data remains until you delete the parcel or the account. Archiving a parcel only hides it from the active list and retains its history. The time your apps last loaded your parcels is overwritten at each visit and deleted with the account. Turning off Live Activities or signing out removes that installation's ActivityKit tokens; notifications waiting in the Android app's inbox are deleted when the app fetches them, and after a day at most; disabled browser endpoints, ordinary native device registrations, and delivery acknowledgements may remain until account deletion or operational cleanup. Infrastructure backups and security logs may persist for the limited retention configured by their operator. The service's own logs are kept for 30 days and Sentry reports for up to 90 days; both can retain a tracking number after its parcel or account is deleted. An entry of the review list is kept up to 10 days after no parcel follows its number any more, because the parcel or the account was deleted or you checked the number without saving it, then deleted. A new check of the number restarts the 10 days. What a check learnt about a number's carrier also goes after 90 days without a new check. The record of a delivery email goes with the account; Resend deletes its own copy after 30 days. Turning off adding parcels by email deletes the forwarding address, what it recorded and the emails kept from it; a new address replaces the old one, which then takes no more email. A kept email is deleted 30 days after it came, or sooner once the account has 100 newer ones. The count of emails an account forwarded each day is kept for seven days. Disconnecting an assistant or deleting a personal token removes it and its keys. A connection unused for 60 days, whose keys have all expired, is removed the next time you open the list or connect an assistant.

Use Download my data in the account menu for a machine-readable export, including your Friends profile and connections. Use Delete account to permanently delete the Auth user and, with it, your parcels, tracking events, shared links, browser subscriptions, native device registrations, delivery acknowledgements, delivery email records, forwarding address and kept emails, connected assistants and personal tokens, and your Friends profile, connections and invitations. If you use Sign in with Apple, the iPhone app asks you to sign in with Apple once more, and the service asks Apple to revoke Peek's access to your Apple ID before deleting your account; the Android app, which has no Sign in with Apple, deletes the account without that step. Deletion cannot remove data already sent to a carrier or data a processor must retain for security or legal obligations.

The browser stores the Supabase session, application preferences, an offline application shell, and an account-scoped offline parcel snapshot. A language chosen in the app is also kept in a first-party cookie, so pages open in that language; it contains only the language code. A number you track from the box of a carrier's page or from a guide's number checker waits in that tab's session storage until the landing opens and takes it, ten minutes at most; it never goes into an address. The number checker names a carrier from the number's shape in your browser, without sending the number anywhere. The iPhone app stores its session in Keychain and a protected account-scoped parcel snapshot; it requests a current APNs token from Apple instead of persisting that token locally. It stores a random installation identifier and the independent Home Screen widget and Live Activity preferences on the device. The Android app keeps its session and an account-scoped parcel snapshot in the app's private storage; its home-screen widgets and its place in Android's share menu read only what is already on the phone. Each snapshot can include tracking history, a private tracking link, a supplied delivery postcode, a reference that contains the delivery postcode, and phone digits you gave. Signing out clears account-scoped local state and ends Live Activities. Browser or operating-system controls can clear app data, Live Activities, and notification permissions.

Security and contact

The service uses HTTPS, short-lived access tokens, rotating refresh tokens, Postgres row-level security, rate limits, and server-only secret keys. No internet service can promise absolute security.

Peek is a personal, non-commercial project run by Paul-Louis Hery, in Switzerland (plhery on GitHub). To get a copy of your data, have it corrected or deleted, or object to how it is used, write to privacy at peektracker.com. You can also complain to your data protection authority.

For a security concern, use GitHub's private vulnerability report. Do not include a real tracking number, delivery postcode, sign-in code, access token or private tracking link in a public issue.

This notice covers the official Peek service. A fork is run by someone else, who must publish their own notice.