Privyrides
Privacy Policy
PRIVYRIDES TECHNOLOGIES INC. · Version 2.4.3 · English
1. Scope and responsibilities
This Policy explains how PRIVYRIDES TECHNOLOGIES INC. ("Privyrides", "we" or "us") processes personal information through its websites, applications, business tools, booking and payment integrations and Client View. It covers account holders, guests, passengers, business representatives and people whose information a Provider enters into the software. A "Provider" is the independent business offering or arranging the transportation identified in a booking.
Privyrides determines how information is used for platform accounts, security, support and its own administration. Providers determine how they use information for their business and transportation relationships, and may instruct Privyrides to process information through the tools. The parties' legal roles depend on the particular processing and applicable law. A Provider's independent activities and third-party websites are covered by their own notices. Accepting terms is not blanket consent to every processing activity described here.
2. Information we receive
Account and business information includes names, contact details, sign-in identifiers, business names, account roles, preferences, invitations and relationships with Providers. Business users may supply photographs, descriptions, vehicle and service information, commercial coverage, documents and declarations about licenses, insurance or other credentials. We distinguish a declaration, an uploaded record and a review result; none is treated as universal permission to operate.
Booking and service information includes addresses and coordinates, dates and times, itinerary, requested service, passengers and luggage counts, instructions, pricing, acceptance and status changes, invoices, cancellations, refunds, reviews and communications. A customer or Provider may enter information about someone else. Avoid unnecessary health, identity or other sensitive information in free-text instructions. Accessibility information supplied for a particular service can reveal sensitive details even when we do not specifically request a medical history.
Payment records include transaction identifiers, amounts, currency, payment status, fees, refunds and the limited payment-method information returned by the processor. Stripe collects card, bank and identity information in its payment or onboarding interfaces. Privyrides does not store complete payment-card numbers; it stores identifiers and records needed to connect a payment to the correct account and service. A processor may independently collect fraud, device and identity information under its own policy.
Technical and usage information includes IP addresses received by our servers, session and device-connection identifiers, browser or device category, error and access records, feature activity and security events. Signed-in mobile diagnostics can include platform, application version, build and last activity. This diagnostic feature does not require a hardware identifier. Legal or optional-authorization records can include the document or notice shown, version, language, action and server time. These records serve different purposes from advertising permission.
Mileage Tracking information can include vehicle labels and identifiers, default or archived status, dated entries, origins and destinations, business purpose, personal or commuting categories, distance and its source, odometer readings, annual summaries, evidence notes, corrections and prior revisions. We process these account records to provide mileage tracking, statistics, reconciliation and requested reports. A route estimate or entered odometer reading is not proof of continuous device-location collection. Mileage records are account information, not public Network content. A subscription change does not itself delete those records; available access and export functions depend on the applicable entitlement. Retention and deletion follow the provisions below, not a promise of indefinite storage.
3. Sources of information
We receive information directly from you; from the Provider, booker or authorized business user who enters it; from your use of the services; and from integrations you or an authorized business user connect. Payment services return transaction and eligibility information. Google integrations return permitted account, business and review data. An external verification integration, when separately available and authorized, may provide a bounded status or evidence about its specific subject. The presence of integration code does not mean a background check is performed on every user. For a stated review, we may receive information from an issuing authority, insurer, authorized representative or other appropriate source where access is lawful. We must identify the scope of the review and use the information consistently with its purpose and applicable rights.
4. Purposes of processing
Company–customer acquisition records may identify the source of a relationship, relevant referral or booking evidence, attribution corrections and the commission-policy version used for a transaction. We use these records to calculate and explain fees, reconcile payments and review incorrect attribution. Acquisition classification does not change who provides transportation, make a customer or their information our property, or replace the legal basis needed for marketing or other data use. A relationship with one company does not by itself establish acquisition for every company.
We use information to create and secure accounts; manage Provider and customer relationships; display profiles and requested public content; calculate and communicate quotations; process bookings, invoices and payments; share authorized trip information; deliver Client View; provide support; record preferences and agreements; and maintain the software. We also use relevant information to investigate fraud, reconcile financial records, enforce legitimate access rules and meet legal obligations.
We use limited first-party marketplace analytics to understand visits, profile views, quotation activity and booking requests. These events use random browser and session identifiers, campaign attribution, referral domain, device category and relevant Provider or market identifiers. Their designed payload excludes booking form contents, names, emails, telephone numbers, precise trip addresses and payment details. Random identifiers are not a promise that data is anonymous. Operational records for the underlying booking are separate and can contain personal information.
Where applicable law requires a legal basis, processing may be necessary for the requested service or contract, a legal obligation, a legitimate operational interest balanced against your rights, or your consent. Optional uses that require consent must have an appropriate separate choice. We do not treat the existence of a privacy notice as your authorization for an unrelated purpose.
Where a Provider requests public participation, we may use relevant declarations, supporting records and review results to assess eligibility, describe checked facts, correct misleading information and handle reports or appeals. A public statement must reflect its actual source, scope and date. Supporting identity and insurance files are not automatically public; only appropriate information about a stated review may be displayed. We must minimize unnecessary personal information and protect retained evidence. The Privy Network Terms describe participation and review responsibilities; they are not blanket permission to disclose documents.
5. Location, maps and tracking
Trip addresses and coordinates are processed for search, pricing, routing, service coverage and the booked service. Device location is used when you permit the relevant feature. You can change device permissions, though a feature depending on them may become unavailable. Location information entered by a booker or Provider is separate from device permission.
Marketplace state detection uses server-side IP and geographic boundary datasets. Address suggestions and validation use Google Places through our server; Google receives the query and relevant search context, such as a general state viewport. Routing, geocoding and time-zone services can receive the coordinates or addresses necessary for their function. The absence of forwarded device GPS in one address-suggestion request does not mean no location data is ever sent to a mapping service.
Where trip tracking is available, the driver's location and estimated arrival are shared with authorized participants for the relevant trip and status. Tracking access is limited by account and trip context; it is not a public authorization to follow the driver indefinitely. Maps and estimates may be incomplete or inaccurate. We do not need continuous passenger tracking merely to determine commercial service coverage.
6. Who receives information
The selected Provider receives information needed to evaluate and perform the request and administer its customer relationship. An authorized collaborator can receive the trip information necessary for its role. Public profiles and published reviews are available to visitors, including people outside your region. A receipt, invoice or payment link can expose the information designed for its holder; share such links only with intended recipients.
We use infrastructure, storage, communication, mapping, payment, support and other service providers for their functions. They receive information necessary for the service and subject to the relevant arrangement; some, including payment and mapping providers, also act independently under their own notices. Authorized Privyrides personnel can access relevant information for support, administration, security or legal duties. We do not promise that we have no technical access to information processed by the platform.
We may disclose information when legally required, to protect rights and safety, to investigate wrongdoing, or in a business reorganization subject to applicable protections and notice. We do not operate the described service by selling customer lists or permitting unrelated advertising uses of Google integration data. Any materially different use must be assessed and disclosed with the choices required by law before it begins.
7. Google Business Profile and reviews
When an authorized business user connects Google, we access the permitted account identity, managed business profiles and reviews for the selected business. Reviews may contain author names, photos, ratings, text, dates and business responses. We display them with Google attribution on the Provider profile and review embeds, separately from Privyrides trip reviews. Google authorization may describe broader business-management permissions; this integration reads the selected data and does not edit the business or reply to reviews.
Access and refresh tokens are stored encrypted. Review caching is designed to refresh within short intervals, with a cleanup process for reviews older than 24 hours and business display metadata older than 29 days. Cleanup runs periodically; these thresholds are not a promise of instantaneous removal from every backup at the exact threshold. Technical identifiers needed to maintain the authorized connection can remain while the connection is active.
Disconnect through Public Profile → Google reviews to stop access and remove the stored connection credentials and cached content from Privyrides. This does not delete reviews at Google. Completed account deletion also removes the account's stored Google connection. We do not use this integration's data for advertising, resale or disclosure to commercial collaborators. Google processes data under its Privacy Policy, and its platform rules apply to the integration.
8. Cookies, local storage and shared devices
We use session cookies and similar storage for sign-in, security, language, account preferences and operation of the application. The application may cache interface assets and permitted content on the device. First-party marketplace analytics uses local and session storage identifiers; the analytics feature honors the browser's Do Not Track signal. This does not stop the separate security or transaction records necessary to operate a requested service.
You can control cookies, storage and permissions through browser and device settings. Blocking or clearing them may sign you out or affect saved settings. On a shared passenger display, use the Provider's passenger mode and avoid entering unnecessary private information. Device pairing, access leases and exit controls help limit access; the Provider is responsible for operating the device appropriately and clearing access between users. Third-party links or payment interfaces can use their own technologies and policies.
9. Communications and choices
We and Providers send relevant service communications about bookings, security, billing and support. Where optional promotional communications require consent, that choice is separate from service terms. Marketing messages provide the applicable unsubscribe method. Withdrawing from marketing does not stop essential notices about an existing transaction or security issue.
In-app messages may record when a notice was shown and whether you acknowledged, accepted, refused, dismissed or selected "Don't show again". Closing an authorization request or choosing "Later" is not consent. Such a response does not grant device permission or connect an external account by itself. You can manage push notifications through device settings. You should contact a Provider directly about marketing that it sends independently.
10. Retention and deletion
We retain information for the periods reasonably needed for the purpose for which it was collected, account and service administration, security, legal compliance, accounting and dispute resolution. Relevant factors include the record type, whether a booking or payment remains open, limitation periods, legal holds, integration policies and legitimate audit needs. We do not impose one indefinite retention period on every category in this Policy.
Account deletion may remove or anonymize account identifiers while preserving shared transportation, financial, fraud-prevention or legal records that remain necessary. A Provider or processor can have independent obligations to retain its own records. Deletion is not instantaneous across all systems; external tasks, backups and legal holds can affect completion. We will describe the applicable handling in response to a request rather than promise that every record disappears when an account is closed.
11. Your privacy rights and requests
Depending on applicable law, you may have rights to know about processing; access and obtain a portable copy; correct information; request deletion; withdraw consent; restrict certain uses; or opt out of sale, sharing or targeted advertising as legally defined. Applicable thresholds, exceptions and the processing actually performed determine the rights available. We do not require you to waive a mandatory right in exchange for using the service.
Account holders can use the available privacy export and deletion controls. For assistance, requests without an account, a correction, an authorized-agent request or an appeal of a decision, write to info@privyrides.com and identify the request as a privacy matter. We may request proportionate information to verify identity and authority and prevent disclosure to the wrong person; do not send passwords or complete card numbers. We will respond, explain a denial and provide any appeal or regulator information required by the applicable law within its applicable deadlines. You may complain to the competent privacy or consumer authority.
For information controlled independently by your Provider, contact that Provider as well. We will assess our own obligations and assistance responsibilities; you are not required to rely exclusively on the Provider to raise a concern about Privyrides' processing. We will not unlawfully discriminate against you for exercising protected rights.
12. Security, children and cross-border processing
We use access controls, secure communications, session protections and other measures appropriate to the service. No system can guarantee absolute security. Notify us of suspected unauthorized access through support or the published security contact. A security report should not include information obtained through unauthorized access to another person's account.
The services are not directed to children under 13. A booking for a minor must be arranged through a person with the necessary authority, and information supplied should be limited to what the service lawfully needs. If you believe a child has supplied information inappropriately, contact us so we can assess and address it. This Policy does not authorize a Provider to transport an unaccompanied minor without the necessary arrangements.
Information may be processed in the United States and other locations used by authorized service providers. Privacy protections can differ by location. Where a transfer requires specific safeguards under applicable law, those safeguards must apply; use of the platform alone does not waive them.
13. Updates and contact
We will identify updates through the published version and provide notice of material changes as appropriate or required. New consent will be requested where legally necessary. A changed notice does not automatically authorize a materially incompatible use of previously collected information.
For privacy questions, use the account privacy controls or info@privyrides.com, identifying PRIVYRIDES TECHNOLOGIES INC. and the relevant privacy request. The Terms of Service describe platform use and the separate responsibilities of Providers. This Policy does not limit rights that applicable privacy law makes nonwaivable.