Privacy Policy

This Privacy Policy explains how Sparta Trading, LLC, doing business as ParkProof ("ParkProof," "we," "us," or "our") collects, uses, discloses, retains, and protects personal information through the ParkProof website, web applications, dashboards, QR-code flows, payment interfaces and terminals, cameras, connected equipment, and related services (collectively, the "Services").

ParkProof currently supports participating locations in Washington, D.C., Maryland, and Virginia. This Policy applies to Operators, customers, drivers, monthly parkers, guests, valet users, merchants, property managers, attendants, enforcement personnel, and others who interact with the Services.

1. ParkProof's role and participating Operators

Property owners, parking-management companies, garages, parking lots, valet operators, employers, tenants, merchants, charging-site hosts, and other participating entities ("Operators") may use ParkProof to manage their locations.

• Processor or service-provider role. When an Operator determines the purposes and means of processing and instructs ParkProof to handle information on its behalf, ParkProof acts as that Operator's processor or service provider.
• Controller or business role. ParkProof acts independently for information used to operate and secure the platform, authenticate accounts, administer payments and platform fees, reconcile transactions, prevent fraud, provide support, respond to privacy requests, comply with law, maintain records, and improve reliability.

Operators may provide separate privacy notices and may independently use information under their own policies. When ParkProof acts only for an Operator, a privacy request may need to be directed to that Operator, and ParkProof will reasonably assist the Operator.

2. Information we collect

Account, contact, and identity information

• Name, mobile number, email address, account credentials, authentication information, one-time codes, consent records, and support communications.
• Monthly-parker, tenant, employer, host, guest, merchant, validation, reservation, permit, access-list, and visit-note information.

Vehicle, parking, valet, charging, and access information

• License plate, plate jurisdiction, vehicle make, model, color, ticket or permit number, parking space, stall, charger, and related vehicle details.
• Entry and exit times, duration, reservation window, validation, overstay, access decision, gate or door attempt, retry, guest-pass activity, patrol result, citation or violation status, and enforcement notes.
• EV-charging enrollment, connector or stall, charging status, session time, energy delivered, card-on-file status, and related charges.
• Valet check-in and checkout information, ticket or key tracking, customer pickup status, vehicle-condition assessments, damage descriptions, and vehicle-condition or damage photographs.

Images and camera-derived information

• License-plate and vehicle images captured by LPR or patrol cameras.
• Vehicle-condition and damage images collected during valet operations.
• Image-derived plate text, timestamps, lane or camera identifiers, confidence scores, and matching results.

Routine ParkProof camera functions are intended to identify vehicles and license plates, not people. Images may incidentally include individuals or nearby areas.

Payment and transaction information

• Rates, authorizations, holds, charges, refunds, fees, payment status, receipts, reconciliation records, and transaction identifiers.
• Card brand, expiration information where supplied by the processor, and the last four digits of a payment card.

Payment-card details are collected and processed by Stripe or another disclosed payment provider. For payments taken at a location, the Operator is normally the merchant of record, and the payment provider processes the payment on the Operator's behalf; those funds settle to the Operator rather than to ParkProof, which charges only its own platform fees. ParkProof does not store a complete payment-card number or security code on its own systems.

Technical, device, and operational information

• IP address, browser and device type, operating system, language, referring page, timestamps, application events, errors, and security or audit logs.
• Essential cookies, local storage, session identifiers, authentication records, and fraud-prevention signals.
• Equipment and integration events from gates, doors, vehicle loops, chargers, cameras, payment terminals, controllers, and connected devices.

3. Sources of information

We collect information directly from users; from Operators, property managers, employers, hosts, merchants, attendants, valet personnel, and enforcement personnel; automatically from devices, cameras, connected equipment, browsers, payment terminals, and logs; and from service providers such as payment, messaging, hosting, security, identity-verification, and equipment-integration providers.

4. How we use information

• To create, authorize, manage, close, validate, bill, and document parking, valet, EV-charging, reservation, guest, monthly-parker, and access sessions.
• To detect vehicle entry or exit, match plates, operate connected equipment, manage charging, support patrol and enforcement, and investigate incidents.
• To calculate charges, place or release holds, facilitate the processing of payments and refunds, issue receipts, reconcile transactions, and support the handling of disputes or chargebacks.
• To send payment links, confirmations, receipts, one-time codes, secure links, expiration alerts, charging updates, valet pickup notices, and violation notices.
• To document vehicle condition, investigate damage or safety incidents, and assist with claims.
• To authenticate users, administer accounts, enforce permissions, prevent fraud and misuse, troubleshoot equipment, secure the Services, and maintain availability.
• To provide support, comply with contracts and law, respond to privacy requests, maintain accounting and audit records, and establish or defend legal claims.
• To improve reliability, safety, accessibility, and product functions using aggregated, de-identified, or limited operational information where practical.

5. How we disclose information

We do not sell personal information and do not disclose it for cross-context behavioral or targeted advertising. We may disclose information:

• To Operators and authorized personnel who need it for location management, parking, valet, charging, access, validation, customer service, claims, safety, or enforcement.
• To service providers that support databases and hosting, web delivery, payments, transactional messaging, connected equipment, email, LPR or OCR, terminals, security, support, and related operations. Current providers include Supabase, Netlify, Stripe, Twilio, and Shelly.
• To professional advisers and insurers such as attorneys, auditors, accountants, insurers, and claims administrators where reasonably necessary.
• For legal, safety, and fraud matters when we reasonably believe disclosure is required by valid legal process or law, or necessary to investigate fraud, misuse, emergencies, threats, injury, property damage, or security incidents.
• For business transactions involving financing, merger, acquisition, reorganization, bankruptcy, sale of assets, or a similar transaction.
• At your direction or with your authorization.

Service providers may use information only for contracted purposes or as otherwise allowed by law. Operators' independent uses are governed by their own policies and agreements.

6. Role-based access and phone-number masking

ParkProof is designed to limit access by assigned organization, location, and job responsibility. Managers may access operational and financial records; attendants may access information needed to serve customers; enforcement personnel may access plate and authorization status; merchants may access validation functions; and valet personnel may access ticket, vehicle-condition, and pickup information.

In ordinary Operator-facing views, mobile numbers may be masked so only the last four digits are displayed. ParkProof and limited service providers may still process the full number for message delivery, session matching, account recovery, fraud prevention, support, privacy-request verification, emergencies, and legal compliance.

7. LPR, patrol cameras, and vehicle images

At participating locations, LPR and patrol cameras may capture vehicle and plate images to detect entry and exit, identify or match a session, calculate duration, verify authorization, open equipment, support enforcement, investigate incidents, or protect property. Camera use may also be described by on-site signage and an Operator's additional notice.

ParkProof does not use LPR images to identify individuals through facial characteristics. We do not sell LPR information or use it for advertising. Access is limited to authorized users and service providers for legitimate operational, safety, enforcement, claims, support, and legal purposes.

8. Identity verification and biometric information

If identity verification is later activated, ParkProof or the applicable Operator will provide a separate, conspicuous notice before collection. That notice will explain the provider, information requested, purpose, disclosures, retention, and alternatives, and consent will be obtained where required. A material biometric use will not be introduced only through a silent change to this Policy.

9. Transactional text messages

When you provide a mobile number in a text-enabled ParkProof flow, you agree to receive automated transactional messages related to your activity. Message frequency varies; message and data rates may apply. Reply STOP to opt out or HELP for help. Consent to receive texts is not a condition of parking, payment, or another purchase where a reasonable alternative is offered.

Messages may include payment links, receipts, session alerts, access links, one-time codes, charging updates, valet pickup notices, and violation notices. ParkProof does not send promotional text messages through this program. See the SMS Terms.

10. Cookies, local storage, analytics, and advertising

We use essential cookies, local storage, and similar technologies to authenticate users, maintain sessions, remember limited information on a device, process payments, prevent fraud, and secure the Services. Blocking these technologies may prevent parts of the Services from working.

ParkProof does not currently use Google Analytics, Meta Pixel, targeted-advertising cookies, or cross-site tracking. If nonessential analytics or advertising technologies are introduced, we will update our notices and provide consent or opt-out controls where required before activation.

11. Data retention

We retain information only as long as reasonably necessary for the purposes described in this Policy, an Operator's documented instructions, legal and accounting obligations, safety, fraud prevention, disputes, enforcement, claims, and legal holds. Our intended baseline schedule is:

A shorter period may apply when an Operator directs deletion or law requires it. We may retain a minimal suppression record to honor an opt-out or deletion request. When retention is no longer justified, information is deleted, aggregated, or de-identified where reasonably feasible.

12. Your privacy choices and rights

Subject to applicable law and exceptions, you may request to confirm whether we process your personal information, access it, correct inaccuracies, delete it, or receive a portable copy. Where applicable, you may also opt out of targeted advertising, sale of personal information, or certain legally significant profiling, and may withdraw consent for processing that relies on consent.

ParkProof does not currently sell personal information, process it for targeted advertising, or use it for legally significant profiling. We will not discriminate against you for exercising an applicable privacy right.

Submitting a request

Email support@parkproof.ai with the subject Privacy Request, or mail the request to the address below. Include enough information to identify the relevant account, location, session, plate, or phone number. Do not send a complete payment-card number, password, government identifier, or unnecessary sensitive information.

We may verify your identity and authority. If ParkProof processes the information solely for an Operator, we may refer or transmit the request to that Operator. We aim to respond within 45 days where applicable, subject to legally permitted extensions.

Appeals

To appeal a denied privacy request, email support@parkproof.ai with the subject Privacy Appeal. We will review the appeal and, where required, provide the result and information about contacting the appropriate Attorney General.

13. Security

We use administrative, technical, and physical safeguards designed to protect personal information, taking into account its nature and the risks involved. Measures may include role-based and location-scoped access, authentication, encryption in transit, payment tokenization, phone-number masking, logging, backups, vendor controls, and incident-response procedures.

No system is completely secure. Secure links and QR codes may provide access to a session; do not share them with anyone you do not authorize. If we identify a qualifying data breach, we will provide notices as required by applicable law.

14. United States processing

ParkProof is operated in the United States. Production information and backups are intended to be stored in the United States. Service providers may access or process information from other locations when necessary to support their services, subject to contractual and legal safeguards.

15. Drivers under 18 and children's privacy

The Services may be used by legally authorized drivers under 18 where permitted by the Operator and applicable law. The Services are not directed to children under 13, and we do not knowingly collect online personal information directly from a child under 13 without legally sufficient authorization. Contact us if you believe a child under 13 provided information.

16. Testing and development

Before public launch, ParkProof may use test accounts, sandbox payment or identity-verification tools, and controlled pilot data to validate functions. We seek to avoid unnecessary real consumer information in development. Test and pilot information remains subject to appropriate access, security, and deletion controls.

17. Changes to this Policy

We may update this Policy as the Services, vendors, or laws change. We will post the updated version and revise the effective date. If a change materially expands how previously collected information is used or disclosed, we will provide additional notice and obtain consent where required rather than relying only on a silent or retroactive policy change.

18. Contact us