Your information, explained

Privacy notice

Here’s what Pedalink keeps, how it helps in an emergency, and what you can control.

Pedalink is a personal passion project by Vivan Patil, not a registered business. Last updated 27 October 2026.

Your profile

• Public details: your name, blood type, any health notes you add, and the profile’s update date. Contact names, age and gender appear only when you choose to share them.
• Contact numbers: stored to enable calls and WhatsApp messages. They aren’t printed on the profile, but someone using its direct-contact options can access the selected number.
• Your own WhatsApp number: kept privately with your profile and never shown on your public tag. With your permission, Pedalink uses it to remind you about pending emergency contact agreements. You can change your reminder preference in Edit/Verify your tag or send STOP to Pedalink.
• Date of birth: stored privately to calculate your age. Your full birth date is never shown publicly. Older profiles may need this added when next saved.
• Account records: tag status, manufacturing and printing references, profile versions, consent wording and dates, and protected sign-in details.

Profile details are provided by the rider and aren’t independently verified. Random tag links make guessing harder, but don’t make a profile private. Rider profiles don’t collect home addresses.

WhatsApp alerts

How contacts agree

You share an invitation with your contact. It lasts seven days and shows your name and their number’s last four digits, without medical details. They send the prepared agreement from their own WhatsApp account to Pedalink at +91 72495 98067.

We match their number and privately save the agreement wording, version, dates and rider/contact association. Changing your name or their number requires a fresh agreement.

When someone asks for help

A helper chooses whether to send a message. Pedalink checks the selected contact’s current agreement and opt-out status before forwarding an alert with the helper’s WhatsApp number and any location they included.

Location is optional. It is requested only after the helper chooses to share it and allows browser access. There is no continuous tracking. Direct WhatsApp options send the message to the contact instead.

We don’t save raw chat, helper phone numbers or coordinates in our database or application logs. We do keep limited request and delivery records for seven days, including tag/contact references, protected identifiers, timestamps, status, error codes and Meta message IDs. These help prevent duplicates and investigate problems. Meta processes messages under its own terms.

Stopping alerts

Send STOP to Pedalink on WhatsApp to stop automated alerts for all riders who list you. To agree again, use a new invitation. Calls and direct messages remain available.

We keep a protected one-way number identifier and the opt-out time so an old message cannot restore permission. This record contains no plain phone number, name or chat text. To remove your number from a rider’s profile too, ask the rider or contact us.

Nearby hospital search

Pedalink provides an optional link that opens a nearby-hospital search in Google Maps. Pedalink does not request, access, transmit or store your device location when you use this link. Pedalink does not receive the search results, hospitals viewed or directions requested.

After Google Maps opens, Google may process location, device and usage information according to your device settings, Google account settings and Google’s Privacy Policy. Google Maps is an independent third-party service and is not operated or controlled by Pedalink. See also the Google Maps/Google Earth Additional Terms.

Orders and delivery

We privately collect your chosen tag and seatpost type, name, WhatsApp number, delivery address, expected-price feedback, optional note and contact consent to fulfil your order. We also store its reference, fulfilment status, any self-pickup marker and shipment/export details. An unfinished form stays in browser memory and is cleared when you leave or reload.

Authorized administrators can access order details for fulfilment and delivery support. Necessary details are shared with courier services, and manual order exports are stored for this purpose. Order details are separate from public profiles; your address and phone number aren’t placed in URLs or analytics.

We use WhatsApp to coordinate delivery. You can contact us to correct or request deletion of order information. Donations are optional and don’t affect order eligibility.

Reviews and photos

When you send a review, we privately store your name, Indian mobile number, ratings, experience, optional suggestions and photos. Your number is only used if we need to follow up; it is never included in public review data. Photos are compressed and location metadata is removed.

Sharing is optional. Only with your permission and our approval may your name, review, ratings and photos appear publicly. Suggestions stay private. Please avoid contact details or other private information in your review and photos. Contact us to correct, withdraw or delete a submission. We retain submissions to respond to feedback and maintain approved rider stories until removal is requested or we no longer need them.

Manage your information

Visit Edit/Verify your tag and enter your name and PIN to:

• Edit your details and sharing choices.
• Deactivate your tag to hide the profile while keeping it privately for you.
• Delete your profile, contact agreements, invitations and sign-in records from the live database. Your personal details and contact confirmation status are also erased from the recovery copy; only the tag code and deletion status remain. A minimal non-personal record prevents reuse of the tag code.

Keep your PIN private. We store a protected password hash, not the PIN itself, and a normalized name for matching. Forgot PIN requests are manually reviewed. We match the submitted name and registered phone number, and keep a request record with the name, masked number, matching tag references, time and a protected request-source identifier. Where recovery is available, an authorized administrator can send a single-use reset link to the rider’s saved WhatsApp number. The link expires after 48 hours. Reset records contain protected token/phone identifiers and audit metadata; we do not store the new PIN in plain text. Deleting information cannot remove copies someone has already saved or photographed.

How long we keep data

• Live profiles: until you delete them. Deactivation hides a profile rather than deleting it.
• Recovery copies: entered profile details, sharing choices, tag code and contact confirmation status are stored separately to recover accidental admin deletions. They survive admin deletion and deactivation. When you delete your personal data, personal details and contact confirmation status are erased from the recovery copy, leaving only the tag code and deletion status. Deactivation alone retains the private recovery copy until it is purged or you delete your data. Recovery copies do not contain PINs or sign-in credentials.
• Emergency logs and duplicate-message records: accessible for seven days, then eligible for removal by expiry or cleanup.
• Opt-out records: retained to keep your STOP preference effective.
• Orders and courier exports: kept for fulfilment and delivery support; contact us about correction or deletion.
• Temporary access and limits: sign-in sessions have expiry times, activation recovery lasts up to 15 minutes, and temporary abuse counters have short validity periods, generally up to two days. Expiry stops their use; it does not guarantee immediate physical deletion.
• Security and recovery records: admin audit events, security alerts, PIN-recovery requests and reset history are retained for security investigation and support. These records do not currently have a universal automatic deletion schedule; clearing a notification does not necessarily erase its underlying record. Contact us about a record concerning you.
• Scan statistics: aggregate visit and throttle counts are retained against the tag code. Temporary scan-limit records use protected source identifiers and a short rolling window; aggregate counts can remain after those records expire.

Expired records stop granting access even if database cleanup happens later. The browser keeps a random emergency-request reference for its session; it does not establish that a message was sent or delivered. Matching server events determine the backend delivery record.

Security and services

Pedalink uses Vercel for hosting, Google Firebase Firestore for its database, and Meta for WhatsApp messaging. The primary Firestore database is located in Mumbai, India. Hosting, messaging, support and delivery providers may process data in other countries under their own policies; database location does not mean every copy or service stays in India. Administrators can access relevant private records for support and operations. See the Firebase privacy information, Vercel privacy policy and WhatsApp privacy policy.

Secure, short-lived cookies support sign-in and activation recovery. Protected network identifiers help limit abuse. PIN sign-in and recovery attempts are rate-limited. Security records may include an administrator’s identity, action, result, time, affected tag references and a keyed, privacy-preserving request-source identifier. Raw IP addresses are not saved in these application rate-limit records, although infrastructure providers may process connection IPs.

We count tag-page visits and throttled requests, including repeat attempts. To limit abuse, we temporarily associate a tag code with a protected identifier derived from the request source and recent load timestamps. These records are separate from aggregate scan totals and do not contain a raw IP address or precise location. We do not install third-party advertising or analytics trackers. Application diagnostics are designed to avoid recording PINs, medical notes, raw chats and full phone numbers; the support, order, recovery and security records described above are stored separately. Providers may keep their own operational logs.

The optional QR scanner uses your camera only when you open it. Video stays on your device and stops when you close the scanner, leave the page or switch tabs. It doesn’t use your microphone or location.

Young riders and public sharing

If a rider is under 18, a parent or guardian should review the service and sharing choices with them before setup. Pedalink currently has no dedicated verified-parental-consent workflow. Please contact us before adding a child’s information if you need help deciding what should be public, or to request removal of a child’s profile.

Questions, correction and withdrawal

You can ask what information we hold about you, request corrections or deletion, withdraw optional review or reminder permission, or raise a privacy complaint using the contact below. We may need proportionate verification before disclosing or changing a record. Please never send your PIN or unnecessary medical details in a support message.

Deleting a profile does not automatically delete separate orders, reviews, support correspondence, security records, courier exports or records already held by providers. Ask us about those separately. Copies downloaded by administrators or saved by others require separate handling; we cannot recall another person’s screenshot or message. Necessary records may also be retained where required by applicable law.

We use data to provide the features described here, manage requests and protect the service. Optional publication and reminders depend on your sharing choices. We may disclose necessary information to fulfil a legal obligation or respond to a valid legal request. This notice will be dated again when material practices change.

Contact us

For privacy questions, corrections or deletion requests, contact Vivan Patil on WhatsApp at +91 86982 76725.