Scope and platform purpose
PlacePulse is a private-preview Market Signal Intelligence and place decision platform for physical-location decisions. It helps authorized users interpret source-labelled place evidence, imported review snapshots, visitation context, public benchmarks, climate and resilience context, data freshness, missing evidence, and Meridien analyst workflows for decisions about locations, districts, retail assets, tourism destinations, and media / OOH environments.
The platform is not intended to make automated legal, eligibility, employment, credit, healthcare, or similarly regulated decisions about individuals.
PlacePulse is not designed for individual tracking and does not present individual visitor profiles.
Information we may collect
Account and contact data, such as name, business email address, organization, role, access requests, support correspondence, and similar information provided by users or customer representatives.
Usage analytics and operational telemetry, such as pages viewed, feature interactions, session metadata, browser and device information, performance events, and diagnostic logs used to operate, secure, and improve PlacePulse.
Location and place intelligence inputs, such as location names, geographic references, market context, visitation context, directional visit movement signals, review signals, sentiment signals, evidence notes, uploaded source materials, or customer-provided analysis context.
Visit movement context, where used, is directional or aggregated unless expressly supported by a verified provider scope.
Form submissions, including demo requests, request-access submissions, contact forms, briefing requests, and other inbound messages we receive through the platform or related forms.
Email and contact records, including messages exchanged with the PlacePulse team about access, support, privacy, security, or commercial questions.
API and audit data, such as request metadata, route activity, status codes, timestamps, integration identifiers, authentication events, and security events needed for reliability and access control.
AI assistant interactions, including prompts, questions, context passed to Meridien, generated responses, feedback, and related evidence packets used to provide analyst-style outputs.
How we use information
We use information to provide PlacePulse features, operate dashboards, generate reports, support Meridien analyst workflows, deliver API functionality, maintain customer access, and respond to support or commercial enquiries.
Information may also be used for security monitoring, abuse prevention, debugging, performance improvement, product analytics, service reliability, and retention or compliance workflows.
PlacePulse outputs are intended to support human review, planning, prioritization, and business decision-making. Customers remain responsible for validating outputs before relying on them.
Security, audit logs, and access monitoring
PlacePulse uses technical and operational controls intended to restrict access to platform systems, credentials, source data, and customer information.
Controls may include role-based access, secure secret handling, environment separation, authentication, audit logs, least-privilege practices, request logging, and monitoring for service reliability and abuse prevention.
Access logs and security logs may include device, browser, and IP metadata where applicable, along with route activity, timestamps, and user-agent information needed to investigate suspicious or unauthorized use.
No internet-connected service can guarantee absolute security. Customers should use appropriate access controls, contractual safeguards, and internal governance when using the platform.
Service providers and API processing
PlacePulse may rely on third-party infrastructure and service providers for hosting, databases, authentication, mapping, AI processing, voice features, observability, analytics, and operational support.
Providers may process relevant information only as needed to support the service, subject to applicable provider terms, customer agreements, and configured safeguards.
Provider or API processing may change as the product and deployment architecture evolve.
Retention
Information is retained for as long as reasonably necessary to provide the service, maintain records, satisfy security and operational needs, support customer relationships, and meet legal or contractual requirements.
Retention periods may vary depending on the type of data, the customer agreement, operational requirements, deletion requests, and backup or audit-log practices.
Access, correction, and deletion requests
Users or customer administrators may request access, correction, or deletion of account-related personal data by contacting support@arqonelabs.com.
Some records may be retained where necessary for security, legal, contractual, backup, dispute resolution, or legitimate business purposes.
Regional privacy laws and customer responsibilities
PlacePulse is designed to support privacy-conscious operation and customer compliance workflows, including where customers may have obligations under applicable data protection laws such as GDPR, UAE PDPL, Saudi PDPL, or similar frameworks.
Customers remain responsible for ensuring their own use of the platform, uploaded data, source materials, retention choices, notices, permissions, legal bases, and downstream decisions comply with applicable laws and contracts.
PlacePulse should not be used to upload unnecessary sensitive personal data unless covered by appropriate legal basis, contract terms, customer instructions, and safeguards.
Contact
Questions or privacy-related requests can be sent to support@arqonelabs.com.
Private-preview reference for PlacePulse privacy practices.