Privacy Policy
This policy explains how PlacePulse may handle information used to operate place intelligence, reports, APIs, and Meridien analyst workflows for enterprise customers.
Platform Purpose
PlacePulse is designed as a business intelligence and decision-support platform for place, market, mobility, sentiment, evidence, and executive briefing workflows.
The platform helps customers understand monitored destinations and supporting evidence. It is not intended to make automated legal, eligibility, employment, credit, healthcare, or similarly regulated decisions about individuals.
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 and operational telemetry, such as pages viewed, feature interactions, session metadata, browser or 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, mobility indicators, reviews, sentiment signals, evidence notes, uploaded source materials, or customer-provided analysis context.
Publicly available or third-party source data, such as reviews, listings, maps, venue metadata, and other market signals where available through licensed, public, customer-provided, or third-party providers.
API and log data, such as request metadata, route activity, status codes, timestamps, integration identifiers, and security audit events needed for reliability, debugging, 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.
Enquiry and Contact Form Data
When you submit a contact form, demo request, Investment Brief enquiry, or pilot access request, PlacePulse may collect details such as your name, work email address, company name, job role, and phone number where provided.
Enquiries may include optional context such as your enquiry type, market of interest, number of locations or assets, stated use case, location or asset names, city and country references, decision type, sector, and project or investment timeline.
We use enquiry data to respond to requests, assess data coverage fit, prepare proposals, follow up on pilot or Investment Brief discussions, and improve our commercial process. We do not sell enquiry data to third parties.
Enquiry submissions are stored securely and may be accessed by the PlacePulse team for the purpose of responding to and following up on your enquiry.
How Information Is Used
We use information to provide PlacePulse features, operate dashboards, generate reports, support Meridien analyst workflows, deliver API functionality, and maintain customer access.
Information may also be used for security monitoring, abuse prevention, debugging, performance improvement, customer support, product analytics, and service reliability.
PlacePulse outputs are intended to support human review, planning, prioritization, and business decision-making. Customers remain responsible for validating outputs before relying on them.
Third-Party Processors and Providers
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 include services such as Supabase, Mapbox, OpenAI, ElevenLabs, Netlify, Google services, and other vendors required to provide the platform. Provider use may change as the product and deployment architecture evolve.
Third-party providers process relevant information only as needed to support the service, subject to applicable provider terms, customer agreements, and configured safeguards.
Security and Access Controls
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, and monitoring for service reliability and abuse prevention.
No internet-connected service can guarantee absolute security. Customers should use appropriate access controls, contractual safeguards, and internal governance when using the platform.
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.
Public reference for PlacePulse privacy practices.
