Security
ParkTek is built for environments where digital decisions can affect physical vehicle access. Our approach is to keep access scoped, actions traceable and connected systems limited to the permissions and operating purpose of each deployment. No connected system can guarantee complete security, so controls are reviewed and improved as products and deployments evolve.
Access to ParkTek dashboards, workflows and administrative functions is limited to authorised users and the relevant society, property or operating context.
Customer or site administrators are responsible for assigning appropriate permissions to their teams. Access should be removed or updated when a user’s role or relationship with the deployment changes.
Users should protect passwords, OTPs, devices and other authentication information and must not share them with unauthorised persons.
ParkTek may use authentication, session controls and other safeguards appropriate to the applicable product. Suspected unauthorised access should be reported promptly.
Production website and API traffic uses HTTPS/TLS. Security controls for storage, backups and supporting infrastructure may vary by product and deployment and are reviewed according to the applicable operating requirements.
ParkTek does not represent every customer environment as identical; deployment-specific controls may depend on the approved architecture, integrations and customer responsibilities.
Vehicle registration numbers, RFID identifiers, plate images or ANPR results, where enabled, are used only for the approved parking, access, support or operational purpose of the deployment.
Access to this information should remain limited to authorised users with a legitimate operating need. ParkTek does not use ANPR for facial recognition.
ParkTek systems may retain relevant access, controller, operator and support events so authorised teams can review activity, investigate exceptions and troubleshoot incidents.
The availability and retention of particular records depends on the product, deployment, customer requirements and applicable law.
Connected gate workflows are designed to act on configured identity, permit and site rules. Unknown or ineligible vehicles should not automatically receive access by default.
Societies, properties and operators remain responsible for the permissions and site rules they configure or instruct ParkTek to implement.
ParkTek deployments may depend on controllers, readers, cameras, barriers, local networks and external connectivity. Where supported, local controller logic can continue using synchronised permit information and queue events during temporary connectivity interruptions.
Hardware, power, network or third-party failures can still affect availability, and recovery depends on the configuration of the applicable site.
Some ParkTek features may integrate with cloud, communications, payment, hardware or other authorised service providers. Those providers operate their own systems and security controls.
ParkTek seeks to use third parties only where necessary for an approved service and applies contractual or technical safeguards appropriate to the relationship where applicable.
If you believe you have identified a security issue affecting a ParkTek website, application, account, connected deployment or API, please report it responsibly.
Include the affected service or site, an approximate time, steps to reproduce where relevant and a clear description of the concern. Do not send passwords, OTPs, access tokens or unnecessary personal data.
