Privacy Policy

Effective November 1, 2026 · Version 1.3

Coastal Waterfall LLC ("we," "us," or "our") operates Stop Circling, including this website and our Android app (the "Service"). This policy explains information handled when you use the Service. Contact us at [email protected] with privacy questions or requests.

Your price and walking preference is saved on your device. We do not upload that preference or the ranking scores that reveal it. Searches still send information needed to find parking, show maps, estimate walking routes, and open the checkout you choose.

1. Information we handle

• Destination searches and location. Text you enter in destination search and the places you select are processed by Google Places. On the website, already-permitted device location may help tailor suggestions; otherwise Google may use an approximate location, such as one inferred from your IP address. The current Android app does not request device-location permission. A selected parking destination is not necessarily your physical location.
• Parking searches. We receive selected destination coordinates, arrival and departure times, the destination time zone, and technical search identifiers. Your device or our server sends the relevant search parameters to parking inventory services. When your device retrieves inventory directly, it sends the results to our server to combine and standardize them. We receive parking locations, prices, availability, instructions, ratings and related source information.
• Availability notifications you request. If you choose Notify me for an unsupported destination, we save your email address, the selected destination's coordinates and label, your notification consent and its date, and whether you used the website or Android app. We use this separate signup record to notify you when parking search becomes available in that area. Searching alone does not create a signup, and signup details are not added to operational failure reports. We do not save your email as a device preference.
• Maps and walking. Mapbox receives requests needed to display maps, which can include the viewed area, IP address, device/browser information, and SDK usage information. Our routing service processes destination and garage coordinates to estimate walking time and distance. We use shared route caches without attaching a customer account or saved preference to them.
• Checkout handoffs. We process the parking option and times needed to prepare checkout links and handle reported link failures. Selecting checkout sends you to the named booking service, which may receive facility and time information in the link. We do not currently collect payment-card details, take parking payments, or maintain customer booking accounts. Information you provide at third-party checkout is handled by that service.
• Technical and operational information. Servers and integrated services process connection information such as IP addresses, browser/device information, request timing, response status and security signals. Our operational reports use random per-search identifiers, fixed error/outcome categories, durations, and, where applicable, client type and app version. They do not include the saved price/walking preference, personalized ranking scores, names, email addresses, raw search text, or payment details. Infrastructure and security logs may separately contain technical connection information.
• Legal document updates. When you open or refresh Terms or Privacy in a supported Android version, the app may request the document from our website. Our hosting services receive ordinary connection and request information described above. The app does not attach a visitor identifier, parking destination, parking times or saved preference to that request, and this feature does not add usage analytics.
• Website performance and usage counts. We measure page landings, searches that return results, checkout clicks and approximate page-load timing using daily aggregate counters. These counters distinguish homepage and venue pages and broad referring-service categories, such as Google, ChatGPT or an unknown/direct source. The website derives the category locally and does not send the referring URL or its search terms in this measurement. The measurement sends no venue name, destination coordinates, parking times, saved preference, ranking scores, customer identifier or search identifier. We store totals by day and category rather than individual measurement records. These counts cannot establish an individual visitor's journey or a completed booking.
• Communications. If you contact us, we receive the contact details, message, attachments and other information you choose to send. Please do not send payment-card numbers, passwords, government identification, or other unnecessary sensitive information.

2. Storage on your device

The website stores your last valid Budget, Balanced or Convenience selection, or exact custom hourly amount, in browser local storage. The Android app stores the equivalent value in private app storage, with Android backup disabled for the app. This setting has no application-set expiration, is not synchronized through our servers, and is not uploaded for recommendation analytics. Invalid edits do not replace the last valid value. Missing or unavailable storage defaults to Balanced.

You can change the setting using the preference controls. Reset replaces a custom value with Balanced; it does not remove the storage entry. To remove the saved setting, clear this site's browser data or clear the Android app's storage. Private browsing, browser cleanup, or uninstalling the app may also remove it. Clearing local data does not itself delete records already held by us or third parties.

We do not save destination text, selected place details, parking times or checkout progress as customer preferences on your device. Both clients may separately cache service-routing configuration and update timing. Browsers, operating systems, and Google/Mapbox components may cache resources or use their own storage, identifiers and telemetry as described in their policies. This preference does not use an application-set cookie.

Our website usage measurement does not set cookies or persistent browser identifiers. A temporary in-memory record limits measurements during the current page load and disappears when that page is closed or reloaded.

Supported Android versions keep the last validated legal documents and their update timing in private app storage excluded from Android backup, so you can read them when a connection is unavailable. The app also includes a dated packaged copy for fallback. These copies are documents, not a record that you accepted them. Cached copies remain until replaced, the app's storage is cleared, or the app is uninstalled; they are separate from the website measurement counters and their retention period.

3. Why we use information

We use information to provide and improve parking discovery, compare inventory, determine destination-local times, display maps and walking estimates, deliver the checkout handoff you request, troubleshoot failures, measure service reliability and website performance, understand broad referral and usage trends, respond to support requests, prevent fraud and misuse, enforce our terms, protect rights and safety, and comply with applicable law. We may develop related parking, travel, mobility and merchant services using operational insights and appropriately aggregated or de-identified information. We do not treat a privacy policy as permission to collect unrelated data or use information incompatibly with the notices and choices given when it was collected.

4. Who receives information

Our public homepage, destination pages and informational pages can be indexed and summarized by search engines and answer services. These pages publish general information about venues and our service; they do not publish your searches, parking times, preferences, notification requests or operational records. Following a link from a search or answer service is subject to that service's own privacy practices. Public-page indexing does not authorize us to disclose customer records for AI training.

• Search, maps and booking services. Google provides destination search; Mapbox provides maps and SDK functionality. We currently query SpotHero, ParkWhiz, ParkMobile, BestParking and Parking.com for parking inventory. These services may receive search, location or technical information directly from your device or through us. The provider you choose separately handles checkout and any account, payment, reservation, cancellation or refund.
• Service providers. Hosting, infrastructure, routing, security, support and professional-service providers may process information as needed to support our operations, subject to applicable contractual and legal requirements.
• Legal and safety disclosures. We may disclose information when reasonably necessary to comply with law or valid legal process, investigate abuse, establish or defend legal claims, protect rights, property or safety, or enforce our terms, subject to applicable law.
• Business changes. Information may be reviewed or transferred in a financing, reorganization, merger, acquisition, sale of assets or insolvency process, with appropriate safeguards and subject to existing privacy commitments and applicable law.
• Your direction. We may disclose information when you request or authorize a feature or disclosure, with additional notice or consent where required.

Third-party services have their own terms and data practices. Review Google's Privacy Policy, Mapbox's Privacy Policy, and the policy shown by your selected booking service. These links do not limit our responsibility for our own processing. Mapbox's Android attribution/information control includes its telemetry choice. Browser and device privacy settings may provide additional controls.

5. Advertising, tracking and privacy signals

We do not sell customer lists or personal information for money, and we do not use your saved tradeoff for advertising. Our application does not include advertising pixels or build cross-site advertising profiles. Integrated third parties can receive technical information as described above and may recognize an existing relationship with you under their own policies. Our application does not change its essential functionality in response to a browser's Do Not Track signal; necessary preference storage is not cross-site advertising. Where applicable law requires honoring Global Privacy Control or other opt-out signals for a particular processing activity, those rights apply regardless of this statement.

Our website skips its optional performance and usage measurements when your browser exposes Do Not Track as enabled or Global Privacy Control as true. Essential search, checkout, security and operational processing still works. Referring services and integrated third parties control their own measurement practices.

Before introducing advertising or other processing that requires an additional notice, opt-out mechanism or consent, we will provide the required disclosures and controls. This policy is not advance consent to future sale, cross-context advertising, or unrelated use of precise location.

6. Retention and security

Requested availability notifications are stored separately from operational records until the notification is fulfilled, you request removal, or we determine that the request is no longer needed. You can withdraw the notification request through our privacy/support contact. This signup is for the selected area's availability notification, not unrelated marketing.

Local preferences remain until replaced or removed as explained above. Checkout context is held in bounded server memory, normally eligible for use for up to ten minutes; expired entries are removed during subsequent housekeeping or process shutdown. Successful walking estimates are reused only while less than seven days old. Expired route rows are removed during cache maintenance and can remain on disk until that maintenance runs; seven days is a reuse limit, not a promise of immediate physical erasure.

Daily website performance and usage counters are kept for a rolling 90-day period. Older counters are removed when the measurement store starts or accepts new measurements; cleanup does not run while the service is stopped. This aggregate-counter schedule is separate from the operational-record retention described below.

Operational records are currently retained without a fixed automatic deletion period. We review retention in light of troubleshooting, security, service improvement and legal needs, and may delete or aggregate records when no longer needed. Support correspondence and records needed for legal obligations or disputes may be retained for those purposes. The former recommendation-upload endpoint is disabled; legacy preference audit records are removed during the backend upgrade cleanup. Historical backups and independently operated third-party systems may follow separate retention schedules.

We use safeguards intended to protect information, including access restrictions and appropriate transport protections. No system is perfectly secure, and we cannot guarantee absolute security. Information may be processed in the United States and other countries where our providers operate, subject to applicable legal safeguards.

7. Your choices and privacy requests

You can change or clear local preferences, manage device location permissions and browser storage, use Mapbox's available telemetry controls, and choose whether to proceed to external checkout. Refusing information necessary for a requested feature may prevent that feature from working.

Depending on applicable law and our coverage under it, you may have rights to access or obtain a copy of personal information, correct it, request deletion, withdraw consent, or opt out of certain uses or disclosures. Contact [email protected], describing your request and the Service you used. We will respond as required by applicable law, may reasonably verify identity or an authorized agent's authority, and will explain any applicable exception or inability to locate records. You do not need to create an account to submit a request. We do not require you to send sensitive documents unless needed and proportionate for lawful verification.

We do not maintain an identity-linked search history or server copy of your current preference, so we may be unable to associate a historical technical record with you. We will not collect extra identifying information merely to build such a history. Rights may be subject to security, fraud-prevention, transaction, recordkeeping and other legal exceptions. We will not unlawfully discriminate or retaliate against you for exercising privacy rights. You may contact the relevant privacy regulator and, where applicable, appeal a decision by replying to our privacy contact.

California residents: California privacy rights depend on the law and whether it applies to a particular business and processing activity. This policy does not waive any applicable California rights. It describes our online collection, disclosures, tracking practices, available choices and how changes are communicated.

8. Children

The Service is intended for adults and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided such information, contact us so we can investigate and take appropriate action.

9. New features and policy changes

The current published policy is available at stopcircling.com/privacy.html. Supported Android versions can retrieve revised documents without an app update and identify when a saved or packaged copy is being shown. Check the displayed effective date; an offline copy may be older than the published version. Reading, downloading or refreshing a document does not itself change app functionality or provide consent to new collection or use of information.

We may offer new features, such as accounts, saved trips, notifications, memberships, reviews, merchant tools or booking services. Features that are not currently available do not collect information merely because they are mentioned here. We will explain relevant collection and terms when a feature is introduced and obtain permission where required. Device-only preferences will remain device-only unless you separately choose a future synchronization feature after receiving appropriate notice.

We may update this policy and will change the effective date. For material changes, we will provide a prominent notice in the Service or another appropriate communication before the change takes effect, as required by law. We will not retroactively apply materially incompatible uses to previously collected information without any legally required notice and consent. Contact us for questions about an earlier version.