Privacy Policy

Porch helps you find parking for the places you visit. We use personal information to provide this service, not to sell it or share it for advertising.

1. Who we are

APB Industries LLC (the “Company,” “we,” “us” or “our”) owns and operates the Porch mobile application and porchpark.app. This policy covers both. Contact hello@porchpark.app about privacy or your data.

2. Information we receive

• Guest access and visits. Porch creates a guest account with a persistent identifier and saves its access credentials securely on your device. A visit request includes the name you enter, business, arrival and departure times, status and optional parking preference. Each reservation has an identifier linking it to status changes, uploaded documents and review history. Guests do not need to provide email or a phone number. Records linked to this identifier are not anonymous.
• Optional parking validation. If you submit a validation request, we receive camera photos of your restaurant bill and parking ticket, linked to your guest account and reservation. We send the images and reservation details to support@porchpark.app for review. The photos are private, not published to businesses or other visitors, and are not used for advertising. Include only the documents needed for your validation request and avoid unrelated personal or full payment-card details.
• Business accounts. We receive your sign-in email and the profile details you submit, such as business name, address and coordinates, category, phone, website, hours, description and parking recommendations. Published business details are public; your sign-in email is private.
• Business verification. The updated verification flow sends precise device location, accuracy and capture time for ownership review. Its camera image stays on your device and is not uploaded. Photos submitted through the earlier flow remain in private storage for review and disputes until deleted under the retention rules below. Location alone does not prove ownership.
• Search and service information. We process the search text, selected place, map area and timing needed to return parking recommendations and routes. The recent-search list shown in the app stays on your device. Separately, search requests and selected results are included in our first-party usage journal described below. A map area can reflect your location if you center the map on yourself. Infrastructure providers also process connection and security information, such as IP address, request time, device/browser information and errors.
• First-party product analytics. Porch records app sessions, searches, places opened, results shown, parking options and selections, arrival and departure choices, reservation references and statuses, validation-submission steps and Directions actions. Selected request and response fields, outcomes and response times help us reconstruct the sequence of actions and identify failures. These records are linked to a stable keyed pseudonym of your Porch account and session identifiers. They are pseudonymous, not anonymous. When a fresh foreground location is already available under your iOS permission, the journal may include latitude, longitude, accuracy and capture time, including when requesting results or pressing Directions. We do not request background location or extra location permission for analytics.
• Limits on the journal. The journal stores selected fields rather than unrestricted network traffic or screen recordings. It excludes sign-in and refresh tokens, verification codes, passwords, entered guest names, account email, receipt image bytes and private management links. Searches can still contain personal information you type; recognizable email addresses, URLs and credentials are redacted, but you should not enter sensitive information in search. Place names, public place addresses and reservation identifiers may be retained. IP addresses used by the journal rate limiter remain in memory and are not copied into usage-event rows; hosting providers may keep their own technical logs.
• Terms acceptance. When you continue from the native introduction, we record your account identifier, accepted document release and hashes, a request identifier, the time reported by your device, server receipt time and presentation version to document that action. These receipts are separate from analytics and are removed with the account.
• Contact and Careers. Contact forms send first and last name, work email, company, address and any message to our support mailbox. Careers sends first and last name, email, LinkedIn URL, selected role and city. We do not automatically visit that URL. We also receive information you send directly to support. Both forms use security checks. To prevent spam and duplicates, we keep request identifiers, times and keyed hashes of IP addresses, email addresses and submitted content; these are not records of agreement to our terms.

3. How we use information

We use the first-party usage journal exclusively for product analytics and service improvement: evaluating feature use, testing product hypotheses, understanding where visits stop and diagnosing performance or errors. We do not use it for advertising, building advertising audiences, selling data or tracking activity across other companies’ apps and websites. We use other information to sign you in, save and deliver visit requests, show business profiles, recommend parking, review ownership and parking validation requests, answer inquiries, consider applications, prevent abuse and meet legal obligations.

Your selected business can see your visit details and parking preference, including after an authorized owner claims its profile. Other visitors cannot see them. We use business email for sign-in and service communications. Contact forms and business registration do not subscribe you to marketing.

We email new reservation details and a private review link to our support mailbox. Authorized support reviewers use time-limited links to view the reservation, inspect validation photos while they are temporarily available and record reservation or validation decisions. Anyone with the complete private link can access that record until the link expires, so it must not be shared publicly. Status changes and validation results appear inside Porch for the associated device session. If you allow notifications, Porch sends your app-specific Apple Push Notification service (APNs) token and its delivery environment to our server so Apple can deliver reservation confirmations, declines, reminders and parking-validation updates. We use this token only for service notifications, not advertising. Notification permission is optional; validation results remain available inside Porch without it.

We do not sell personal information, share it for cross-context behavioral advertising, or track you across other companies’ apps and sites for advertising. The website has no advertising or audience-analytics scripts. Its behavior does not change in response to a browser Do Not Track signal; these restrictions apply regardless of that signal. External services may process connection information under the policies below.

4. Businesses and external services

We use service providers for specific functions. They receive the information needed to perform those functions. Processing may take place in the United States or other countries where they operate.

• Hosting, accounts and email. Supabase provides accounts, authentication, database and private storage, including reservation cases and temporary validation images. Resend delivers sign-in codes, website submissions, reservation notices and validation requests with their image attachments. Cloudflare Email Routing forwards incoming mail. Hostinger hosts our website and supporting services, including the private review page and the access-restricted MySQL usage journal. The journal is operated for APB Industries LLC; it is not sent to Google Analytics or an advertising network.
• Form protection. Cloudflare Turnstile processes browser and connection signals; our server sends it the verification token and visitor IP address. Cloudflare also processes signals to improve its bot detection under its Turnstile Privacy Addendum.
• Service notifications. Apple APNs receives the app-specific device token, reservation reference, public business name, visit time and reservation or validation status needed to deliver an alert. Push notifications may appear on your lock screen according to your iOS settings. We do not include receipt photos, your name, precise location or payment details in the push payload. Delivery depends on Apple, your connection and device settings.
• Maps and directions. Apple provides maps, place searches and walking routes under Apple Maps & Privacy. Opening Directions passes the destination address or recorded entrance coordinates to Apple Maps or Google Maps. It does not send your Porch account or verification records. Navigation and any permissions you give that maps service are governed by its own practices.
• Earlier app versions. Version 1.5 removes the Google Analytics for Firebase SDK and its analytics setting. Earlier versions may still contain optional Google Analytics, disabled by default. You can disable Help improve Porch in Account & Privacy in those builds or update the app. Removing the SDK does not retrospectively erase information previously sent with that setting enabled; those records follow the Google Analytics retention and privacy settings. Yelp enrichment is currently disabled and does not delay or receive live place requests from this release.

APB Industries LLC is responsible for the processing it determines and the providers acting on its behalf. External services and businesses are responsible for processing they independently determine, including activity after you open their apps or sites. Their policies do not replace this policy for Porch's own processing. Nothing here excludes duties or rights that applicable law makes mandatory.

We may disclose information when necessary to comply with law, protect people or investigate misuse. We do not authorize businesses to sell guest information or use it for unrelated advertising.

5. Retention and deletion

We retain accounts and requests as needed to provide them; verification records as needed for ownership review and disputes; and inquiries and applications as needed to respond or complete their review. Website delivery counters stop counting after 24 hours and verification counters after one hour; expired records are removed on subsequent requests. Other security counters are periodically or opportunistically cleared. Provider logs and backups follow their retention settings. These periods depend on purpose, legal requirements and unresolved disputes, rather than one permanent retention period for all data.

Usage journal. Events normally expire 30 days after the server receives them. When account deletion starts, the signed deletion process disables journal writes for that account and retains its remaining usage history for up to seven days from that deletion request, solely for product analytics and improvement. The normal 30-day event limit can remove older events sooner. Automatic cleanup removes the retained events after the applicable deadline. A minimal keyed deletion marker remains to block stale credentials from recreating the deleted journal; it contains no search history, coordinates or visit details. Scheduled cleanup and failed deletion jobs are retried. This seven-day period is separate from the reservation-case period below.

Reservation and validation records. We retain the reservation identifier, visit details, statuses and linked review history to manage requests and resolve validation requests. A cancelled or declined reservation remains in a private operational case for 30 days after that change. Deleting the account starts a 30-day retention window for its retained cases. Photos follow the shorter delivery-based rules below. Expired cases are removed during scheduled cleanup after associated stored photos have been removed.

New validation photos are compressed JPEGs held temporarily in private storage for email delivery. We delete these stored copies after Resend confirms delivery to our support mailbox. Unfinished or undelivered temporary uploads expire after 24 hours; failed cleanup is retried. Earlier submissions may remain until their original 30-day deadline. Deleting an account does not extend the new temporary-photo deadline. Delivered emails and attachments remain in our support mailbox as needed to handle the reservation or validation request; provider logs and backups follow their retention settings. Account deletion does not recall delivered mail or automatically erase mailbox, provider-log or backup copies. Contact hello@porchpark.app about those copies or an unresolved validation request.

Guests and businesses can delete their account in Account & Privacy. This removes the sign-in account, personal profile, live requests and private business-verification records, including earlier verification photos, from the active service. Retained reservation cases are detached from the account, and the guest name is removed from their structured snapshots. Receipts and other retained evidence may still contain personal information; these records are not treated as fully anonymous. Public facts about a place and other visitors' requests may remain. Limited legal or security records may remain where justified and are not used to restore the deleted profile for ordinary service use.

6. Your choices

You can search without granting device-location permission. Camera and foreground location are requested for business verification; declining prevents that step. Optional parking validation uses the camera to capture the bill and parking ticket, without requesting location or access to your photo library. Declining camera access prevents photo submission, but does not prevent search or reservations. Permissions can be changed in iOS Settings. Porch does not request background location tracking. You can allow or disable notifications in iOS Settings; disabling them does not stop in-app reservation updates. App-specific push tokens are removed when you delete the associated account.

First-party product analytics runs as part of using Porch and has no advertising purpose or separate in-app opt-in switch. You can decline or revoke foreground location permission without disabling search. You can clear the on-device recent-search list; this does not erase search events already recorded in the server journal. Deleting account data restarts onboarding with an empty name and schedules journal deletion under the seven-day rule above.

Business owners can edit published details. Guests should keep their device session to manage requests, because there is no guest email recovery. Contact hello@porchpark.app for access, correction or deletion, including when you cannot enter the app. We may verify that the request concerns your account. Additional rights may apply where you live.

Porch is not directed to children under 13. Contact us if you believe a child has provided personal information. Please do not submit passwords, sign-in codes, payment details or unrelated sensitive information.

7. Policy changes

We publish revisions at this address with their date and version. Material changes will be communicated through the service or another appropriate channel. Where new consent is required, we will ask for it; changing this page does not create consent retroactively.