Overview. Hopwise does not require a Hopwise account. Provider credentials, saved places, and detailed ride history are stored on your device, subject to your backup settings. The Application communicates directly with linked providers and mapping services, and sends diagnostics and reduced-detail pricing information to service providers. Support and legal correspondence may include your name and other information you provide. We do not sell personal information or share it for targeted advertising. The sections below describe these practices and their limitations.

1. Operator and scope

This Privacy Policy describes how Steven Mirabito, an individual operating Hopwise as a sole proprietor in San Francisco, California ("Hopwise," "we," "us," or "our"), collects, uses, retains, and discloses information in connection with the Hopwise mobile application (the "Application") and the website at hopwise.co (the "Website"), collectively the "Service." The Application is currently a private beta distributed through Apple TestFlight and is intended for adults located in the United States.

Information is processed locally on your device, transmitted directly to third-party providers at your direction, or processed by us and the service providers identified below. We do not operate an account or ride-history server. That does not mean the Service involves no off-device processing. For privacy questions and requests, contact support@hopwise.co.

2. Information processed on your device

The Application does not require registration with Hopwise. Its local storage includes:

• Saved places and recent destinations: place names, addresses, and coordinates, including up to 20 recent destinations.
• Pending bookings and ride history: the provider, ride product and service class, quoted prices, comparison quotes, estimated savings, pickup and destination information, and relevant times. When a pending booking is matched to provider history, the Application also stores the ride time and final fare. Unmatched pending bookings are discarded after the matching window.
• Linked-account information: the linked providers, account labels (typically email addresses), and connection status.
• Authentication information: provider access and refresh tokens and, for Waymo, a long-lived Google sign-in credential and an installation identifier. These are stored using secure storage provided by your device's operating system. The Application does not retain your provider passwords. A phone number entered during Lyft authentication is transmitted to Lyft and is not saved by Hopwise.
• An installation identifier: a randomly generated identifier used to associate diagnostics and certain usage events with an installation. It is not your provider account identifier, but it is a persistent identifier and the associated records are not necessarily anonymous.

Location permission. The Application requests location access while in use to establish a pickup point and obtain nearby quotes. It does not collect background location for ongoing tracking. You may change location permissions in your device settings; restricting permission may affect location-dependent features.

Backups and device controls. Depending on your operating system and backup settings, local records and eligible credentials may be included in device or cloud backups. Backup copies are controlled through your device settings and the relevant backup-service account. The location and credential information transmitted to third parties is described in Section 3; the reduced-detail pricing information transmitted for analytics is described in Section 4.

3. Information transmitted to third-party services

Authentication, quote, and ride-history requests travel directly from your device to the relevant service rather than through a Hopwise-operated server.

• Ride providers and authentication services. When you link an account, the Application authenticates with that provider, using Google authentication for Waymo. For a search, it sends your pickup and destination and, where required by the interface, your device location, authentication credentials, and app or device identifiers. It retrieves relevant recent ride history to match pending bookings. These requests are associated with your provider account. The Application makes account-specific requests only to linked providers, and each provider applies its own terms and information practices.
• Mapping and place services. Address searches, autocomplete, place lookups, and map directions use mapping services integrated with the Application. The current beta uses Apple Maps. Search text and relevant location information are processed by the mapping provider to deliver those features.
• Apple TestFlight. Apple processes tester contact information, installation and diagnostic information, and feedback through TestFlight. We may receive tester information and feedback made available to developers through that service.
• Provider handoff. Selecting a quote opens the provider's application or website and may transmit ride details where the integration supports it. Any booking is completed with the provider.

Relevant third-party notices include the privacy policies of Uber, Lyft, Waymo, Tesla, Google, and Apple. Those policies govern the respective providers' independent practices; they do not replace our responsibility for processing described in this policy.

4. Diagnostics, usage activity, and pricing analytics

4.1. Installation-associated diagnostics and usage activity

We use Sentry in its US region for crash and error reporting, and PostHog in its US cloud for error reporting and product analytics. Diagnostic and non-pricing usage records can be associated with the random installation identifier described in Section 2. We do not intentionally attach provider account emails, phone numbers, or authentication credentials to these records.

• Sentry diagnostics: errors, stack traces, Application version, device model, operating system version, and short activity trails used to investigate failures. The Application applies filters intended to remove credentials, phone numbers, email addresses, coordinates, and URL query strings before transmission. Filtering is best-effort and cannot guarantee that every sensitive value is removed.
• PostHog errors and usage: error information and events indicating the start, completion, or removal of a provider link and the creation, modification, or deletion of a saved place. These usage events identify the provider or place type, such as Home or Work, rather than the saved place's name or address. Standard app, device, network, event-time, and IP information may also be processed, including approximate location derived from an IP address where enabled.

These providers also receive network information needed to accept requests. The Application does not currently offer an in-app switch to disable diagnostics or usage analytics during the beta. Discontinuing use and deleting the Application stops new transmissions from it; deletion of previously transmitted information is addressed in Section 8.

4.2. Reduced-detail ride pricing information

The Application sends pricing events to PostHog with a shared identifier used by all installations, rather than your installation identifier or provider account identifier. Person-profile creation and IP-based location enrichment are disabled for these events. The Application removes SDK-added session, device-model, operating-system, language, time-zone, and screen properties. It retains Application and analytics-library version information, connection type, event timing, and the pricing properties described below.

• Search events: approximate pickup and destination areas, rounded straight-line distance, and the number of linked providers. Areas use map cells approximately 3 miles (5 km) across, with dimensions varying by location.
• Provider responses: provider identity, success or failure status, response time, and relevant failure categories. Successful responses include quoted product identifiers and names, service classes, prices and currencies, any quoted price ranges or surge multipliers, whether a price is an estimate, and estimated pickup and trip durations.
• Handoff events: the selected product and price, estimated savings, lowest comparable quote, price ranking, comparison counts, and approximate areas.
• Matched ride events: provider and product information, quoted and final fares, currency, estimated savings, comparison counts, and approximate areas.

A new random search identifier groups events associated with one search and its resulting handoff or matched ride. It is not a persistent identifier across separate searches. The pricing event payloads do not intentionally include names, email addresses, phone numbers, authentication credentials, exact coordinates, street addresses, or place labels.

These measures reduce identifiability but are not a guarantee of anonymity. Event timing, approximate locations, fare information, network metadata, and information obtained elsewhere could potentially be combined to recognize a trip. Disabling IP-based location enrichment does not prevent a receiving service from processing the source IP address to deliver or secure a request. We do not attempt to identify the individuals associated with pricing events or associate those events with named individuals or installation profiles.

4.3. Aggregate statistics and publication

We use pricing information to evaluate provider prices, performance, and estimated savings. We may generate summaries grouped by day, provider, service class, and broader geographic area and retain those summaries indefinitely if they do not reasonably identify an individual or household. Before publishing statistics, we remove individual search identifiers, suppress small groups, and review the results to reduce the risk of identifying particular trips.

We will maintain information we treat as deidentified in that form and will not attempt to reidentify it, except for lawful testing of deidentification safeguards. If we provide nonpublic deidentified information to a recipient, we will require appropriate restrictions on reidentification and use. These commitments do not make individual pricing events categorically anonymous.

5. Website, support, and legal correspondence

Support and requests. If you submit the support form or contact us by email, we receive the information you provide, which may include your name, email address, message, attachments, request topic, device and app details, and installation identifier. Messages may contain locations or other personal information you choose to include. We use this information to respond, investigate problems, process privacy requests and arbitration opt-outs, and maintain necessary legal records. If you provide your installation identifier, we may use it to locate related diagnostic records. Do not send passwords, authentication tokens, or payment-card details.

The support form is processed by Web3Forms and delivered to our email account. Migadu provides our email service and processes incoming and outgoing messages, attachments, and associated email metadata. Your own email provider also processes messages you send.

Hosting and technical logs. Cloudflare hosts and delivers the Website and provides related network services. It processes technical information such as IP addresses, request times, requested resources, browser information, and DNS request information for delivery, reliability, and security. HTTP request and DNS logs are retained for 24 hours.

Cookies and tracking signals. We do not set advertising or analytics cookies or embed a website visitor-analytics tool. Operational logging by Cloudflare and processing by other service providers still occur as described above. We do not use the Website to track individuals across third-party websites for advertising or authorize third parties to do so on our behalf.

The Website does not change its behavior in response to browser Do Not Track signals. Because we do not sell personal information, share it for cross-context behavioral advertising, or use it for targeted advertising, a Global Privacy Control signal does not change those practices. Applicable privacy choices and rights remain available as described in Section 8.

6. Purposes and disclosures

We process information to provide the features you request, authenticate linked accounts, obtain quotes and match rides, operate and secure the Service, diagnose errors, improve functionality, analyze pricing, respond to communications, honor privacy choices, and comply with legal obligations. The categories and sources of information are described in Sections 2 through 5.

We disclose information only as described in this policy, including:

• At your direction: to linked ride providers, authentication services, mapping and distribution services, or another recipient you choose in order to perform the requested feature.
• To service providers: to Sentry, PostHog, Cloudflare, Web3Forms, Migadu, and other providers engaged to perform necessary operational functions, subject to appropriate contractual restrictions and access controls.
• For legal and security purposes: where reasonably necessary to comply with applicable law or valid legal process, address fraud or security threats, protect rights or safety, obtain professional legal or accounting advice, or establish, exercise, or defend legal claims.
• In a business transfer: in connection with a proposed or completed transfer of the Service, such as a sale, reorganization, or succession, subject to confidentiality protections, applicable law, and continued protection consistent with this policy or any required notice and consent.
• As aggregate or deidentified information: subject to the safeguards and publication limits in Section 4.3.

We do not sell personal information, disclose it for cross-context behavioral advertising, or use it for targeted advertising. Our operational disclosures to service providers and user-directed disclosures to ride providers are described above.

7. Retention

• Device records: saved places and confirmed ride history remain on your device until removed, subject to the Application's storage limits and your device controls. Disconnecting an account removes its stored account label and authentication tokens. Unmatched pending bookings expire as described in Section 2.
• Sentry: hosted diagnostic records are retained for 30 days.
• PostHog: individual error, usage, and pricing event records are retained for 90 days. This event-retention period is separate from any aggregate summaries described in Section 4.3.
• Cloudflare: HTTP request and DNS logs are retained for 24 hours.
• Support, feedback, and legal correspondence: we retain records as reasonably necessary to respond, investigate and resolve an issue, honor an opt-out or other choice, maintain necessary business records, meet legal obligations, and establish or defend legal claims. The appropriate period depends on the nature of the request, its resolution, and any applicable legal requirements.
• Aggregate summaries: summaries that do not reasonably identify individuals or households may be retained indefinitely, subject to Section 4.3.

We may retain specific records longer where necessary to comply with a legal preservation obligation or resolve a pending dispute. Copies in service-provider backups are subject to the relevant provider's deletion cycles. User-controlled device or cloud backups are managed through your device settings and the relevant backup-service account. Removing information from the Application does not itself delete records independently maintained by a ride provider, mapping or distribution provider, or another service.

8. Choices and privacy requests

• Disconnect a provider: use Settings › Accounts to sign out and remove the provider's tokens and account label. You may also revoke access through the provider's own controls where available. Disconnection does not automatically remove previously confirmed ride history.
• Remove local information: use the Application's saved-place controls to delete a saved place. Deleting the Application removes its local database, but your operating system may retain credentials in secure device storage. Disconnect accounts before deleting the Application, and manage any device or cloud backups separately.
• Control location access: change or revoke permission through your device settings.
• Request diagnostic deletion: email support@hopwise.co with your installation identifier. To obtain it, tap the rabbit at the bottom of Application Settings five times; the Application displays it and copies it to your clipboard. We can use that identifier to locate associated Sentry and PostHog records and request their deletion, subject to applicable exceptions.

You may also email us to request access to, correction of, or deletion of personal information we maintain about you. Depending on your residence and applicable law, you may have additional rights to obtain a portable copy, restrict or object to certain processing, appeal a denial, use an authorized agent, or exercise applicable opt-out rights without unlawful discrimination. These rights are subject to the scope, conditions, and exceptions of the law that applies; this policy does not represent that every state privacy statute applies to Hopwise.

Describe the information or request and provide enough detail for us to identify relevant records. We may ask for proportionate verification of your relationship to those records, and, for an agent, evidence of authority. You do not need to create a Hopwise account or provide a provider password or token. Information supplied for verification will be used for that purpose and retained only as reasonably necessary. We will respond within the period required by applicable law, explain any applicable exception or denial, and provide an appeal method where required.

Because pricing records do not use your installation identifier, we generally cannot reliably identify which pricing events are yours from your name, email, or installation identifier alone. We will assess requests using reasonably available information; where records cannot reasonably be associated with you, individual deletion may not be possible, and the 90-day event-retention period applies. We may retain a limited record of a privacy request or arbitration opt-out where necessary to honor it or meet legal obligations.

9. Security and processing locations

We use reasonable technical and organizational safeguards appropriate to the information processed, including operating-system-provided secure storage for credentials, diagnostic filtering, reduced-detail pricing payloads, and access restrictions. No transmission, storage method, or filtering system is completely secure, and we cannot guarantee absolute security or anonymity.

Sentry and PostHog event storage is configured in the United States. Other providers, including our email, hosting, and support providers, may process information in other countries according to their service arrangements. Migadu is based in Switzerland, and Cloudflare operates a global network. United States availability of the Application does not mean all processing occurs exclusively in the United States. Where applicable law requires safeguards for a transfer, we will use the required safeguards.

10. Children

The Service is intended for individuals aged 18 or older. We do not knowingly collect personal information from children under 18. If you believe a child has provided personal information to us, contact support@hopwise.co so we can investigate and take appropriate steps, including deletion where required.

11. Changes to this policy

We may update this policy to reflect changes in the Service, our practices, or legal requirements. We will revise the date above and provide notice of material changes through the Application, TestFlight release notes, the Website, or email where available. Where required by law, we will provide notice before a change takes effect and obtain any necessary consent before using previously collected information for a materially different purpose. Continued use alone does not replace consent where consent is legally required.

12. Contact

Hopwise is operated by Steven Mirabito, a sole proprietor in San Francisco, California. Direct privacy questions, requests, and notices to support@hopwise.co.