PRIVACY POLICY

Parking Guidance Systems
Review our privacy policy to learn how we collect, use, protect, and manage your personal information when you use our website and services.

Last updated: October 6, 2026
Effective: September 30, 2026

At a Glance

Facility Operators control their sites

PGS provides parking technology. Facility Operators manage their own sites, determine how their systems are used, and control parker-facing notices and operating policies.

We do not sell parking data

PGS does not sell Facility Operator parking data or commercialize it through advertising, data brokers, insurance products, repossession services, shared plate databases, or aggregate parking-data products.

Retention is configurable

Vehicle/plate images are commonly retained for 30 or 60 days. Plate characters, parking-session data, and space/occupancy linkages commonly default to 7 years. Facility Operators may direct PGS to use different retention periods.

No DMV lookup or facial recognition

PGS does not identify vehicle owners through DMV or registration databases and does not apply facial recognition or other biometric identification to captured images.

No continuous PGS video surveillance

PGS does not store continuous surveillance video or provide live/recorded surveillance viewing. A Facility Operator may separately route a camera stream to its own third-party video system.

Website tracking requires consent

Google Analytics and HubSpot optional tracking technologies remain disabled until a visitor accepts optional cookies.

Contents

  1. Scope and Introduction
  2. Our Role: Controller vs. Processor
  3. Information We Collect
  4. Children
  5. Cookies, Website Analytics, and Tracking
  6. Notice at Collection
  7. How We Use Information
  8. Automated Processing and Operational Alerts
  9. Automated License Plate Recognition (ALPR/LPR)
  10. Retention
  11. Disclosure of Information
  12. Your Choices
  13. Privacy Rights
  14. Security
  15. Hosting and Data Residency
  16. EEA, UK, and Switzerland
  17. Third-Party Links and Integrations
  18. Changes to This Privacy Policy
  19. Contact Us

1. Scope and Introduction

Parking Guidance Systems, LLC (“PGS,” “we,” “us,” or “our”), together with its subsidiaries and affiliates where applicable, respects privacy and is committed to handling personal information responsibly.
This Privacy Policy explains how PGS collects, uses, maintains, protects, retains, and discloses personal information in connection with parkingguidancesystems.com, PGS applications and software platforms (including PGS Pulse, IVIS, and PGS Mobility), PGS-powered parking systems, and other PGS products and services (collectively, the “Services”).
This Privacy Policy is a notice describing our practices. Where applicable law requires consent for a particular processing activity, PGS obtains that consent separately.
This master policy applies to PGS products and services unless PGS provides a supplemental privacy notice for a specific product or service. If a supplemental notice applies, it governs the specific processing described in that notice.

2. Our Role: Controller vs. Processor

2.1 PGS as controller/business

PGS acts as a controller, or as a “business” where that term applies under U.S. state privacy law, when PGS determines the purposes and means of processing personal information for its own business activities. Examples include website and marketing data, business-contact information, sales and contracting records, support and training communications, and accounts that PGS directly administers.

2.2 PGS as processor/service provider

PGS generally acts as a processor or service provider for parking, vehicle, occupancy, reservation, and Facility Operator account data generated or stored in systems used by airports, healthcare systems, universities, municipalities, corporate campuses, mixed-use developments, parking operators, and other Facility Operators.
The Facility Operator manages its own parking site and determines how the system is used. PGS processes Facility Operator data under a written Data Processing Agreement or equivalent contractual terms and only for authorized service, support, maintenance, configuration, reporting, troubleshooting, and related purposes.
PGS systems include configurable retention controls. PGS provides standard/default settings, but a Facility Operator may direct PGS to use shorter or longer retention periods to align with the Facility Operator’s legal, contractual, operational, or internal retention policies. Longer retention may require additional storage capacity.
PGS does not combine parking data across Facility Operators to build profiles of individuals or vehicles. Customer data remains in the applicable customer-controlled environment or is segregated within the applicable cloud-hosted environment.
If you are a driver, visitor, employee, or other person whose vehicle or information was captured at a Facility Operator site, the Facility Operator generally controls that data. Requests concerning that information should normally be directed to the Facility Operator. If you contact PGS, we may refer the request to the Facility Operator or assist the Facility Operator as required by contract and law.

3. Information We Collect

The personal information PGS handles depends on the product, deployment model, Facility Operator configuration, and how an individual interacts with the Services.
CATEGORYEXAMPLES
Business identifiers and contact dataName, business email, telephone number, postal address, employer, job title, account name, and similar business-contact information.
PGS commercial relationship dataRecords of PGS products or services purchased, licensed, requested, or considered, and related sales, contracting, onboarding, training, and account-management information.
Website and application activityInteractions with the PGS website or applications, including page views, session activity, device information, and IP address.
GeolocationApproximate geographic location derived from IP address. PGS Mobility may also access precise device location when a user enables location permissions; precise GPS location is used in real time and is not retained as a historical location record.
Vehicle and ALPR dataLicense plate characters; the state associated with a plate where the system is able to determine it; vehicle images captured by LPR/camera systems; vehicle type; and, where entered by the Facility Operator, vehicle make, model, color, and parker name.
Parking operational dataParking sessions/transactions, reservations, entry/exit times, dwell duration, parking-space location, occupancy status, counts, and operational alerts. Space-level data may remain linked to a specific plate and session during the configured retention period.
Account informationUsername, hashed password, role assignments, and permission assignments.
System and device dataCamera and controller IP addresses, device identifiers, firmware versions, sensor health, alerts, telemetry, and diagnostics.
Audit and access recordsHistorical access, security, and audit records generated by the applicable system or approved remote-support tools.
Support and correspondenceSupport tickets, screenshots, exported reports, log files, chat messages, survey responses, comments, and other correspondence. Support records may contain personal information when it is necessary to diagnose or resolve an issue.
Payment informationPGS does not process or store full payment card numbers. Where payment functionality is integrated with a parking workflow, payment processing is handled by the Facility Operator and/or its designated third-party payment provider.

3.1 Operator-entered data

PGS Pulse can store information entered by a Facility Operator, including a parker name and associated vehicle attributes such as license plate, make, model, and color. PGS does not automatically identify a parker from a plate and does not independently source vehicle-owner identity information.

3.2 Sensitive personal information

PGS may process sensitive personal information such as account credentials and, in PGS Mobility, precise device location when the user enables location services. PGS does not use sensitive personal information to infer characteristics about individuals. Sensitive personal information is used only for the operational, security, account, or location-dependent purposes for which it was collected and as otherwise permitted by applicable law.
A license plate read can reveal that a particular vehicle was at a particular location at a particular time. PGS therefore applies heightened protections to ALPR information, including restricted access, defined retention controls, and limitations on use and disclosure.

3.3 Camera functions and continuous video

PGS camera-based products may be used for occupancy detection, counting, and license plate recognition. PGS does not provide continuous video surveillance, does not store continuous video, and does not provide live or recorded surveillance-video viewing through PGS Pulse or IVIS.
A Facility Operator may choose to route a camera stream to its own third-party video management system. Any recording, retention, security monitoring, or other use of that third-party video system is controlled by the Facility Operator and is governed by the Facility Operator’s policies and systems, not by this Privacy Policy.

3.4 Healthcare sites

PGS systems may be deployed at hospitals and other healthcare facilities, but PGS does not connect to EHR/EMR systems, appointment systems, patient-management systems, medical records, diagnoses, treatment information, medical record numbers, or other clinical systems. PGS provides parking technology and processes parking/vehicle information only.

3.5 How we collect information

PGS collects information directly from individuals; through PGS hardware and software deployed at Facility Operator sites; from Facility Operators; and from trade shows, conferences, and similar business events where individuals provide contact information or permit badge scanning. Trade-event contact information may be stored in PGS’s CRM.

4. Children

PGS Services are not directed to children under 13. PGS does not knowingly collect personal information directly from children under 13 for its own purposes. Where information relating to a minor is processed on behalf of a Facility Operator, the Facility Operator controls that information, and PGS handles requests concerning that information in accordance with the Facility Operator’s instructions and applicable law.

5. Cookies, Website Analytics, and Tracking

The PGS website uses strictly necessary cookies and optional analytics/engagement technologies. Visitors may choose Accept, Decline, or Necessary Only through the website cookie banner.
PGS uses Google Analytics and HubSpot for website analytics, engagement measurement, website interactions, and related business functions. Optional analytics and tracking technologies are not activated until a visitor provides consent through the cookie banner.
Marketing emails may use tracking technologies that allow PGS to determine whether an email was opened or a link was clicked.
PGS does not use standalone advertising, retargeting, or social-media advertising pixels such as Meta Pixel or LinkedIn Insight Tag. Analytics/tracking technologies described in this section are used on the public PGS website and in marketing communications, not in PGS operational applications or on-site guidance, sensor, or LPR hardware.
Website analytics data, including IP-derived approximate location data, is generally retained for up to 3 years.

6. Notice at Collection

PGS provides notices at or before relevant points of collection on the PGS website and in PGS applications. Those notices may identify the categories of information collected, purposes of processing, applicable retention information, and available privacy choices.
Where a Facility Operator uses ALPR/LPR technology, the Facility Operator is responsible for providing any notices, signage, or disclosures required at the facility or through its own communications. PGS does not control the Facility Operator’s signage or communications to parkers and does not determine whether those notices satisfy the Facility Operator’s legal obligations.

7. How We Use Information

7.1 When PGS acts as controller

  • Respond to inquiries, requests for information, and sales communications.
  • Provide quotes, contracting, onboarding, training, support, and client-success activities.
  • Create, administer, and secure PGS-managed accounts.
  • Operate and improve the PGS website and Services.
  • Measure website engagement after consent is provided.
  • Send business-to-business marketing communications, subject to opt-out rights.
  • Detect, investigate, and prevent fraud, misuse, and security incidents.
  • Comply with legal obligations and enforce agreements.

7.2 When PGS acts as processor/service provider

PGS uses Facility Operator data only to operate and support the licensed system; provide technical support; diagnose faults; perform health monitoring, maintenance, configuration, commissioning, integration, upgrades, reporting, and troubleshooting; meet contractual obligations; and comply with law.
Where necessary to diagnose or resolve a support issue, support records may include screenshots, exported reports, log files, license plate information, parker information, vehicle images, or other customer data relevant to the issue. PGS limits use of such information to support, troubleshooting, maintenance, and related service activities.
PGS sales demonstrations use synthetic or test data rather than live Facility Operator personal information.

7.3 Aggregated and de-identified information

PGS may generate aggregated or de-identified information for internal engineering, system reliability, reporting, and product-improvement purposes. PGS does not sell or commercially distribute aggregated or de-identified Facility Operator parking data to third parties.

8. Automated Processing and Operational Alerts

PGS software performs automated license plate recognition, occupancy detection, record matching, and alert generation. Recognition results may be inaccurate because of factors such as plate condition, weather, lighting, camera angle, or unusual plate formats.
PGS does not itself make legal, enforcement, eligibility, access-control, citation, towing, immobilization, fine, or similarly significant decisions. Any action taken by a Facility Operator in response to PGS-generated information or alerts is determined by that Facility Operator.
Authorized users may review the associated vehicle image against recognized plate characters. While a vehicle has an active parking session, an authorized user may correct an inaccurate plate read. Once the parking session has closed, the historical record is not ordinarily editable through the active-session correction function.

9. Automated License Plate Recognition (ALPR/LPR)

9.1 Authorized purposes

PGS uses ALPR/LPR technology to locate vehicles when requested, identify when and where a vehicle parked, support parking-session and revenue reconciliation, support reservations, generate occupancy and utilization reporting, and create operational alerts.
PGS does not use ALPR to identify the registered owner of a vehicle, perform general surveillance, control facility access, issue citations, create formal violation records, or commercially resell plate data.

9.2 Access

Facility Operator administrators control access within their deployments. PGS access to ALPR information is limited to authorized Service personnel and, when technically necessary, authorized developers performing troubleshooting, maintenance, or support activities.
Remote support access depends on the Facility Operator’s requirements. Some customers permit authorized unattended support access; others require the Facility Operator to initiate or approve each session. Approved remote-support tools use individual PGS/INDECT user credentials and maintain connection logs identifying who connected to a customer environment and when. Certain deployments may use a common application-level administrative account for authorized support functions.

9.3 Responsible personnel and training

The PGS Chief Technology Officer is responsible for oversight and implementation of PGS’s ALPR compliance program and serves as the primary internal owner for ALPR-related compliance matters. PGS personnel with ALPR access receive training on permissible use, privacy obligations, and applicable policies at onboarding and annually thereafter, with completion recorded.

9.4 Owner lookup, biometric identification, and shared databases

PGS has no access to state motor-vehicle registration databases and does not perform plate-to-owner lookups against government or commercial registration sources. PGS does not apply facial recognition, gait analysis, or other biometric identification to images captured by its systems.
PGS does not operate, contribute ALPR information to, or draw from shared regional or national license-plate databases or hotlist-sharing networks.

9.5 Law enforcement

PGS does not provide law enforcement with direct or routine access to Facility Operator plate or parking data and does not maintain standing law-enforcement integrations or subscriptions. If PGS receives a request for Facility Operator parking data, PGS normally refers the requester to the Facility Operator and notifies the Facility Operator unless legally prohibited. PGS responds directly only where legally required to do so.

10. Retention

PGS retains personal information only for as long as reasonably necessary for the applicable purpose, contract, Facility Operator instruction, or legal obligation. For Facility Operator deployments, retention is managed through configurable system cleanup controls. Standard/default periods can be shortened or extended at the Facility Operator’s direction, subject to technical storage capacity and applicable law.
DATA CATEGORYSTANDARD/DEFAULTCONFIGURABLENOTES
Vehicle / plate imagesCommonly 30 or 60 daysYesFacility Operator may request a different period. Images are automatically deleted when the configured period is reached.
License plate characters7 yearsYesStored as text for reporting and may remain linkable to historical parking sessions during the configured period.
Parking sessions / transactions and plate-to-space linkage7 yearsYesMay include entry/exit times, dwell duration, facility/space location, and associated plate characters.
Occupancy and count data7 yearsYesUnderlying space-level records may be identifiable; aggregated reports may omit direct identifiers.
ReservationsConfigured by Facility OperatorYesRetention depends on deployment settings and Facility Operator requirements.
System telemetry, alerts, and diagnostics7 yearsDeployment dependentUsed for operational support, reliability, and troubleshooting.
Access / security / audit records7 yearsGenerally noMay remain after a user account is removed.
Platform user accountsWhile activeControlled by Facility OperatorAccount profile and associated operational data are deleted when the user is removed; separate audit/security records may remain.
Closed support tickets and attachments3 years after closureNoAutomatically deleted after the retention period. Closed tickets are restricted within the support platform.
Website analytics3 yearsNoIncludes website IP-derived approximate location data.
Marketing contact records3 years after last meaningful interactionNoLonger retention may apply to an active customer/contractual relationship. Minimal suppression records may be retained to honor opt-outs.
Backups after contract terminationUp to 12 monthsNoUsed only for business continuity/disaster recovery and automatically deleted at the end of the retention period.
When configured retention periods are reached, applicable records are automatically removed according to system retention controls, generally deleting the oldest qualifying data first.
Upon termination or expiration of an agreement, PGS will make Facility Operator data available for return to the Facility Operator in accordance with the applicable contract. Copies retained in backups may be preserved for up to 12 months solely for business continuity and disaster recovery and are not used for routine operational access, reporting, or analytics. Those backup copies are then automatically deleted.

11. Disclosure of Information

PGS does not sell Facility Operator parking data and does not commercialize it through advertising, resale, data-broker relationships, analytics products, insurance products, repossession services, or shared plate-data networks.
PGS does not sell personal information or share it for cross-context behavioral advertising. PGS may disclose personal information only in the following circumstances:
  • To the Facility Operator that owns or controls the applicable Facility Operator data.
  • Where necessary to provide the applicable service, comply with the Facility Operator’s documented instructions, fulfill a specific request made by the individual, or as otherwise required or permitted by law.
  • In connection with a merger, acquisition, restructuring, divestiture, sale of assets, or similar corporate transaction, subject to applicable law, contractual obligations, and the protections described in this policy.
  • To comply with a court order, law, legal process, or legally binding government/regulatory request.
  • With the individual’s consent where consent is required or requested.
PGS does not disclose personal information to third parties for their own direct-marketing purposes.

12. Your Choices

  • Marketing email: use the unsubscribe link in a marketing email or contact service@parkingguidancesystems.com. Transactional, security, outage, billing, or service messages may still be sent where appropriate.
  • Cookies: use the website cookie banner to Accept, Decline, or select Necessary Only. You may also use browser controls to manage cookies.
  • Precise location: revoke PGS Mobility location access through your device settings at any time.
  • Account management: for accounts administered by a Facility Operator, account creation, modification, deactivation, and deletion are controlled by that Facility Operator. Where PGS directly administers an account, requests may be submitted through the privacy channels below.

13. Privacy Rights

Depending on your jurisdiction, you may have rights to access, correct, delete, or obtain a portable copy of personal information; object to or restrict certain processing; opt out of certain sales/sharing or targeted advertising; limit certain uses of sensitive personal information; appeal certain decisions; and exercise rights without unlawful discrimination.
Where PGS processes information on behalf of a Facility Operator, the Facility Operator generally handles the request as controller. PGS may refer the request to the Facility Operator or assist the Facility Operator in responding.

13.1 How to submit a request

Submit a request through our online privacy request form, email service@parkingguidancesystems.com, mail the request to the address in Section 19, or use the privacy-request telephone number listed in Section 19.

PGS will request only the information reasonably necessary to verify the identity or authority of the requester and locate the relevant records. The information required will depend on the nature of the request and the data involved.
Authorized agents may submit requests where permitted by law. PGS may require reasonable evidence of the agent’s authority and may separately verify the individual when permitted or required.
PGS responds to privacy requests within the time required by applicable law. For U.S. state privacy requests, this is generally within 45 days where applicable. Requests subject to the GDPR are handled within the applicable GDPR response period. The scope and lookback period of disclosures are determined in accordance with applicable law.
PGS does not charge for privacy requests unless a fee is permitted by applicable law, such as for requests that are excessive, repetitive, or manifestly unfounded.

13.2 California

PGS does not sell personal information or share it for cross-context behavioral advertising. A Do Not Sell or Share My Personal Information page is available at parkingguidancesystems.com/privacy-request.

PGS does not disclose personal information to third parties for their own direct-marketing purposes and does not offer financial incentives, price differences, or service-level differences in exchange for personal information.

13.3 Other U.S. states

Residents of U.S. states with applicable consumer privacy laws may exercise the rights available to them under those laws through the request methods described in this policy. PGS processes requests in accordance with the requirements of the applicable jurisdiction.

14. Security

PGS maintains administrative, technical, and physical safeguards designed to protect personal information from accidental loss and unauthorized access, use, alteration, or disclosure. Controls include encryption in transit, encryption at rest, role-based access controls, and annual penetration testing by an independent third party.
For customer-hosted or on-premises deployments, network architecture, segmentation, and certain infrastructure controls are managed by the Facility Operator. System and application logs are generally maintained within the applicable deployment environment.
Support access is restricted to authorized personnel and is governed by deployment-specific controls and Facility Operator requirements. Keep your password confidential and do not share it.
Certain PGS products are subject to independent security certifications or attestations. IVIS is covered by ISO/IEC 27001 certification, and PGS Mobility is covered by a SOC 2 Type II examination. Additional security documentation applicable to a product or deployment may be made available to customers or prospective customers subject to appropriate confidentiality requirements.
If a security incident affects Facility Operator data, PGS will notify affected Facility Operators without undue delay and in accordance with applicable contractual and legal requirements. No method of electronic transmission or storage is completely secure, and PGS cannot guarantee absolute security.

15. Hosting and Data Residency

PGS systems may be deployed on-premises within a Facility Operator’s environment, within customer-controlled virtual infrastructure, or in cloud-hosted environments, depending on the product and deployment.
  • Core INDECT/IVIS parking and ALPR deployments are commonly hosted on-premises or within customer-controlled infrastructure.
  • Where IVIS cloud hosting is used, Microsoft Azure is generally the preferred cloud platform.
  • PGS Mobility and PGS Pulse are currently hosted in Google Cloud.
For PGS-managed cloud deployments, hosting regions are selected based on customer location, contractual requirements, and applicable data-protection obligations. Customer data is segregated within the applicable cloud environment.

16. EEA, UK, and Switzerland

Where PGS acts as controller, legal bases for processing may include performance of a contract, consent where required (including for optional cookies and precise device location), legitimate interests in operating, improving, and securing the Services, and compliance with legal obligations.
Individuals in the EEA, UK, and Switzerland may have rights including access, rectification, erasure, restriction, portability, objection, withdrawal of consent, and the right to complain to an applicable supervisory authority.
Where personal information is transferred from the EEA, UK, or Switzerland to a country that does not provide an equivalent level of protection, PGS uses appropriate contractual safeguards, including the European Commission Standard Contractual Clauses and the UK International Data Transfer Addendum where applicable.
PGS support personnel may access customer systems and data from locations outside the hosting region when necessary to provide support, troubleshooting, maintenance, configuration, or other contracted services. Such access remains subject to applicable access controls, confidentiality obligations, and contractual data-protection requirements.
European customers may contract with PGS or an affiliated PGS-owned entity, depending on the applicable product and commercial arrangement. The applicable agreement identifies the contracting entity and the entity responsible for the relevant processing activities.
Questions regarding European privacy or data-protection matters may be directed to service@parkingguidancesystems.com.

17. Third-Party Links and Integrations

PGS Services may link to or integrate with third-party systems, including PARCS platforms, third-party payment providers, Apple Maps and other mapping services, and Facility Operator applications.
Where payment functionality is part of an integrated parking workflow, PGS may exchange parking-session or transaction-related information necessary to support that workflow, but payment card processing is handled by the Facility Operator and/or its designated payment provider, not by PGS.
Third-party services are governed by their own privacy practices and terms. This Privacy Policy does not govern a third party’s independent processing.

18. Changes to This Privacy Policy

PGS may update this Privacy Policy from time to time. Material changes will be posted on the PGS website, and additional notice will be provided where required by applicable law or contract. The revision date at the top of the policy identifies the current version.

19. Contact Us

Parking Guidance Systems, LLC
10111 W Hidden Lake
Richmond, TX 77406

Privacy: service@parkingguidancesystems.com
Privacy requests: service@parkingguidancesystems.com
Phone: (832) 222-2101