Franco Food logoFranco Food Download

Privacy Policy

Effective Date: October 23, 2026  ·  Last Updated: November 1, 2026

This Privacy Policy applies to all mobile applications developed and operated by SgtWarfare LLC (“we,” “our,” or “us”), including Franco Food, Franco Drive, Franco Business, and any additional services such as taxi and ride-hailing services (collectively, the “Franco App”). By downloading, accessing, or using any Franco App service, you consent to the collection, use, and disclosure of information as described in this Privacy Policy.

1. Information We Collect

We may collect the following categories of information:

1.1 Personal Information

Name, email address, phone number, delivery or pickup address, payment-related details, resume/CV information you provide to our AI resume builder, and content and photos you publish in listings.

1.2 Account Information

Login credentials, profile details, business registration information, driver identification data, vehicle information, and verification documents.

1.3 Transaction and Service Data

Orders placed, ride or taxi requests, completed deliveries or trips, cancellations, fares, fees, commissions, and sales history. This includes scheduled trips accepted, cancellations, and no-shows. This includes customer cancellations of scheduled trips or orders, including the card payment method, the amount retained, and the amount refunded. This includes a scheduled food order that could not be fulfilled because no driver took it after the accepting driver cancelled, including the full refund to the customer and the 10% payment to the business paid by the platform.

1.4 Device and Usage Data

IP address, device identifiers, operating system, app version, log files, and usage analytics.

1.5 Location Data

Real-time and approximate location data collected only when necessary to provide deliveries, taxi services, ride tracking, navigation, fraud prevention, or customer support.

2. How We Use Information

We use collected information to:

3. Information Sharing and Disclosure

We do not sell or rent personal data. Information may be shared only as necessary with:

4. Payments and Remitly Processing

Payments and payouts may be processed through third-party providers, including Remitly.

Remitly payments are available only for Franco Drive drivers and Franco Business vendors, primarily for users located outside the United States.

When using Remitly, certain personal and financial information may be shared with Remitly in accordance with their privacy policy, verification requirements, and applicable financial regulations.

SgtWarfare LLC does not control Remitly’s data practices and is not responsible for delays, fees, exchange rates, or processing decisions imposed by Remitly or intermediary institutions.

5. Cancellations and Pricing Data

We collect and process data related to order, ride, and taxi cancellations, including time, location, zone, and usage patterns. This data is used to:

For scheduled trips, we also collect and process data about scheduled trips accepted, cancellations, and no-shows, including the scheduled date and time, city, type (food or taxi), and reason, such as not opening the app within 5 minutes of the 30-minute notice, or a late cancellation with 1 hour or less remaining. This data is used to apply the scheduled trips policy, count Strikes, notify the driver by notification and email, improve reliability, and enforce the rules. No new category of personal data beyond those already listed in Section 1 is collected for this purpose. Strike records are retained as transaction and cancellation records.

For customer cancellations of scheduled trips or orders, we also process the card payment method, the amount retained (30%) and the amount refunded (70%), to apply the cancellation policy, process the partial refund, and pay the driver, business, and platform as applicable. No new category of personal data beyond those already listed in Section 1 is collected for this purpose.

Pricing, fares, and cancellation fees may vary by geographic zone, demand, time, and operational conditions.

For a scheduled food order that cannot be fulfilled because the driver who accepted it cancelled and no other driver took it before the scheduled time, we also process the full refund (100%) to the customer and the 10% payment to the business, paid by the platform. No new category of personal data beyond those already listed in Section 1 is collected for this purpose.

6. Data Retention

We retain personal information only as long as necessary for legitimate business and legal purposes:

7. Data Security

We use commercially reasonable and industry-standard safeguards, including encryption, secure servers, access controls, and monitoring systems.

Despite these measures, no electronic transmission or storage system can be guaranteed to be completely secure.

8. User Responsibilities

By using the Franco App, users agree to:

9. App-Specific Privacy Practices

Franco Food - Customer data is collected to process and deliver orders - Payment details are encrypted and not shared with drivers or businesses - Accurate delivery information is the customer’s responsibility

Franco Drive (Delivery, Taxi, and Ride-Hailing) - Driver data (identification, vehicle details, location, and payment information) is collected to enable services and payouts - Location data is required during active deliveries or trips - Drivers must not share, rent, or sell their accounts - Drivers must comply with traffic, safety, and local regulations

Franco Business - Business registration data, catalogs, pricing, and transaction history are collected - Businesses are responsible for maintaining accurate menus and availability - Sales and order data may be used for reporting, payouts, and compliance

10. Children’s Privacy

Franco App services are not intended for individuals under the age of 18. We do not knowingly collect personal data from minors. If such data is discovered, it will be deleted promptly.

11. International Data Transfers

Your information may be transferred to, processed, and stored on servers located outside your country of residence.

By using the Franco App, you consent to such international data transfers in accordance with applicable law.

12. User Rights

Depending on your jurisdiction, you may have the right to:

Requests may be submitted to team@francoapp.com. Verification may be required.

13. Live Selling

Businesses may broadcast live video to promote products and interact with viewers (“Live Selling”). When you watch or participate in a live session, we may process viewing activity and interactions (such as comments and reactions) to operate the feature and keep the platform safe. Businesses are responsible for the content they broadcast.

14. Jobs, Rentals & Classified Listings

When you publish a listing for a job, rental, or classified ad, the information you provide — including title, description, photos, price, and any contact details you choose to share (such as phone number, email, or WhatsApp) — is made visible to other users of the app and website. Listings expire after seven (7) days and are removed, except official Franco Food announcements. Do not include sensitive personal information in public listings.

15. AI Resume Builder

If you use our AI resume builder, we process the information you provide — such as name, contact details, work history, education, skills, and photo — to generate your resume. At your direction, the resume may be shared with employers via WhatsApp or email. AI-generated content may contain inaccuracies; you are responsible for reviewing your resume before sharing it.

16. Reviews and Ratings

When you submit a review or rating for an order, driver, business, or support agent, your score and comment are stored in connection with the relevant order or interaction and may be shown to the business, driver, or support team involved.

17. Push Notifications and Marketing Communications

We send push notifications through Firebase Cloud Messaging (FCM); your device notification token is stored so we can deliver them. Businesses with an active notification subscription may send promotional notifications to their followers and to users in their city. We may also send service-related emails — such as order updates, security alerts, and legal notices — to the email address on your account. You can manage notification preferences in the app settings. You can also unsubscribe from marketing emails at any time using the link included in every marketing email; unsubscribing does not stop transactional or service emails.

18. Subscription Data

When a business purchases or manages the “Franco Food Business Monthly” subscription, we receive and store the subscription data needed to operate it, including purchase tokens, transaction identifiers, subscription status (active, expired, canceled), and the country and currency of the purchase.

We verify subscription purchases and renewals directly with Apple, Google, or Stripe servers. We do not receive, process, or store your full card details; payments are processed entirely by Apple, Google, or Stripe under their own privacy policies.

Subscription records are retained while the subscription is active and thereafter for the period required by applicable legal, tax, and accounting obligations.

19. Advertising Measurement (Meta Pixel & Conversions API)

If — and only if — you grant consent in the app/website privacy controls, we collect and share with Meta Platforms, Inc. the following event data: the action you took (viewing a store or product, adding an item to the cart, starting checkout, completing a purchase or registration, booking a taxi), the event time, the city, the order value and currency, and product/order identifiers. To match events to your Meta account, identifiers such as your user ID, email address, or phone number are hashed (SHA-256) on our servers before transmission — Meta does not receive them in plain text from our server events. Browser events use Meta's first-party cookies (fbp/fbc) where you have consented.

20. Why We Share This Data

To measure whether our advertising works, build audiences of people similar to our customers, show Franco Food ads to people likely to be interested, and avoid showing ads for things you already bought. We do not sell your personal information.

21. Personalization Inside Franco Food

We use your own Franco Food activity (stores you ordered from, product categories, your city and language) to order the home-screen store list for you — for example, showing stores you have ordered from before, and open stores, earlier. This processing happens with Franco Food's own data; your segment (for example "new", "active", "frequent", or "dormant" customer, computed from your order history) may also decide which Franco Food announcements you see inside the app. Segments are labels we compute; they are never sold.

22. AI-Assisted Pricing Data

For taxi trips and food deliveries, our system may use aggregate, real-time demand signals (number of ride requests or orders, drivers online, completion rates in a city) to adjust prices within the limits published for the city (see the Terms of Service). We do not set your individual price based on your identity, device, payment method, or how much we think you personally would pay. The fare or delivery fee quoted before you confirm is the fare or fee you pay.

For in-app disputes, we store the order reference, the reason and description you provide, the amount you request, the decision, any refund granted and its method (Wallet or card), and the dispute history. This data is visible to you, to our support team, and to the platform administrator, and is retained as a transaction record under Section 6. If you open a payment dispute with your card network (a Stripe dispute), we prepare the evidence and response draft for manual review by the administrator; nothing is sent to Stripe automatically.

23. Your Choices (Opt-Out / Consent)

24. Retention & Processors

Event data is sent to Meta and retained under Meta's policies. Segment labels are recomputed periodically from your order history and stored with your account. Payment data continues to be handled only by Stripe (see the main policy above).

25. Changes to Sections 19–24

Material changes to these sections will be announced by email and in-app/push notification before they take effect, per our standing commitment in Section 28.

26. Package Shipping & API Data

This section describes what data we collect, use, and share when the Franco Package shipping service or the Franco Food API is used. It supplements the other sections of this Policy, including those on location, use of information, retention, and user rights, which also apply to package shipping.

26.1 Shipment data

When an individual or a business creates a shipment or a route, we collect and store:

a) The pickup and delivery addresses for each stop, together with any location references provided.

b) The name and phone number of the recipient for each stop and the name and phone number of the sender (the individual or business sending the package), as well as the contact details of the pickup point where they are different.

c) Each package's dimensions (length × width × height), weight, and declared value, and the label associated with each stop (stop number and recipient's name).

d) Photos of the packages: a photo at pickup and a photo when delivery is confirmed, where the confirmation method includes them. The photos serve as evidence of pickup and delivery.

e) The delivery codes generated for each stop and the record of their use to confirm delivery.

f) The status of each stop and of the route (created, picked up, in transit, delivered, not delivered, pending return, returned, or not returned), with dates and times.

We use this data to create and price the route, assign a driver with a capable vehicle, coordinate pickup and delivery, confirm delivery, manage returns, handle loss or damage claims, and prevent fraud or abuse.

26.2 Real-time driver location during the shipment

During an active shipment or route, we collect the driver's real-time location, as with the delivery and taxi services described in this Policy. This location is used to track the route, calculate estimated times, coordinate each stop, and keep the parties safe.

The driver's real-time location may be seen only during the active shipment by:

a) The sender (the individual or business sending the package), from the app or panel, to follow progress stop by stop.

b) The recipient, if the recipient receives a tracking link for the shipment, only for the recipient's own stop and while that delivery is in progress.

c) The Franco Food administrative team (admin), for operations, support, and safety.

Once the route ends, the location is no longer shown in real time to the sender or the recipient. The route history is kept as described in Section 26.7.

26.3 Data shared with the assigned driver

So the delivery can be completed, we share with the driver assigned to the route, and only during the active shipment:

a) The recipient's name, address, and phone number for each stop.

b) The name, address, and phone number of the pickup point (the individual or business sending the package).

c) The operational data for each stop: stop number, label, declared dimensions and weight, confirmation method (code or photo), and any delivery instructions provided.

The driver does not receive the full payment details of the sender or the recipient. When the route ends, the driver no longer has access to that shipment's contact details in the app, without prejudice to the records Franco Food keeps under Section 26.7.

26.4 Chats and ratings linked to the shipment

a) During an active route, the sender and the driver can communicate through the in-app chat linked to that shipment. We store the content of those chats together with the shipment history, for operations, support, safety, and dispute resolution.

b) Post-chat and post-shipment ratings (for example, a rating of the driver, of the delivery experience, or of the chat service) are also stored together with the shipment history and may be shown to the parties involved and to the administrative team, as described in the reviews and ratings section of this Policy.

26.5 API data

When a business uses the Franco Food API, we collect and store:

a) Credentials in protected form: we store API keys only as a hash (a cryptographic digest). We do not store the full key in plain text after it is issued, so a lost key cannot be recovered: it must be revoked and a new key issued.

b) Usage logs: the date and time of each request, the operation performed, the shipments or stops created or queried, error responses, counts used to enforce rate limits, and the address and technical connection data needed for security and abuse prevention.

c) Webhooks: the receiving address configured by the business, the events sent, the date and time of sending, and the delivery result of each webhook.

d) Data of shipments created by API: the same data as in Section 26.1, because an API shipment follows the same rules as a shipment created in the app or the panel.

The business is responsible for the personal data it transmits from its own website or system through the API: it must have a valid basis for sharing it (for example, consent or its own customer relationship), must transmit only the data needed for the shipment, and must keep its customers informed under its own privacy policy. Franco Food processes that data only to provide the package shipping service and in accordance with this Policy.

26.6 Returns data

When a package is not delivered, we store the return history associated with that shipment: the recorded reason for the failed delivery, the date and time the package became pending return, the applicable deadline (before 11:00 AM on the following day, local time of the city), the sender's confirmation (returned / not returned), and the condition in which the package was reported as returned.

This history is associated with the driver's account and with the sender's account, and is used to operate the returns process, maintain the driver's count of unreturned packages, apply the measures provided in the Terms (account at risk or suspension from the package shipping service), handle disputes, and prevent abuse.

26.7 Retention of shipment records

We retain shipment and route records (shipment data, statuses, delivery evidence, linked chats and ratings, return history, and API usage logs) for twelve (12) months from the date of the shipment. After that period, we delete or anonymize them, unless a legal obligation or an open dispute, claim, or investigation requires us to keep specific records for longer, in line with the general retention section of this Policy.

Pickup and delivery photos are kept associated with the shipment for that same twelve (12) month period, as evidence that the service was provided. When records are no longer necessary or required by law, we will delete or anonymize them.

The rights of access, correction, deletion, and withdrawal of consent described in this Policy also apply to package shipping and API data, subject to the limits imposed by applicable law for retaining transaction records.

27. Gift Cards, Bonuses and Campaign Data

When you buy, receive, or use a Franco Food gift card, we process the purchase and redemption data needed to operate it: the card identifier, the amount and currency, the purchase and redemption history, and the remaining balance. Gift card payments are processed by our payment providers as described in Section 4; we do not store your full card details.

When we grant bonuses or other promotional benefits to drivers or customers, we record in the associated account the type of benefit, its conditions, its amount, and its expiration date, so that we can apply it, prevent abuse, and honor its terms.

Announcements shown in the app and on the website may be targeted by city and by customer segment, as described in Section 21. To operate campaigns we process which announcements were shown to an account and the interactions with them (for example, views or taps), together with the city and segment data already described in this Policy. We do not sell this data.

28. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we make material changes, we will notify you by email and by push notification in the app before the changes take effect, including a summary of the changes and links to read the full text. Updates will also be published within the app and on our website. Continued use of the Franco App after the effective date constitutes acceptance of the revised policy.

29. Contact Information

SgtWarfare LLC
Louisville, Kentucky, USA
Email: team@francoapp.com
Phone: +1 502-701-7573