Frilok Privacy Policy
Preamble
This document is an electronic record in terms of the Information Technology Act, 2000 and the rules made thereunder, as amended from time to time, and does not require any physical or digital signature. It is published in accordance with Rule 3(1) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 and Rule 4 of the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 (the "SPDI Rules"), and in accordance with the Digital Personal Data Protection Act, 2023 (the "DPDP Act") and the Digital Personal Data Protection Rules, 2025 (the "DPDP Rules") as and when their provisions come into force.
This Privacy Policy forms part of, and shall be read together with, the Frilok Terms of Use and End-User Licence Agreement (the "Terms"). Capitalised terms used but not defined in this Privacy Policy have the meanings given to them in the Terms.
1. Scope and Responsible Entity
1.1 Scope. This Privacy Policy describes how the Operator collects, uses, stores, discloses, transfers and otherwise processes the Personal Data of Users in connection with the Platform. It does not apply to any third-party service, website or application, including any App Store or map tile provider, which is governed by the privacy policy of its own provider.
1.2 Data Fiduciary. In respect of each Designated Territory, the Operator determines the purposes and means of processing Personal Data and is the "Data Fiduciary" within the meaning of the DPDP Act (and the "controller" under the laws referred to in Schedules B and C). In respect of India, the Data Fiduciary is High Way Fresh, a sole proprietorship concern having its principal place of business at Sonapur, Kamrup (Metro), Assam. PIN: 782402 ("HWF").
1.3 HWF as Data Processor. Where the Operator of a Designated Territory is a person other than HWF, HWF operates the Platform's infrastructure and processes Personal Data solely on behalf of, and on the documented instructions of, that Operator, as its Data Processor, under a written contract.
1.4 Consent. Where processing is based on consent, the Operator shall obtain it through a separate notice presented in the App that describes the Personal Data concerned and the purpose of processing. Consent may be withdrawn at any time with the same ease with which it was given. Withdrawal shall not affect the lawfulness of processing carried out before withdrawal, and may result in the discontinuation of the feature concerned.
2. Definitions
In this Privacy Policy:
"Data Principal" means the individual to whom Personal Data relates.
"Data Processor" means any person who processes Personal Data on behalf of a Data Fiduciary.
"Location Data" has the meaning given in the Terms.
"Personal Data" means any data about an individual who is identifiable by or in relation to such data.
"Personal Data Breach" means any unauthorised processing of Personal Data or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to Personal Data that compromises its confidentiality, integrity or availability.
"Processing" means any wholly or partly automated operation performed on Personal Data, including collection, recording, organisation, structuring, storage, adaptation, retrieval, use, alignment, combination, indexing, sharing, disclosure, restriction, erasure or destruction.
"Service Provider" means a third party engaged by the Operator to process Personal Data on its behalf.
"Sensitive Personal Data or Information" has the meaning given in Rule 3 of the SPDI Rules.
3. Personal Data Collected
3.1 The Operator collects the following categories of Personal Data:
| Category | Personal Data | Source |
|---|---|---|
| Account and identity | An internal account identifier allotted by the Operator, which is never shown; the Frilok ID (Terms, Clause 4.3), if the User chooses one; display name, profile photograph, biographical description; authentication credentials (a password, if the User sets one, and sign-in tokens issued to each signed-in device), which are stored only in protected (non-reversible) form | The Operator; the User |
| Contact details | Mobile number (one per Account, verified by a code; required for every Account, Terms Clause 4.1A) and e-mail address (optional) | The User |
| Contacts (optional, Clause 3.7) | The telephone numbers in the User's address book, read on the device only when the User asks the App to find friends among the User's contacts and sent only to be matched; and, between two Users who each have the other's number saved, the fact that they do | The User's device |
| Documents | For each document a User sends for themselves, their business or their vehicle (Terms, Clause 5.2): its kind, the issuing country, its number (for a proof of identity, only the last four characters), its date of expiry, what the driver states a driving licence covers, photographs of the document and a fingerprint (hash) of each photograph, how each detail was entered, and the decision of Frilok staff (accepted or not accepted, the reason, who decided and when) | The User; Frilok staff for the decision |
| One-time passwords and verification codes | Codes sent to sign in with a mobile number, to verify an e-mail address or telephone number, to confirm a change of number or password, or to confirm the handover of an order; and the record of which device entered the code for the Account's number (the main device, Terms Clause 4.8) | Generated by the Operator and sent to the User |
| Location Data | As described in Clause 4 | The User's device |
| Communications | Messages and attachments; call metadata (participants, time, direction, duration) | The User and other Users |
| Transactions | Requests, Offers and Counter-offers, orders, prices agreed, delivery, collection and meeting points, routes selected and followed for Tracked Orders, steps marked by the parties, ratings, reviews and disputes | The User and other Users |
| Order payments and dues | For each order: any amount the Seller asks to be paid first; for each amount paid or returned, its amount, currency, whether it was paid to the Seller or returned to the Customer, how it was paid (UPI, cash, bank transfer, card or other) and a reference number if the party gives one, the User who recorded it, whether the other party confirmed it or said it was not received, and the date and time; and any amount outstanding | The Customer and the Seller of that order |
| Store | For Sellers: Store Page particulars, including name, photographs, opening hours, contact particulars, licence and tax registration numbers, terms of sale and Shop Rules | The Seller |
| Seller payment particulars | For Sellers who enter them: a UPI ID (stored in encrypted form) and the name to show with it, and a record of each change (when it was made and from which device) | The Seller |
| Preferences | The shops that the User has chosen to follow; notification and privacy settings | The User |
| Content | Listings, catalogues, photographs and other Content | The User |
| Device and technical | Device model, operating system and version, App version, IP address, push-notification tokens, records of App state necessary for message delivery, and, on Android devices where the User allows it, whether the SIM card that received the sign-in code is still in the device (not the SIM's number) | The User's device |
| Commercial vehicles and fleet assets | Commercial vehicle registration numbers, vehicle category (auto, hatchback, sedan, suv, bus, truck), capacity, fuel type, make, model, wheelchair accessibility, commercial transport permits, and fitness and insurance particulars | The Transport Provider |
| Product scans | Photographs a Seller chooses to take, for a product scan, of a product's packaging, its label and the items to be counted; and the details read from them, such as the product name, price, barcode, dates and the number of items. The photographs are kept only while the scan runs (Clause 10.1); a photograph the Seller adds to a Listing is kept as part of that Listing | The Seller |
| Support and grievances | Correspondence with the Operator and the Grievance Officer | The User |
3.2 Authentication credentials constitute Sensitive Personal Data or Information under the SPDI Rules and are collected with the User's consent solely for authentication. The Operator does not collect financial information such as bank account or payment card details; payments between Users are made outside the Platform.
3.3 The Operator does not knowingly collect Personal Data of persons under eighteen (18) years of age (Clause 13).
3.4 No tracking. The App contains no third-party analytics, advertising or tracking software, and the Operator does not track Users across applications or websites of other persons. The Operator shall amend this Privacy Policy before introducing any such software, and shall seek consent where Applicable Law so requires.
3.5 Website. The websites at frilok.com
provide information about the Platform, publish the Terms and this
Privacy Policy, explain how a User may delete its Account or some of its
Personal Data, and enable a User to request such deletion. They use no
advertising or analytics cookies. Personal Data furnished in a request
for deletion (the mobile number or e-mail address registered with the
Account, the Frilok ID, and a description of the data concerned) is used
only to verify that the requester holds the Account and to give effect
to the request. The Operator's hosting and network-protection provider
receives the IP address and browser particulars of visitors in order to
deliver and protect the websites.
3.6 Sharing to other applications. Where a User shares a Listing or store to another application through the device's share function, or follows a link or telephone number leading outside the Platform, the information concerned passes to that application or service, whose own terms and privacy policy apply. The Operator is not responsible for the processing of Personal Data by any such application or service.
3.7 Your contacts (finding friends). The App can find which of the people in the User's address book are on Frilok, and who among them already has the User's number saved. This works as follows, and only if the User asks for it:
(a) When. The address book is read only after the User taps "Find friends from my contacts" (or agrees when the People screen offers it), after a notice stating this Clause's substance and with a "Not now" choice; never on the first open of the App, and never in the background without the User having turned the feature on. The device permission is asked for at that moment and may be refused or withdrawn in the device settings; the App works fully without it.
(b) What is sent. The telephone numbers in the address book (in international form), over the encrypted connection, in batches; names, photographs and other address-book details stay on the device. The first check may send up to a number of contacts, and later checks only changed numbers up to a daily number, set by the Operator to keep the feature from being used to scan numbers at large.
(c) What is kept. The numbers of persons who are not on Frilok are answered and forgotten in the same request; they are not stored and not logged. Where a number belongs to a User who allows being found by number (paragraph (e)), the Operator keeps only the fact that the User has that person's number saved, as a link between the two Accounts, without the number. The device keeps a small cache of which of the User's contacts are on Frilok so the list opens at once.
(d) What it is used for. To mark contacts who are on Frilok, to add two Users as friends automatically where each has the other's number saved (both having asked for the feature), and to offer a one-tap friend request where only one has. Nothing else; the links are not used for advertising, for suggestions to third persons, or to build profiles.
(e) Being found. "Let people who have my number find me on Frilok", under Me → Privacy and safety, is on by default. When it is off, the User is not marked as being on Frilok for anyone, and the links concerning the User are deleted.
(f) Withdrawal. Turning the feature off in the App deletes the links under paragraph (c) and the device cache; withdrawing the device permission stops any further reading. Deleting the Account deletes the links (Clause 10.3).
(g) Invitations. An invitation to a contact who is not on Frilok is sent from the User's own messaging application, with text the User can see and change; the Operator does not send messages to numbers in the User's address book and does not learn whether the invitation was sent.
4. Location Data
4.1 Purposes. The Operator processes Location Data only in the following circumstances:
| Circumstance | Period | Recipients | Basis |
|---|---|---|---|
| Display of the map and nearby places | While the map is displayed | None; processed on the device | Use voluntarily initiated by the User (DPDP Act, s. 7(a)) |
| Orders (Terms, Clause 6.3(a)): the point of delivery, collection, pick-up or meeting | For the life of the order, then as set out in Clause 10.2 | The parties to the order | Use voluntarily initiated by the User for the specified purpose (DPDP Act, s. 7(a)) |
| Tracked Orders, in which a party goes to, or accompanies, the other, such as a delivery, a collection, a visit or the carriage of a person or goods (Terms, Clause 6.3(b)–(c)): live positions, the route selected and the route followed | From the time a party sets out to the completion or cancellation of the order; retained as set out in Clause 10.2 | The other participants in that order; the Operator, for the performance of the order, safety, fraud prevention and dispute resolution | Use voluntarily initiated by the User for the specified purpose (DPDP Act, s. 7(a)) |
| Personal location sharing (Terms, Clause 6.4) | While the User shares, for the duration selected | Only Users with a mutual contact relationship who have accepted by sharing their own Location Data | Consent (DPDP Act, s. 6) |
| Travel Together: the positions a member shares within a Group for a period chosen by the member who starts it, with the member's means of travel, route so far, route ahead and Travel Party (Terms, Clause 6.5; Clause 5.8) | While the User shares in the session | The members of that Group who are sharing at the time; the Operator's map and routing service provider, for the route ahead | Consent (DPDP Act, s. 6) |
| Providers who receive Requests by their current position (Clause 4.4) | While location sharing for work is enabled | As set out in Clause 4.4 | Use voluntarily initiated by the User (DPDP Act, s. 7(a)) |
| Live display of a vehicle open to booking, unless the Provider has disabled it (Clause 4.4A; Terms, Clause 6.2A) | While the vehicle is open to booking and the display is enabled | Users viewing the Listing within the distance determined in the App | Use voluntarily initiated by the User (DPDP Act, s. 7(a)) |
| Places, points, routes and areas that a User shares (Terms, Clause 6.8) | Until the User or the recipient deletes them | The Users with whom they are shared, and any person to whom those Users share them further | Use voluntarily initiated by the User (DPDP Act, s. 7(a)) |
4.2 Mutual visibility. Save for the position of a vehicle open to booking displayed with its Listings under Clause 4.4A, Location Data shared under Clause 4.1 is not published to a User's wider contacts, profile or the public, and may not be requested by other Users. The Operator's servers verify, upon every request for Location Data, that the requesting User is entitled to receive it. When either of two Users sharing with each other ceases to share, sharing ends for both.
4.3 Background processing. Location Data is processed while the App is in the background, closed or the device is locked only (a) during a Tracked Order, and (b) for personal location sharing, where the User has enabled background sharing. The device displays a persistent indication while such processing continues. Permission to access location "all the time" is requested only when the User enables background sharing, after an explanatory notice, and may be refused or withdrawn in the device settings at any time.
4.4 Providers who receive Requests by their current position. Where a Provider without a fixed store, such as a delivery person, a mobile vendor or a Provider who carries persons or goods, enables location sharing for work in order to receive Requests near it (Terms, Clause 6.2):
| Matter | Position |
|---|---|
| Personal Data processed | Geographical position, accuracy, speed, direction of travel and time |
| Purposes | Before an order is agreed, only to determine whether the Provider is within the distance each Customer selected for a Request; during a Tracked Order, to enable the participants to see one another until its completion or cancellation, and for safety, fraud prevention and dispute resolution |
| Recipients | Before an order is agreed, the Operator's servers only; Customers are not shown the Provider's position, save for the live display of a vehicle open to booking under Clause 4.4A. During a Tracked Order, the participants in that order and the Operator |
| Nature of storage | The current position is held in server memory while sharing is enabled and is not retained as a location history |
| Effect of disabling sharing | The Provider ceases to receive new Requests by its current position; the last known position is retained for not more than two (2) hours and then deleted; Requests may continue to be shown by reference to any store or base location recorded in its profile; if a Tracked Order is in progress, Clause 6.3 of the Terms applies |
| Retention | As set out in Clause 10.2 |
| Safeguards | Transmission over encrypted connections; server-side verification of every request; notifications contain no coordinates of any User's position; access to Location Data is logged |
4.4A Live display of vehicles open to booking. Where the live display of a vehicle with its Listings is enabled (Terms, Clause 6.2A):
| Matter | Position |
|---|---|
| Personal Data processed | The current position of the vehicle and the time |
| Purpose | To enable Users to decide whether to book a free seat on, or hire, a vehicle that is open to booking |
| When | Only while the display is enabled, location sharing for work is enabled, and the vehicle is open to booking (a vehicle for hire that is available and not engaged in a Tracked Order, or a trip with at least one free seat during the period shown in the App). Display ceases as soon as any of these conditions ceases to be met, and while the vehicle is near a place the Provider has saved as private |
| Recipients | Users viewing the Listing within the distance determined in the App. They are not shown the past positions of the vehicle, nor the identity of any person in it |
| Nature of storage | The current position is held in server memory as described in Clause 4.4; no history of positions is created by reason of the display |
| Choice | Enabled when the Provider publishes a trip or offers a vehicle for hire, after notice in the App; not a condition of publishing any Listing; may be disabled for any vehicle at any time with immediate effect. The mutual-visibility rules of Clause 4.2 for personal location sharing do not apply to this display |
4.5 Other Location Data.
(a) Routing requests are processed to compute a route. A route selected for a Tracked Order, and the route followed in performing it, are stored with the order as provided in Clause 4.1 and Clause 10.2. Other routing requests are not retained.
(b) Places saved by a User (for example "Home" or "Work") are stored on the Operator's servers and are visible only to that User, unless the User shares them. A place, point, route or area that a User shares with other Users is visible to them, may be shared further by them, and remains with them until they delete it; the Operator is not responsible for such further sharing.
(c) A Request published without display on the map is notified only to Providers within the distance selected by the Customer, and is not displayed on any map.
(d) The country in which a User is at present. So that the rules of the country in which a User is can be applied, the App reports that country to the Operator's servers when the User signs in, returns to the App, or has moved a long distance. The country is found from the device's position, where the User has allowed location access, or from the country of the device's mobile network. The position is used only to find the country and is not stored for this purpose; the country is kept by the servers for not more than twenty-four (24) hours. Where neither is available, the servers may look up the country to which the IP address of the device's connection is registered (using the DB-IP database), solely to suggest a country, which the User confirms or changes in the App. No rule is applied on the strength of such a suggestion until the User confirms it, and the IP address is not stored for this purpose.
4.6 The Operator does not sell Location Data, does not disclose it to advertisers or other third parties for their own purposes, and does not use it to build profiles of Users. The App may show a User stores near the User's current position or along a route that the User is following, including promotions paid for by their Sellers, which are labelled "Sponsored" (Terms, Clause 3.7). Such stores are selected at that moment by place, route and category only; the Location Data used to select them is not stored for that purpose, is not disclosed to the Sellers concerned, and is not used to profile the User.
5. Communications, Calls and Content
5.1 Messages. Messages are transmitted over encrypted connections. The Operator retains a server-side archive of messages, in accordance with the User's message-history setting, to enable synchronisation across devices and restoration on a new device. Messages in the archive, and messages held for delivery to a User who is not connected, are stored in encrypted form. The content of each message is encrypted with a key specific to the User, or to the group conversation, to whose archive it belongs; those keys are themselves protected by a key management service and are stored separately from the messages. The identity of the sender and of the recipient and the time of each message are not encrypted, as they are required to deliver messages and to arrange the archive. Messages are not end-to-end encrypted: the Operator is able to decrypt them in order to deliver them, to make them available on each device signed in to the Account, and as provided in Clause 14 of the Terms. A User may delete a message: it is removed from the User's device and from the User's copy in the archive, while the copy held for any other participant is not affected. In a group, a User may also delete its own message for all participants.
5.2 Calls. The content of voice and video calls is transmitted directly between devices or, where a direct connection is not possible, through relay servers, and is encrypted in transit by means of DTLS-SRTP. The Operator does not record calls and relay servers cannot access their content. A User's telephone number, device identifiers and mobile carrier are not disclosed to the other party to a call. Call logs are stored on the User's device. Relay servers retain limited technical records (session times and IP addresses) solely for rate limiting, the prevention of abuse and attacks, and compliance with Applicable Law.
5.3 Media. Photographs and attachments are uploaded to access-controlled storage. Device and location metadata embedded in photographs is removed on the device before upload.
5.4 Public information. A User's profile, Store Page (including its Shop Rules), Listings, reviews and photographs uploaded to public place records are visible to other Users.
5.5 Notifications. In order to inform a User of messages, calls, Offers and orders while the App is not open, the Operator sends notifications through Google Firebase Cloud Messaging (on Android devices) and the Apple Push Notification service (on Apple devices). A notification may contain the display name of the other User, a short description of the event and an amount, and may be displayed by the device on its lock screen. A notification of a message states only the display name of the sender or the name of the group conversation, and that a new message has been received or that the User has been mentioned; it does not contain the content of the message. A notification may state that a User has started or stopped sharing its location, or has sent a place, and may include the name of a place or a meeting point chosen by the sender; notifications do not contain the coordinates of any User's position. A User may conceal the content of notifications on the lock screen, or disable notifications, in the settings of the device.
5.6 Order Records. The Operator does not receive, hold or transfer any payment: a Customer pays the Seller directly (Terms, Clause 9.8A). A Seller's payment particulars are shown only to the Customer of an order the Seller has accepted, while payment is due, so that the Customer can pay; the Operator does not check them. Payments recorded in an Order Record, and any amount outstanding, are displayed only to the Customer and the Seller of the order concerned, and may be communicated to both of them as messages in the conversation relating to that order. The Operator processes them solely to maintain the Order Record and to handle any problem report concerning the order. The Operator does not use them to assess the creditworthiness of any User, and does not disclose them to any credit information company, lender or advertiser.
5.7 Listing records. For each Listing, the Operator records the changes made to its quantity, free seats or availability, the reason and any cost price or note entered by the Seller, and the time at which the Seller last updated or confirmed it. The quantity, free seats or availability, and the date of the last update or confirmation, are displayed with the Listing (Terms, Clause 9.17); the other records are visible only to the Seller. The Operator uses the time of the last update or confirmation only to apply the Update Period and to remind the Seller before a Listing is set to zero or marked as not available, and does not use these records to rank or assess any Seller.
5.8 Travel Together. While a User shares in a Travel Together Session (Terms, Clause 6.5):
(a) its positions are relayed to the members of the Group who are sharing at the time, and are not written to the Operator's databases. For the duration of the session, the Operator's server holds in memory the User's route so far (its positions since it began to share, thinned to one point every twenty-five (25) metres or more) and its latest route ahead, so that a member who opens the Group's map later sees them; both are discarded when the User stops sharing, leaves the Group, or the session ends;
(b) the means of travel which the User chooses, and the Travel Party which it joins, are shown to those members; the App does not infer the means of travel from the device's sensors and requires no additional permission;
(c) the route ahead is calculated on the User's device: its position and the meetup point, or the position of the traveller whom the Group follows, are sent to the Operator's map and routing service provider, which returns the route; the route is shared with the members and is not stored by the Operator after the session;
(d) the record of the session (who started it, its times, its meetup point, who shared and for how long, whom the Group followed, by whose choice and when, and who travelled in which Travel Party and when) contains no positions or routes, is kept with the Group and is visible to its members, and is deleted with the Group; it is included in the User's copy of its Personal Data (Clause 12.2);
(e) during a session, the Group's voice room is end-to-end encrypted and is not recorded; a record of who took part in it and when is kept as for other calls (Clause 5.2), including any Guest with the member who brought it. A photograph or video sent to the Group is a message (Clause 5.1); the pin showing it on the Group's map at the sender's position is drawn on the members' devices and is not stored. An SOS sends the User's position to every member of the Group, and the record of the alert, its responses and its resolution is kept with the Group's messages; once the alert is resolved, the position is removed for all members. Joining a Group by a member's code records whose code was used, who joined and when, with the Group.
5.9 Documents. Other Users see only whether a business's documents were checked, the date of the check and the expiry dates of its documents, and the numbers that the law asks a business to show (such as a food business licence or a business or tax registration). They never see the photographs of any document or the numbers of a person's documents. The account holder of a vehicle sees whether its driver's documents are accepted, but not the driver's photographs or numbers. A User sees all of its own documents at any time. Frilok staff who check documents or handle complaints see the documents; every view and decision by staff is logged. The Operator uses documents only as stated in Clause 5.2D of the Terms: to check them and show the "Documents checked" mark, to decide which businesses, vehicles and drivers may be shown to Customers or take orders and bookings, to remind the User before a document runs out, to look into complaints, reports and suspected fraud, and to meet its legal duties. It does not use them for advertising or marketing, to build a profile of any person, to rank or order Users, Listings or Offers, or to assess credit, and does not sell, rent or give them to anyone for those purposes. Reminders are sent by notification in the App and, where the User has given an e-mail address and chosen to receive them, by e-mail.
5.10 A driver's details shown to Customers. Where a User drives a vehicle that carries passengers for payment (Terms, Clause 10.8), from the start of a booking's negotiation the Customer sees the User's first name, profile photograph, that the User's identity document and licence were checked, and the ratings and reviews from trips the User drove, and may open the User's profile as far as its profile visibility allows. The Customer never sees the User's document numbers or document photographs. Where the User drives for another User's business, Requests from Customers and notices about the vehicle's bookings and documents are sent both to the User and to the account holder.
5.11 Claims of places. When a User claims a place on the map as its store (Terms, Clause 5.1A), the Operator keeps a record of the claim: the place record as the map showed it; the name, address, telephone number and position the User confirmed; the store's details before the claim, so that a claim not accepted can be undone; the decision of Frilok staff, any note sent to the User, and who decided and when. Frilok staff who check claims see the record and may telephone the number shown on the public place record; every decision by staff is logged. Other Users see only the store itself. The Operator uses the record only to check the claim, to undo or transfer it, to handle disputes and complaints under Clause 5.4 of the Terms, and to meet its legal duties. Documents sent for a claim are handled as stated in Clause 5.9. The record is erased with the Account under Clause 10.3, save where it is needed for a pending dispute or must be preserved under Clause 10.5.
6. Device Permissions
6.1 The App requests access to the following device functions only when a feature requiring it is first used, and access may be withdrawn at any time in the device settings:
| Permission | Purpose |
|---|---|
| Location | The purposes in Clause 4; access "all the time" only as provided in Clause 4.3 |
| Microphone | Voice and video calls |
| Camera | Video calls and photographs taken by the User |
| Photographs and files | Selection of items through the device's own picker; the App does not access the User's entire library |
| Notifications | Alerts for messages, calls, orders and location-sharing requests |
| Background services | Persistent notification during background location sharing; incoming-call display when the App is closed |
| Contacts | Finding friends among the User's contacts (Clause 3.7); asked for only when the User taps "Find friends from my contacts", after the notice there described |
| SIM state (Android) | Noting whether the SIM card that received the sign-in code is still in the device (Clause 3.1, "Device and technical"); no telephone number is read |
6.2 The microphone and camera are used only while the User makes, answers or participates in a call or takes a photograph.
7. Purposes and Lawful Bases of Processing
7.1 The Operator processes Personal Data for the following purposes and on the following bases:
| Purpose | Basis under the DPDP Act | Basis under the GDPR (Schedules B and C) |
|---|---|---|
| Registration and administration of the Account; authentication, including sign-in by code to the mobile number and the binding of the Account to that number | s. 7(a) | Art. 6(1)(b) |
| Finding friends among the User's contacts, and being found by number (Clause 3.7) | s. 6 (consent) | Art. 6(1)(a) |
| Delivery of messages, calls and notifications | s. 7(a) | Art. 6(1)(b) |
| Location Data for orders, Tracked Orders and Providers who receive Requests by their current position | s. 7(a) | Art. 6(1)(b) |
| Personal location sharing, Travel Together, background sharing and location history | s. 6 (consent) | Art. 6(1)(a) |
| Display of Listings and Requests | s. 7(a) | Art. 6(1)(b) |
| Offers, orders and Order Records, including recorded payments and amounts outstanding | s. 7(a) | Art. 6(1)(b) |
| Promotional messages from stores that the User follows | s. 6 (consent, given by following the store) | Art. 6(1)(a) |
| Security, fraud prevention and enforcement of the Terms | s. 7(a) | Art. 6(1)(f) |
| Compliance with Applicable Law and orders of authorities | s. 7(d) and (e) | Art. 6(1)(c) |
| Response to a medical emergency or threat to life | s. 7(f) | Art. 6(1)(d) |
| Grievance redressal and dispute resolution | s. 7(a), (d) and (e) | Art. 6(1)(c) and (f) |
| Service messages concerning the Account | s. 7(a) | Art. 6(1)(b) |
| Checking documents sent by Sellers and Providers, and applying the rules on which businesses, vehicles and drivers may be shown to Customers or take orders and bookings | s. 7(a), (d) | Art. 6(1)(b), (c) |
| Product scanning: reading the text on product photographs and counting the items in them, at the Seller's request, to fill in a Listing or a stock update | s. 6 (consent) | Art. 6(1)(a) |
| Territorial service configuration and regulatory discontinuance enforcement | s. 7(a), (d) | Art. 6(1)(c), (f) |
| Promotional communications | s. 6 (consent) | Art. 6(1)(a) |
7.2 The Operator may use data that has been anonymised so that it no longer identifies any individual, such as aggregated demand by area, to operate and improve the Platform.
8. Disclosure of Personal Data
8.1 The Operator does not sell, rent or trade Personal Data, does not disclose Personal Data for behavioural advertising, and does not disclose Personal Data to any credit information company or lender.
8.2 The Operator discloses Personal Data only to:
(a) other Users, to the extent necessary for a Transaction (including the pickup point, contact handle, display name, the Order Record and, during the Transaction, Location Data), for mutual location sharing, and as described in Clauses 5.4 and 8.3;
(b) HWF, where it is not the Operator, as Data Processor under Clause 1.3;
(c) Service Providers engaged under written contracts, being cloud hosting and encryption key management (Amazon Web Services), network protection and object storage (Cloudflare), and push-notification delivery (Google Firebase Cloud Messaging and Apple Push Notification service);
(d) map tile providers (OpenFreeMap and Esri), which receive the IP address of the device and the identity of the map tiles requested, but no account information or Location Data from the device's positioning system;
(e) Google (the Gemini API, a paid service), which receives the photographs a Seller chooses to scan, in order to read their text and count the items in them. Under Google's terms for its paid service, Google does not use them to train or improve its models, and keeps them only for a limited period solely to detect and prevent abuse of its service;
(f) courts, tribunals, government, law-enforcement and other competent authorities, as provided in Clause 14 of the Terms;
(g) professional advisers, auditors and insurers, under duties of confidentiality; and
(h) a successor to, or assignee of, the operation of the Platform (including a company formed by HWF or a licensed operator, as contemplated by Clause 24.2 of the Terms), which shall be bound by this Privacy Policy.
8.3 Personal Data received by Business Users. When a User places an order with, or accepts an Offer from, a Business User, that Business User receives the Personal Data needed to fulfil the order: the User's display name (unless the User has chosen to withhold it from a Request, until an order is made), the delivery or pick-up point, the telephone number if the User has furnished it, the order and its Order Record. The Business User may use such Personal Data only for the purposes permitted by Clause 9.11 of the Terms, and is responsible under Applicable Law for its use. A User who believes that a Business User has misused its Personal Data may report the matter to the Grievance Officer.
8.4 Following a store. A User who follows a store may receive promotional messages from that store through the Platform. The Seller does not thereby receive any further Personal Data of the User. The User may stop following the store at any time, whereupon such messages shall cease.
8.5 Customer Data Handled by Sellers. When a Customer places an order or initiates a transaction, the Seller receives the Customer's name, verified delivery address, telephone number, and transactional details.
(a) Strict Purpose Limitation: The Seller acts as an independent Data Fiduciary with respect to customer personal data delivered to it, and shall use such data solely for fulfilling the specific order, issuing mandatory commercial tax invoices, and complying with statutory accounting requirements.
(b) Prohibition on Unsolicited Marketing: The Seller is expressly prohibited from harvesting, exporting, selling, renting, or repurposing customer contact information (phone number, WhatsApp, email) for external promotional campaigns, unsolicited commercial communications, or sharing with third-party marketing networks, except where the Customer has explicitly opted to follow the store within the Platform.
(c) Secure Deletion: Physical delivery slips, printed waybills, or ephemeral notes bearing the Customer's telephone number or physical address must be disposed of or shredded once handover is completed and legal retention periods expire.
(d) Privacy Violations & Reporting: Customers may report unauthorized off-platform contact, spam, or harassment by a Seller to privacy@frilok.com or grievance@frilok.com. Substantiated violations will result in immediate suspension or permanent removal of the Seller's store from the Platform.
9. Transfer of Personal Data Outside India
9.1 Personal Data is stored principally on servers located in India. Certain Service Providers, including those providing push-notification delivery, network protection, object storage and the reading of product photographs (Clause 8.2(e)), may process Personal Data outside India.
9.2 Any transfer of Personal Data outside India shall be made in accordance with Applicable Law, including any restriction notified by the Central Government under Section 16 of the DPDP Act, and subject to contractual obligations requiring the recipient to protect the Personal Data.
10. Retention and Deletion
10.1 General principle. Personal Data is retained only for as long as necessary for the purpose for which it was collected or as required by Applicable Law, and is thereafter erased. Account data and active Listings, together with their Listing records (Clause 5.7), are retained for so long as the Account remains active or until the Seller deletes the Listing concerned. One-time passwords are deleted within fifteen (15) minutes, and transient matching data within twenty-four (24) hours. Photographs taken for a product scan are deleted from the Operator's storage as soon as the scan ends, and in any case within two (2) days. Any signed-in device (whether the main device or a linked device) that has not connected to the Platform for ninety (90) consecutive days is automatically signed out, its push-notification and call-notification tokens are deleted from the Operator's servers, and local Account data held on that device is cleared when the App on that device next connects; records of signed-out devices are deleted after ninety (90) days.
10.2 Location Data.
| Personal Data | Retention period | On expiry |
|---|---|---|
| Position during personal location sharing or in a Travel Together Session | While sharing continues | Deleted |
| Route so far and route ahead in a Travel Together Session (Clause 5.8(a)) | In the server's memory while the User shares in the session, and never written to its databases | Discarded when the User stops sharing, leaves the Group or the session ends |
| Record of a Travel Together Session: times, meetup point, who shared and for how long, whom the Group followed and when, and who travelled in which Travel Party and when, without positions or routes (Clause 5.8(d)) | For as long as the Group exists | Deleted with the Group; on the erasure of an Account, the records about that User are deleted and its name is removed from the records it set |
| Location history of personal sharing, only where the User has enabled "Location history" (disabled by default) | Not more than thirty (30) days; visible only to the User; stored in encrypted form | Deleted; the User may erase it at any time |
| Record of a share (parties, start and end time, without coordinates) | Ninety (90) days | Deleted |
| Live positions, route selected and route followed for a Tracked Order | Until completion or cancellation, and thirty (30) days thereafter | Deleted, save where a dispute, safety incident or request of an authority concerning the Transaction is pending, in which case until its conclusion |
| Provider's current position | While location sharing for work is enabled | Continuously replaced; not retained as history |
| Provider's last known position after going offline | Not more than two (2) hours | Deleted |
| Position of a vehicle displayed with its Listings (Clause 4.4A) | While displayed | Not retained; no history is created |
| Transaction records, including Order Records, recorded payments, disputes and the evidence attached to them (parties, amounts, dates; without route) | The period prescribed by tax and accounting law for the country of the Transaction, from its close (Schedule A.5 for India) | Deleted, save where a dispute or a requirement under Clause 10.5 still needs them; after the erasure of an Account, reduced first as stated in Clause 10.3(e) |
| Reports and complaints made by or concerning a User whose Account is erased | The period in the Schedule for the User's country, from their decision (Schedule A.5 for India) | Deleted, with their photos |
| Seller payment particulars and the record of their changes | For as long as the Seller keeps them; earlier particulars, for as long as the Account exists, so that a question about where a payment was sent can be answered | Deleted on erasure of the Account |
| Anonymised aggregated data | Indefinitely | Not Personal Data |
10.3 Deletion of Account. Upon a request under Clause 16 of the Terms:
(a) Closing. The Account is closed to new business at once: no new Transaction, Listing, offer or request may be made with it, its Listings, store and vehicle are no longer shown, and orders not yet accepted are cancelled. Where nothing remains open under paragraph (b), the Account is also switched off at once: the User is signed out on every device, notifications to the User's devices stop, the User's live position is removed and the User can no longer be found in people search. No Personal Data is erased during the closing period stated in the Schedule for the User's country (Schedule A.5 for India). If the User signs in during that period, the User may keep the Account, which then continues as before; otherwise erasure follows as stated in paragraph (b);
(b) Open Transactions, disputes and complaints. While a Transaction to which the User is a party has been accepted but not completed, or a dispute, complaint or appeal concerning one has not been decided, the Account remains usable for the sole purpose of completing it (Terms, Clause 16.3). The other party is told at once that the User is closing the Account and is reminded; a Transaction it neither completes, cancels nor raises a problem about within the reply period in the Schedule is closed as it stands. Erasure takes place once nothing remains open and the closing period has elapsed, and in any event at the end of the longest period in the Schedule, save where Clause 10.5 applies. Personal Data needed to complete or decide these matters is processed only for that purpose, and the Operator does not keep any matter open in order to delay erasure. A report by another User that does not concern a Transaction does not hold erasure. The same applies where an Account is erased otherwise than at the User's request;
(c) What is erased. The User's profile, contacts and friend requests, the links under Clause 3.7, server-side messages, group memberships, Location Data (including saved routes, trips and location history), statuses, Listings, shop details, vehicle and the documents sent for a check (Terms, Clause 5.2), reviews and ratings given or received, the verified telephone number and the records of one-time passwords sent to it, settings and devices, and the photos and files uploaded by the User, together with any copy prepared under Clause 12.2. The keys with which the User's archived messages, location history and trips are encrypted are destroyed upon erasure, whereupon any copy of that data remaining in a backup can no longer be read; backup copies of those keys are kept for not more than thirty (30) days;
(d) What remains with others. Messages, photos and files that the User sent in a conversation or a group remain with the persons who received them, without the User's profile. A copy of a message held in the archive of another participant in the conversation is not affected. A photo or cover uploaded by the User for a group that continues remains with that group;
(e) What is kept. Records of Transactions to which the User was a party (with their payments, disputes and adjustments and the evidence attached to them), platform fees, and reports and complaints made by or concerning the User are kept for the periods stated in the Schedule for the country of each record (Schedule A.5 for India), and then deleted with their photos, unless a dispute or a requirement under Clause 10.5 still needs them. On erasure, the record of a completed Transaction is reduced to what the law requires: exact positions, routes, delivery notes and position trails are removed. Kept records are open only to the other party to the Transaction, in its own order history, where the User is shown as a former Frilok user with the name under which the order was placed, and to Frilok staff who record the reason for each viewing. Basic account information is kept for one hundred and eighty (180) days after closure where required under the IT Rules; records of the User's location consents for thirty (30) days after erasure, or for such longer period as Applicable Law requires, as evidence that consent was obtained; and the User's Frilok ID, solely so that it is never issued to another person. These are used only for those purposes;
(f) records preserved at the request of a competent authority shall be retained as provided in Clause 14.4 of the Terms; and
(g) public place records contributed by the User may remain on the Platform but shall be dissociated from the User.
10.4 A request for deletion may be made in the App
(Me → Privacy and safety → Delete account) or by e-mail to
privacy@frilok.com from the e-mail address or telephone
number registered with the Account.
10.5 Data preserved for an authority. Where a competent authority has required the Operator to preserve Personal Data, that data is not erased, whether at the User's request, through a setting of the App or at the end of a retention period, for so long as the requirement lasts, and is used for no other purpose (Clause 14.4 of the Terms). During that period a request to delete such data may be declined without the reason being given where Applicable Law does not permit it to be disclosed.
11. Rights of Data Principals
11.1 Subject to Applicable Law, a User has the right to:
(a) obtain a summary of the Personal Data processed and the processing activities undertaken, and the identities of the persons with whom it has been shared;
(b) the correction, completion, updating and erasure of Personal Data;
(c) withdraw consent at any time;
(d) nominate another individual to exercise these rights in the event of the User's death or incapacity;
(e) receive a copy of the Personal Data processed about the User, as provided in Clause 12.2; and
(f) have grievances redressed in accordance with Clause 17.
11.2 Requests may be made through the App or by
e-mail to privacy@frilok.com. The Operator may take
reasonable steps to verify the identity of the person making a request,
and shall respond within the period prescribed by Applicable Law, being
not more than ninety (90) days under the DPDP Rules.
11.3 Additional rights applicable in other Designated Territories are set out in the relevant Schedule.
12. Privacy Controls
12.1 The App provides the following controls under Me → Privacy and safety, those concerning Location Data being on its Location & Map screen:
(a) a privacy check-up displaying, and permitting the User to change, the persons who may view the User's Location Data, pending invitations and requests, background sharing and location-history settings, profile visibility, message-history settings, blocked Users and device permissions;
(b) "Keep sharing in the background", disabled by default;
(c) "Location history", disabled by default;
(d) "Erase data", which deletes the Location Data associated with the User, including saved routes, from the Operator's servers and from the device, save as provided in Clause 10.5; and
(e) "Let people who have my number find me on Frilok", enabled by default; turning it off deletes the links under Clause 3.7.
12.2 Download your data. Under Me → Privacy and safety → Download your data, a User may obtain a copy of the Personal Data that the Platform keeps about the User. The copy is prepared on the Operator's servers, usually within a few minutes, and comprises:
(a) a page that can be read in any web browser, in the language of the App;
(b) the same data in a structured, commonly used and machine-readable format (JSON); and
(c) the photos and files uploaded by the User, up to two hundred (200) megabytes in total, the remainder being listed with the address at which each may be retrieved.
Messages, location history and trips stored in encrypted form are decrypted for this purpose with the User's own keys. Passwords, one-time passwords and security tokens are not included. The User is notified when the copy is ready. It may be downloaded through a private link for seven (7) days, after which the copy is deleted. One copy may be requested each day. A copy is for the User's own records and cannot be used to restore an Account or its data.
13. Children
13.1 The Platform is not directed to persons under
eighteen (18) years of age, and the Operator does not knowingly process
their Personal Data. Upon becoming aware that an Account belongs to such
a person, the Operator shall delete it. Any person who believes that a
child has registered an Account may notify
privacy@frilok.com.
14. Security Safeguards
14.1 The Operator implements reasonable security practices and procedures, and technical and organisational measures appropriate to the nature of the Personal Data, as required by Section 43A of the Information Technology Act, 2000, the SPDI Rules and Section 8(5) of the DPDP Act, including:
(a) encryption of data in transit, and of call content by DTLS-SRTP, and encryption at rest of archived messages, messages held for delivery and saved location history, with the encryption keys protected by a hardware-based key management service and stored separately from the data;
(b) storage of authentication credentials only in protected, non-reversible form;
(c) restriction of internal services to private networks, and access controls limiting access to Personal Data to authorised personnel on a need-to-know basis;
(d) storage of authentication tokens on devices in the platform's hardware-backed secure storage; and
(e) logging of access to Location Data.
14.2 No method of transmission or storage is completely secure, and the Operator cannot guarantee absolute security.
15. Personal Data Breach
15.1 In the event of a Personal Data Breach, the Operator shall, as required by Applicable Law, intimate each affected User without delay, describing in clear and plain language the nature and extent of the breach, its likely consequences, the measures taken or proposed to mitigate the risk, the safety measures the User may take, and the contact details of a person able to respond to queries, and shall report the breach to the Data Protection Board of India and any other competent authority within the prescribed period.
16. Amendments
16.1 The Operator may amend this Privacy Policy from time to time. The amended Privacy Policy shall bear a revised version number and effective date. Material amendments shall be notified to Users before they take effect, through the App, by notification to the User's device, by e-mail or by SMS, and consent shall be sought afresh where Applicable Law so requires.
17. Grievance Officer and Contact
17.1 Questions, requests and complaints concerning the processing of Personal Data may be addressed to the Grievance Officer:
Grievance Officer: Anurag Kachary, Manager-Customer
Service & Grievances, High Way Fresh
Address: Sonapur, Kamrup (Metro), Assam. PIN:
782402
E-mail: anurag@frilok.com (privacy
requests: privacy@frilok.com)
17.2 The Grievance Officer shall acknowledge and dispose of complaints within the periods specified in Schedule A to the Terms. A User who is not satisfied with the resolution of a grievance relating to Personal Data may, upon exhausting this procedure, file a complaint with the Data Protection Board of India, whose decisions are appealable to the Telecom Disputes Settlement and Appellate Tribunal.
18. Applicable Law and Territorial Scope
18.1 The Platform is offered only in the Designated Territories specified in Clause 22.2 of the Terms, currently India. The processing of the Personal Data of a User is governed by the data protection law specified in the Schedule applicable to the Designated Territory in which the User is ordinarily resident.
18.2 Schedules B, C and D shall apply only upon the Platform being offered in the territories to which they relate. Before the Platform is offered in any other country or territory, the Operator shall add or complete the Schedule for it. The Platform is not directed to persons outside the Designated Territories; nothing in this Clause shall exclude any protection conferred by mandatory law.
Schedule A — India
A.1 Legislation. The Information Technology Act, 2000 and the SPDI Rules (which continue to apply until the commencement of the corresponding provisions of the DPDP Act); and the DPDP Act and the DPDP Rules, notified on 13–14 November 2025 and coming into force in phases, the substantive obligations of Data Fiduciaries applying from May 2027. The Operator applies the standards of the DPDP Act and the DPDP Rules from the effective date of this Privacy Policy.
A.2 Data Fiduciary. High Way Fresh, Sonapur, Kamrup (Metro), Assam. PIN: 782402.
A.3 Grievance Officer. As specified in Clause 17.1.
A.4 Data Protection Board. Complaints may be filed with the Data Protection Board of India through its online platform after exhausting the grievance procedure in Clause 17.
A.5 Deletion of Account and records kept (Clause 10.3). Closing period: thirty (30) days from the request. Reply period for the other party to an open Transaction: seven (7) days, with reminders on the third and sixth days. Longest period: ninety (90) days from the request. Records of Transactions, with their payments and disputes: eight (8) years from the close of the Transaction. Platform fees: eight (8) years. Reports and complaints: three (3) years from their decision. Basic account information: one hundred and eighty (180) days. Records of location consents: thirty (30) days.
Schedule B — European Union and European Economic Area
(Applicable only upon the Platform being offered in the EU/EEA.)
B.1 The Operator shall act as controller under Regulation (EU) 2016/679 (the "GDPR") and shall designate a representative under Article 27 before the Platform is offered in the EU/EEA.
B.2 A User has the rights of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and objection (Art. 21), and the right not to be subject to a decision based solely on automated processing producing legal or similarly significant effects (Art. 22).
B.3 Transfers of Personal Data outside the EEA shall be made on the basis of an adequacy decision or the Standard Contractual Clauses adopted by the European Commission, together with supplementary measures where required.
B.4 A User may lodge a complaint with the supervisory authority of the Member State of habitual residence, place of work or place of the alleged infringement.
Schedule C — United Kingdom
(Applicable only upon the Platform being offered in the United Kingdom.)
C.1 The Operator shall act as controller under the UK GDPR and the Data Protection Act 2018 and shall designate a representative in the United Kingdom before the Platform is offered there.
C.2 A User has the rights described in paragraph B.2, under the UK GDPR.
C.3 Transfers of Personal Data outside the United Kingdom shall be made on the basis of adequacy regulations, the International Data Transfer Agreement, or the UK Addendum to the Standard Contractual Clauses.
C.4 A User may lodge a complaint with the Information Commissioner's Office.
Schedule D — United States
(Applicable only upon the Platform being offered in the United States.)
D.1 The Operator does not sell Personal Data or share it for cross-context behavioural advertising.
D.2 Precise geolocation is processed only to provide the features requested by the User (Clause 4) and is not used to infer characteristics about the User.
D.3 Residents of California and other States with
comprehensive privacy legislation may exercise the rights to know,
delete and correct Personal Data and to limit the use of sensitive
personal information by e-mail to privacy@frilok.com,
directly or through an authorised agent. The Operator shall not
discriminate against any User for exercising such rights.
Privacy requests: privacy@frilok.com.
frilok