Website, Mobile App, Dashboard, Payment Services, and Private Parking Operations
Effective Date: July 28, 2026 Version: 2.0 Company: Veritas Parking Group LLC
Website, Mobile App, Dashboard, Payment Services, and Private Parking Operations
This Privacy Policy explains how Veritas Parking Group LLC ("Veritas," "we," "us," or "our") collects, uses, discloses, retains, and protects Personal Information through:
● veritasparkinggroup.com and other websites that link to this Policy;
● the Veritas mobile application;
● property-owner, operator, tenant, and business dashboards or portals;
● parking-session, payment, validation, permit, support, dispute, and account services; and
● private parking operations supported by Veritas, including license plate recognition, destination-use or "Walk-Off" review, hybrid parking, and authorized app-based enforcement.
This Policy is intended for individuals in the United States. A property-specific sign, notice at collection, state supplement, or separate written notice may provide additional information. If a mandatory law gives you greater rights than this Policy, that law controls.
This Policy is a notice about data practices. It is not the contract governing a driver's use of a parking facility. The applicable posted parking terms, Terms of Service, payment screen, and any state or property-specific supplement govern that use.
1. Who Is Responsible for the Information
Veritas may act in different roles depending on the service:
● Veritas as an independent business or controller. We generally determine why and how information is used for Veritas accounts, website inquiries, security, product administration, Veritas-issued private parking charges, disputes, compliance, and our own business records.
● Veritas as a service provider or processor. A facility owner or operator may determine the purposes and essential rules for permits, validations, ordinary parking fees, property access, or reports, while Veritas processes information under a written services agreement.
● Separate businesses. A facility owner or operator, payment processor, bank, vehicle-record provider, mailing vendor, collection provider, or other partner may separately control information for its own legal duties and services. Its privacy notice may also apply.
The sign, checkout page, receipt, invoice, dashboard notice, or other service screen should identify the relevant facility and, where required, the business responsible for a particular transaction. Questions about Veritas practices may be sent to the contact information in Section 24.
2. Definitions
For this Policy:
● Personal Information means information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked to an individual or household. The term includes "personal data" and similar terms under applicable state law.
● ALPR Data means a license plate image or number and associated capture information generated by an automated license plate recognition system, such as date, time, location, travel direction, and camera identifier.
● Parking Event means an entry, exit, parking session, permit, validation, alleged rule violation, payment, destination-use review, or related event at a supported private parking facility.
● Facility Operator means the owner, manager, tenant, business, association, or other person that lawfully controls parking rules at a facility.
● Account User means a person who uses a Veritas app, dashboard, portal, or account.
3. Information We Collect
The information collected depends on the service, property, account, device settings, and choices made by the individual.
3.1 Parking, Vehicle, and ALPR Information
We may collect:
● license plate number, issuing state or jurisdiction, and plate images;
● vehicle make, model, color, type, and other visible vehicle characteristics;
● parking-facility location, zone, space, entry and exit points, and camera identifier;
● date, time, entry, exit, direction, parking duration, paid time, grace period, and overstay information;
● permit, exemption, validation, authorized-visit, loading, accessibility, and parking-rule status;
● photographs, short video clips, and other event evidence; and
● records showing whether an event was accepted, rejected, voided, disputed, refunded, or referred for further handling.
Veritas parking cameras are configured for parking operations, not general public surveillance. Unless a property-specific notice expressly says otherwise, Veritas does not intentionally collect audio through parking cameras.
3.2 Destination-Use and Walk-Off Information
At a destination-use or hybrid facility, a system may evaluate whether at least one occupant of a vehicle traveled between the parked vehicle and an approved destination at that facility. The system may use time-linked camera views or event markers to establish that limited movement connection.
Veritas does not use this process to determine a person's name or identity. We do not use facial recognition, faceprints, facial templates, gait identification, or other biometric identification for this purpose. Images may nevertheless incidentally depict people, and a trained reviewer may inspect relevant event evidence before a charge is issued or when a dispute is considered.
3.3 Paid Parking and Transaction Information
We may collect:
● selected facility, zone, license plate, parking start and end time, rate, duration, extensions, discounts, taxes, and amount;
● payment status, payment method type, last four digits or tokenized reference, processor transaction identifier, receipt, refund, chargeback, and payout information;
● billing name, email address, telephone number, and billing ZIP code when supplied; and
● merchant-of-record, Facility Operator, and revenue-allocation records needed to process or reconcile a transaction.
Payment-card numbers and security codes are submitted to a payment processor, such as Stripe, and are not intended to be stored in full on Veritas systems. The processor's privacy notice applies to its processing.
3.4 Parking Charge, Vehicle-Record, Notice, and Collection Information
For an eligible, documented Parking Event, we or an authorized provider may collect:
● registered-owner or other legally authorized recipient name and mailing address;
● the source, date, user, stated permissible purpose, and audit record for a motor-vehicle-record request;
● invoice, notice, mailing, delivery, payment, returned-mail, dispute, appeal, settlement, and collection status;
● communications, call notes, and supporting evidence; and
● attorney or collection-provider information if a matter is lawfully referred.
Veritas does not obtain motor-vehicle records for bulk prospecting, pre-event monitoring, marketing, or speculative identification. A record may be requested only for a specific eligible event, through an approved provider, after an authorized reviewer documents a legally available purpose under the Driver's Privacy Protection Act, applicable state law, and the provider's rules. If an authorized purpose or lawful access is unavailable, Veritas will not obtain the record or send a record-based mailed invoice.
3.5 App, Dashboard, and Account Information
We may collect:
● name, business name, title, work email, telephone number, postal address, user ID, authentication information, and account role;
● facility affiliation, proof of authority, assigned properties, zones, permits, exemptions, validation rules, and user permissions;
● app or dashboard submissions, including plate information, location, event date and time, photographs, video, notes, dispute responses, and uploaded documents;
● account preferences, notification choices, support requests, and account-deletion requests;
● device type, operating system, browser, app version, language, IP address, approximate network location, device or installation identifier, push-notification token, login time, session data, diagnostics, crash data, and security logs; and
● camera, photo-library, notification, or location information only when the Account User enables a permission needed for a requested feature.
The app may transmit an authorized user's submission to Veritas-hosted systems and make appropriate portions available in the Veritas dashboard to authorized users, reviewers, service providers, or Facility Operators. A dashboard action may likewise update app-visible status. We use role-based permissions and do not intend to make one Facility Operator's data available to another unrelated Facility Operator.
3.6 Website, Inquiry, and CRM Information
When a person visits our website or submits a form, we may collect:
● name, organization, title, email, telephone number, property location, service interest, message, referral source, and any information voluntarily submitted;
● IP address, browser and device information, pages viewed, approximate location derived from IP, referring page, interaction and performance data, and date and time; and
● consent, suppression, and communication-preference records.
A website inquiry may be transferred to our customer relationship management, support, or sales systems and made available to authorized Veritas personnel for follow-up. Submitting an inquiry does not create a parking-services agreement.
We may use privacy-conscious website analytics and performance services, including Vercel Analytics and Speed Insights. We configure analytics not to intentionally send form contents, full payment details, or URL query strings containing submitted data. We do not use Personal Information for cross-context behavioral advertising as of the Effective Date.
3.7 Dispute, Appeal, Support, and Accommodation Information
We may collect communications and evidence submitted to challenge or explain a Parking Event, including receipts, proof of payment, proof of a destination visit, photographs, vehicle-sale or rental records, accessibility documentation, and other supporting material. Please provide only what is reasonably necessary. Where possible, redact medical details that are not needed to evaluate an accommodation or dispute.
3.8 Information From Other Sources
We may receive information from:
● Facility Operators, their authorized employees, tenants, and businesses;
● drivers, vehicle owners, renters, fleet managers, Account Users, witnesses, or authorized agents;
● payment processors, fraud-prevention services, banks, and chargeback networks;
● state motor-vehicle agencies and authorized vehicle-record providers;
● camera, connectivity, hosting, analytics, mailing, customer-support, dispute, and collection providers;
● public records and legally authorized sources; and
● another party to a transaction, dispute, or legal process.
4. How We Use Information
We may use Personal Information to:
● provide, operate, configure, secure, maintain, and improve the website, app, dashboard, and parking services;
● create and administer accounts, authenticate users, assign roles, and prevent unauthorized access;
● recognize entry and exit events, match paid sessions or permits, calculate duration, and apply property-specific parking rules;
● validate destination use, loading activity, exemptions, or other authorized parking;
● process ordinary parking fees, refunds, receipts, settlements, and revenue allocations;
● review event evidence and decide whether to issue, void, reduce, refund, or pursue a private Parking Charge;
● identify a legally authorized notice recipient for a specific eligible event;
● send notices, administer disputes and appeals, answer support requests, and collect lawful amounts;
● detect fraud, manipulated evidence, account abuse, security incidents, payment misuse, or technical errors;
● perform quality assurance, camera calibration, accuracy testing, audits, reporting, and product improvement;
● communicate about a requested service, inquiry, account, transaction, legal notice, or material policy change;
● comply with law, contracts, lawful process, tax, accounting, insurance, safety, and recordkeeping duties;
● establish, exercise, or defend legal claims; and
● create deidentified or aggregated statistics that are not reasonably linkable to an individual.
We do not use ALPR Data or incidental images of people to identify a person for advertising, track a person away from supported parking facilities, or infer race, religion, health, immigration status, political affiliation, sexual orientation, or other sensitive traits.
Veritas and its providers do not use identifiable ALPR Data, scene video, movement evidence, motor-vehicle-record information, payment data, dispute evidence, or account content to train general-purpose artificial-intelligence systems or large-language models. Parking-specific systems may be tested or improved with synthetic, aggregated, or lawfully deidentified information under documented controls. A provider may not use identifiable Veritas parking information to train its own unrelated model.
Veritas does not furnish Parking Charges or related payment history to consumer reporting agencies.
5. The Four Supported Parking Models
The processing that occurs at a particular facility depends on posted rules and the Facility Operator's selected configuration.
5.1 Paid LPR Parking
The system may compare a vehicle's plate and time at the facility with a prepaid or pay-on-exit session, extension, exemption, or permit. At an open facility, the posted terms may allow a limited period to purchase parking or extend an expiring session. At a gated facility, payment may be handled as part of exit.
5.2 Destination-Use or Walk-Off Parking
Parking may be authorized while at least one occupant visits an approved destination, for a stated maximum time, for a stated period following a visit, or under another posted rule. Time-linked event evidence may be used to determine whether a qualifying visit occurred.
5.3 Hybrid Parking
A vehicle may be authorized either through payment or through a qualifying destination visit, as stated on the facility's signs. We may compare ALPR, payment, permit, and destination-use information to apply that rule.
5.4 Authorized App-Based Enforcement
An authorized Facility Operator or business user may submit a documented parking event through the app. The submission may include a plate, location, time, images, notes, and the submitter's account identity. A submission does not by itself create a charge. Veritas applies eligibility, evidence, legal, and human-review controls before further action.
6. Automated Tools and Human Review
Technology may detect plates, calculate time, compare a permit or paid session, associate views of a Parking Event, or flag a possible rule violation. These tools can make mistakes because of glare, weather, plate obstruction, clock or payment errors, camera angle, similar vehicles, or incomplete evidence.
Veritas does not intend to make a final decision to issue a Parking Charge solely through automated processing. A trained person reviews the available evidence and applicable rule before issuance. A person also reviews a timely dispute and may correct a plate read, timestamp, vehicle match, payment match, or other error.
We do not use parking images for facial recognition or biometric identity matching. We do not make decisions producing legal or similarly significant effects about employment, housing, credit, education, insurance, or healthcare.
7. When We Disclose Information
We may disclose information in the following circumstances.
7.1 Facility Operators and Authorized Account Users
We may provide facility-level event, payment, permit, validation, occupancy, enforcement, dispute, and financial reports to the Facility Operator and its authorized users. Access is limited by role and property. We do not ordinarily provide a Facility Operator with unrestricted motor-vehicle-record information when summary information is sufficient.
7.2 Service Providers and Processors
We may use providers for cloud hosting, databases, cybersecurity, app distribution, authentication, communications, analytics, camera systems, connectivity, payment processing, vehicle-record access, printing, mailing, customer support, dispute administration, accounting, and lawful collection.
For example, Veritas may use Clancy Systems International, Inc. of Denver, Colorado, including its case-administration services, or another approved provider for eligible vehicle-record lookup, notice production and mailing, payment or collection support, and related case administration. A case-administration service may be identified as ClientSeat in the applicable workflow.
Providers receive only information reasonably needed for their assigned services and must be subject to appropriate confidentiality, use, security, deletion, and legal-compliance terms. Veritas remains responsible for selecting and overseeing its providers to the extent required by applicable law.
7.3 Payment and Financial Participants
We may disclose transaction data to the Facility Operator, merchant of record, Stripe or another payment processor, banks, card networks, fraud-prevention services, tax providers, accountants, and payout recipients as necessary to authorize, settle, refund, reconcile, report, or challenge a payment.
7.4 Legal, Safety, and Corporate Events
We may disclose information:
● when required by a valid subpoena, court order, warrant, or other binding legal process;
● to respond to a documented emergency involving imminent risk of death or serious physical harm, where disclosure is lawful and necessary;
● to protect rights, safety, property, services, users, or the public, consistent with applicable law;
● to investigate fraud, abuse, or a security incident; or
● as part of a merger, financing, reorganization, sale, bankruptcy, or transfer of all or part of the business, subject to appropriate protections and notice where required.
We do not provide routine, unrestricted, or real-time access to ALPR systems to law enforcement. Requests are evaluated individually and logged where required.
7.5 With Direction or Consent
We may disclose information when an individual directs us to do so, provides legally valid consent, or uses a feature that necessarily sends information to a selected recipient.
8. Sale, Sharing, Targeted Advertising, and Global Privacy Control
As of the Effective Date:
● Veritas does not sell Personal Information for money or other valuable consideration as those terms are defined by applicable comprehensive state privacy laws.
● Veritas does not share Personal Information for cross-context behavioral advertising.
● Veritas does not process Personal Information for targeted advertising based on activity across unrelated websites or services.
● Veritas does not knowingly sell or share the Personal Information of individuals under 18.
Because we do not currently engage in these activities, an opt-out is not necessary to stop them. If our practices change, we will update this Policy, provide required notice and controls, and honor legally recognized browser-based opt-out preference signals, including Global Privacy Control, where required.
Our website does not currently respond differently to legacy "Do Not Track" browser signals because there is no uniform legal or technical standard for those signals. Third parties may collect information about activity over time and across services only as described in this Policy and their own notices. We do not authorize them to use Veritas parking data for unrelated behavioral advertising.
9. Sensitive Information, Precise Location, and Sensitive Locations
Veritas uses sensitive Personal Information only as reasonably necessary to provide requested parking, account, security, payment, dispute, accessibility, and legal-compliance services, or with consent where required.
The app requests camera, photo-library, notification, or device-location permission only for a disclosed feature. A user may change device permissions, although a feature may not work without necessary access. Unless a user deliberately enables a location-based feature, Veritas does not need continuous background device location for ordinary parking enforcement. We do not sell precise geolocation.
Parking data collected at or near healthcare, reproductive-health, mental-health, substance-use, religious, immigration, shelter, school, or other legally sensitive locations may create heightened risk or be treated as sensitive or consumer-health data. Veritas will not activate camera-based production enforcement at a sensitive location unless a documented legal and privacy review approves the use and the required separate notice, consent, contract, geofencing, access, and retention controls are in place. Where Washington's My Health My Data Act or a similar law applies, Veritas will provide the required separate Consumer Health Data Privacy Policy and consent or authorization workflow before collecting covered data.
In Connecticut and any other state that treats a plate-and-location event, exact facility location, or related movement information as regulated precise geolocation or other sensitive data, Veritas will not activate the covered non-payment processing until it has completed the required data-protection assessment, processor controls, notice, and opt-in consent. Entrance signage alone is not treated as affirmative consent when the governing law requires a separate, specific choice.
Veritas does not intend to infer a person's health condition, diagnosis, treatment, religion, immigration status, or other sensitive trait from a parking visit.
10. Data Retention and Deletion
We keep Personal Information only for the period reasonably necessary for the stated purpose, subject to shorter state-specific limits, legal holds, and mandatory accounting or recordkeeping duties. Our current maximum operational retention schedule is:
● Unpreserved continuous or routine camera footage: up to 7 days.
● Non-case ALPR and entry/exit events that do not support an active transaction, permit, security incident, or charge: up to 30 days.
● Issued-charge and dispute evidence: while the charge, dispute, appeal, refund, or lawful collection is active and ordinarily for 90 days after final resolution. A minimal notice, transaction, dispute, settlement, and collection record may be kept for up to 5 years after final closure when needed for a documented claim or legal duty. Raw scene video and ALPR capture data are not kept for that full period unless a specific legal hold or law permits it.
● Motor-vehicle-record access and disclosure audit logs: at least 5 years or a longer period required by the source or law. The underlying owner name and address are deleted when the authorized notice, dispute, or collection purpose ends unless a documented legal duty requires limited continued retention.
● Paid-parking, payout, tax, and accounting records: up to 7 years after the transaction or longer if tax law requires.
● Active account profile and configuration data: for the account term; ordinarily deleted or deidentified within 30 days after a verified deletion request, except for retained transaction, case, security, or legal records.
● Website sales inquiries: up to 24 months after the last substantive contact, unless the person becomes a customer or requests earlier deletion.
● Support, security, login, and diagnostic logs: generally up to 24 months.
● Backups: protected from ordinary use and overwritten on a rolling basis, generally within 90 days after deletion from active systems.
We may preserve a specific record longer when necessary for a documented litigation hold, binding legal process, fraud or security investigation, contractual claim, or other legal duty. When the exception ends, the record returns to the applicable schedule.
10.1 State-Specific ALPR Limits
● Maine: Veritas does not authorize private ALPR collection or use in Maine. Camera-based ALPR and Walk-Off production features must remain disabled in Maine unless a later change in law and written Maine legal approval expressly permit them.
● Arkansas: Unless written Arkansas legal approval establishes that a different statutory category and period applies, captured plate images, plate numbers, and associated ALPR capture data for a private facility are deleted no later than 60 days after capture. A case record retained after that date must exclude the covered ALPR capture data unless applicable Arkansas law expressly permits continued retention. Where Arkansas law requires a shorter period, published rules, destruction procedures, access limits, or periodic public statistics, Veritas will apply those requirements before activation.
● Other jurisdictions: A shorter local or state limit overrides the general schedule.
Deletion means secure destruction or irreversible deidentification consistent with system capabilities. Aggregated or deidentified information may be retained if we take reasonable measures not to reidentify it.
When we maintain deidentified information, we publicly commit to keep and use it only in deidentified form and not attempt to reidentify it, except to test whether deidentification safeguards remain effective. A recipient must be subject to an equivalent restriction.
11. Security and Accuracy
We use administrative, technical, and physical safeguards designed for the nature of the information, including role-based access, least-privilege controls, authentication, encryption in transit and at rest where appropriate, logging, vendor review, secure development and change controls, incident response, and workforce training.
No system is perfectly secure. Anyone who believes information or an account has been compromised should contact us promptly.
We use quality controls to evaluate plate-read and event accuracy. A Parking Charge should not be issued when the plate, vehicle, property, rule, timestamp, payment status, or supporting evidence cannot be reasonably confirmed. Individuals may challenge inaccuracies through the dispute channel on the notice or by contacting us.
12. Privacy Rights
Depending on residence, context, and applicable law, an individual may have the right to:
● confirm whether we process Personal Information;
● access or obtain a copy of Personal Information;
● correct inaccuracies;
● delete Personal Information;
● obtain a portable copy of information supplied to us;
● obtain a list of categories, or in some states specific identities, of third parties to which information was disclosed;
● opt out of sale, sharing, targeted advertising, or qualifying profiling;
● limit certain uses or disclosures of sensitive Personal Information;
● withdraw consent for processing based on consent;
● appeal a denial of a privacy request; and
● receive equal service without unlawful discrimination for exercising a privacy right.
These rights are subject to exceptions. For example, we may retain information needed to complete a transaction, maintain security, comply with law, preserve a dispute or legal claim, or exercise another legally recognized exception.
12.1 How to Submit a Request
A request may be submitted by:
● emailing support@veritasparkinggroup.com with the subject "Privacy Request";
● calling +1 (561) 453-1517;
● using the account-deletion or support feature in the Veritas app, if available; or
● writing to the address in Section 24.
Please describe the right requested and provide enough information to identify the relevant account, vehicle, transaction, or record. Do not email a full payment-card number, Social Security number, driver's-license image, or unnecessary medical information.
We will verify a request proportionately to its sensitivity. Verification may require access to the relevant email or account, transaction details, invoice reference, vehicle relationship, or a signed declaration. We will not use verification information for another purpose.
We generally respond within 45 days, subject to a legally permitted extension. If we deny a request, we will explain the reason and, where applicable, how to appeal. An appeal may be submitted to the same address with the subject "Privacy Appeal" within 60 days of the decision.
An authorized agent may submit a request where permitted. We may require proof of authority and may directly verify the request with the individual unless law provides otherwise.
12.2 California Notice at Collection
During the preceding 12 months, Veritas may have collected the categories described below, depending on the service used:
● identifiers, including name, contact information, account ID, IP address, vehicle plate, and device identifiers;
● customer and commercial information, including parking sessions, payments, permits, charges, disputes, and service history;
● internet or electronic network activity, including website, app, dashboard, login, diagnostic, and interaction data;
● geolocation information, including a parking-facility location, ALPR capture location, and device location when an enabled feature requires it;
● sensory information, including vehicle and event photographs or video and incidental images of people;
● professional or employment-related information supplied by business Account Users;
● sensitive Personal Information, such as account credentials, precise geolocation when enabled, payment-account information handled through a processor, and limited accommodation information voluntarily submitted; and
● inferences limited to parking eligibility, event status, fraud or security risk, and service configuration.
We collect these categories from the sources in Section 3, use them for the purposes in Sections 4 and 5, and disclose them to the categories in Section 7. We do not sell or share them for cross-context behavioral advertising. Retention criteria and maximum periods are in Section 10. Veritas does not offer a financial incentive in exchange for Personal Information.
California residents may exercise applicable rights to know, access, correct, delete, and receive information about disclosure, and may use an authorized agent. If Veritas later sells or shares Personal Information, we will provide a "Do Not Sell or Share My Personal Information" mechanism and honor Global Privacy Control as required. California residents may also ask about the limited use of sensitive Personal Information; Veritas currently uses it only for permitted service, security, payment, legal, and requested purposes.
13. California ALPR Usage and Privacy Supplement
This Section is Veritas's public ALPR usage and privacy policy for California operations. It applies in addition to the rest of this Policy.
13.1 Authorized Purposes
ALPR systems may be used only to administer clearly posted rules at an approved private parking facility, including entry and exit measurement, paid-session or permit matching, destination-use review, documented Parking Charge review, dispute resolution, system security, quality assurance, and legally required records. ALPR Data may not be used for personal curiosity, employee monitoring unrelated to parking, immigration enforcement, political activity, advertising, or tracking away from supported facilities.
13.2 Authorized Roles and Training
Access is limited to personnel whose job responsibilities require it, including trained parking-event reviewers, dispute and customer-support reviewers, system and security administrators, privacy and compliance personnel, and specifically authorized service-provider personnel. Each user must receive role-appropriate privacy, security, accuracy, permissible-use, incident-reporting, and legal training before access and periodically thereafter.
13.3 Monitoring and Audits
Access must use an individually assigned account. Veritas records access or disclosure details required by law, which may include date and time, plate or record queried, user, purpose, and recipient. Supervisors, security personnel, or the Privacy and Compliance Officer review access logs and conduct periodic audits for unauthorized access, unusual queries, excessive export, and compliance with purpose and retention limits. Suspected misuse may result in access suspension, discipline, contract termination, and legal reporting.
13.4 Accuracy and Correction
ALPR output is treated as a lead requiring validation, not conclusive proof. Before issuing a Parking Charge, a trained reviewer must compare available images, plate characters, issuing jurisdiction, vehicle characteristics, timestamps, facility rules, payment or permit status, and other relevant evidence. A person may challenge a plate read or associated event through the dispute channel stated on a notice or through Section 24. Confirmed inaccuracies will be corrected, annotated, or deleted as appropriate, and downstream recipients will be notified where required.
13.5 Sharing and Restrictions
ALPR Data may be disclosed only to:
● the relevant Facility Operator or an authorized user with a parking-related need;
● a contracted provider performing hosting, camera, security, mailing, dispute, payment, or other approved services;
● a vehicle-record provider for a documented, legally authorized case;
● an individual or authorized agent seeking that individual's record;
● law enforcement or another government entity pursuant to binding legal process or a documented lawful emergency; or
● another recipient when the individual directs the disclosure or law expressly authorizes it.
Contracts and access controls must restrict a recipient to the approved purpose, prohibit unauthorized sale, advertising, tracking, or redisclosure, require reasonable security, and require return or deletion. Veritas does not provide unrestricted feeds, bulk exports, or routine real-time access to law enforcement.
13.6 Custodian
The official custodian responsible for California ALPR Data is the Veritas Privacy and Compliance Officer, Veritas Parking Group LLC, 433 Plaza Real, Suite 275, Boca Raton, Florida 33432, support@veritasparkinggroup.com, +1 (561) 453-1517.
13.7 Retention and Destruction
California ALPR Data follows the definite periods in Section 10. Non-case ALPR Data is deleted within 30 days. ALPR Data preserved as evidence for an issued charge, dispute, security incident, or legal matter is kept only for the applicable case period and then securely deleted or irreversibly deidentified. A legal hold must identify the specific record, reason, approving person, and review date. Destruction occurs through secure deletion, cryptographic erasure, overwrite, or another method appropriate to the system and media.
14. Motor-Vehicle Records and the DPPA
State motor-vehicle records are regulated by the federal Driver's Privacy Protection Act and state law. A parking invoice, private contract, or website statement does not by itself create a permissible purpose.
Veritas requires, before an owner lookup:
● a specific, documented Parking Event supported by reviewed evidence;
● identification of the exact federal and state legal authority relied upon;
● an authorized provider and contract that permits the lookup;
● an individual user, date, purpose, query, and disclosure log;
● use and disclosure limited to that case and authorized purpose; and
● retention and destruction consistent with the provider's rules and applicable law.
Veritas does not use motor-vehicle records for marketing, lead generation, unrelated analytics, bulk identification, or general surveillance. If lawful access is unavailable in a jurisdiction or for an event type, Veritas will not conduct the lookup.
15. Children's Privacy
Veritas accounts and digital services are intended for adults who are at least 18 years old and authorized to enter the relevant transaction or act for a business. They are not directed to children under 13, and we do not knowingly collect online Personal Information from a child under 13 without legally required parental consent.
Parking cameras may incidentally capture children in a public-facing parking environment. We do not use those images to identify, profile, or market to children. If a parent or guardian believes a child submitted Personal Information through an account or online feature, the parent or guardian may contact us for review and deletion, subject to legal exceptions.
16. Account Deletion and Offboarding
An Account User may request deletion through the in-app account-deletion feature, if available, or through Section 12. Deleting the app from a device does not delete the account.
Following a verified request, we delete or deidentify the active profile and revoke access, subject to records we must retain for payments, taxes, permits, security, issued cases, disputes, contracts, legal claims, or law. We will explain material retention categories when responding. A Facility Operator may retain information independently under its own policy.
When a business relationship ends, Veritas removes or disables the Facility Operator's dashboard access and processes return, deletion, or retention according to the services agreement, applicable law, active cases, and backup schedule.
17. Communications
We may send transactional or legally required communications about an account, parking session, payment, receipt, dispute, security issue, policy change, or service request. These are not marketing messages.
Where we send promotional email or text messages, we use the consent and opt-out procedures required by law. Opting out of marketing does not stop transactional or legal communications. We do not use ALPR, vehicle-record, dispute, or parking-event information for unrelated marketing.
18. Data Breach and Incident Response
Veritas maintains procedures to identify, contain, investigate, remediate, and document security incidents. We notify affected individuals, regulators, Facility Operators, or other parties when and as required by applicable law or contract.
19. International Processing
Veritas is based in the United States, and the services covered by this Policy are directed to the United States. Information may be processed in a state other than the state where it was collected. If authorized personnel or providers process information outside the United States, we use contractual, access, and security safeguards appropriate to the information and applicable law.
This Policy does not waive rights under a law that applies because of the individual's location or our processing activities.
20. Third-Party Sites, App Stores, and Services
Our services may link to a Facility Operator, payment processor, map, app store, authentication provider, or other third-party service. That third party's terms and privacy notice govern its independent practices.
Apple and Google may process app-download, purchase, device, diagnostics, and account information under their own policies. Veritas's App Store privacy details and Google Play Data Safety disclosures are intended to describe the app and its integrated providers. If a store disclosure and this Policy appear inconsistent, please notify us so we can investigate and correct the disclosure or practice.
21. State and Local Supplements
Veritas may publish a state, city, property, or service-specific privacy supplement when required or appropriate. A supplement is part of this Policy for the covered processing. If a supplement conflicts with this national Policy, the supplement controls for that jurisdiction or service.
Making the app available for download in a state does not mean that every camera, ALPR, Walk-Off, payment, vehicle-record, or enforcement feature is legally or operationally available there. Production features are activated only after state and site approval.
22. Changes to This Policy
We may update this Policy to reflect changes in services, law, providers, or practices. The current version will identify its Effective Date and version number.
For a material change, we will provide notice appropriate to the change and the affected service, such as an app notice, account message, email, website banner, or updated notice at collection. Where law requires consent, we will obtain it before applying the change to covered information. Merely posting a materially changed policy will not substitute for consent or notice when either is legally required.
23. Accessibility and Languages
Individuals who need this Policy or a privacy-request method in an accessible format may contact us. A translated version may be provided for convenience. Unless law requires otherwise, the English version controls if a translation conflicts with it.
24. Contact Us
Veritas Parking Group LLC Attn: Privacy and Compliance Officer 433 Plaza Real, Suite 275 Boca Raton, Florida 33432 United States
Email: support@veritasparkinggroup.com Telephone: +1 (561) 453-1517 Website: https://www.veritasparkinggroup.com/privacy
For a dispute about a specific Parking Charge, use the dispute instructions on the notice so the request reaches the correct reviewer and deadline. A privacy request does not automatically pause a payment or dispute deadline, although Veritas will not use a privacy process to prevent the exercise of a legally available parking dispute.
