PARALLEX SOFTWARES - FZCO, a free zone company organised and existing under the laws of the Emirate of Dubai, United Arab Emirates, bearing Trade License No. 77188 issued by the Dubai Integrated Economic Zones Authority, with its registered address at DSO-IFZA, IFZA Properties, Dubai Silicon Oasis, Dubai, UAE ("Parallex," "we," "us," or "our"), operates the Parallex platform (the "Platform"), the website at getparallex.com (the "Website") and the project hubs built on the Platform. The Platform is a software-as-a-service solution that enables real estate developers, brokers and related professionals to create, manage and share interactive digital sales and marketing materials for their property developments (each, a "Project"). A project hub is the website through which a Project is presented to the public on behalf of the developer named on it (a "Hub").
This Privacy Policy (the "Policy") explains how we collect, use, disclose and protect personal data (information that identifies or can identify an individual) when you interact with the Platform, the Website or a Hub, whether as a Client, an Authorised User, a sales representative or broker, or an individual who visits a Hub or opens a personal link or a Dealbox (an "End User"). It also explains your rights and how to contact us.
This Policy is issued under the UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (the "UAE PDPL"), which applies to our processing as a company established in the UAE, whether the individuals concerned are inside or outside the UAE. Where the EU General Data Protection Regulation (Regulation (EU) 2016/679) (the "EU GDPR"), the UK General Data Protection Regulation as retained and amended under UK law, including by the Data (Use and Access) Act 2025 (the "UK GDPR"), the Swiss Federal Act on Data Protection (the "Swiss FADP"), the Brazilian General Personal Data Protection Law (Law No. 13,709/2018, the "LGPD"), the Saudi Personal Data Protection Law (the "Saudi PDPL") or the data protection law of Bosnia and Herzegovina applies to you, for example because you visit a Hub from the EU/EEA, the UK, Switzerland, Brazil, Saudi Arabia or Bosnia and Herzegovina, this Policy also sets out the information those laws require.
Our role depends on the personal data concerned:
- Parallex as controller: Parallex decides how and why personal data is processed, and is the data controller, for Client Accounts, billing and support; the Website; communications with Clients and prospective Clients; security and server logs; consent records; the statistics and advertising measurement on Hubs described in section 9; the measurement of how Authorised Users, sales representatives and brokers use the Platform; and the anonymised statistics we create.
- Parallex as processor: We process the following on behalf of others, who are the data controllers: enquiries submitted through a Hub; the activity linked to an enquiry, a personal link or a Dealbox (section 3); buyer records created in a Dealbox; buyers' payment schedules and related documents that a developer records or uploads; and any other buyer or contact information a Client uploads to the Platform. The controller is the developer whose Project it is. Where the sales representative works for a separate brokerage, that brokerage is the controller of the buyer details and activity it sees, and the developer is the controller of the activity it sees without the buyer's identity. We act on their instructions, under our Terms and Conditions with the developer and our terms with the brokerage.
- Advertising: The Meta Pixel on Hubs belongs to Parallex's Meta Business account, and Parallex is the controller of the data collected through it (section 9.4). Campaigns are run by the developer or its agency from their own advertising accounts, and they are the controllers of their campaigns. Meta and Google process the data they receive under their own terms and privacy policies.
Please read this Policy carefully. Where we rely on your consent, we ask for it separately.
1. Information we collect
We collect personal data directly from you, automatically when you use the Platform, the Website or a Hub, and from third parties, as described below. We do not intentionally collect sensitive personal data, such as data about health, religious beliefs, ethnic origin or criminal records.
1.1 Information about Clients and Platform users
- Identity and Profile: Company name, trade license number, corporate registration details, and the names and roles of authorised representatives.
- Contact: Business email, phone number, business address, and the name, designation and contact details of the Client's authorised representative, Authorised Users, and the sales representatives and brokers who use the Platform.
- Billing and Financial Data: Payment status, amounts, invoices and receipts for our services. Today, no payments are made through the Platform, the Website or the Hubs. If payments are added, they will be processed by third-party payment service providers, and we will not store payment card details.
- Project Data: Client Materials submitted through the Platform, such as floor plans, renders, pricing tables and payment plans. Project Data is generally not personal data, except where it contains the details of individuals, such as buyers' payment schedules and related documents that a developer records or uploads.
- Service Records: Quotations, Subscription Fees, Billing Cycles, agreements and records of the services provided.
- Platform Usage Data: How Authorised Users, sales representatives and brokers use the Platform: cookieless visit counts and errors and, with consent, the pages and features used and masked session replays (section 9.5).
1.2 Information about buyers and Hub visitors
- Enquiry Data: Information you submit through a Hub enquiry, contact or comparison form, such as your name, phone number, email address, units of interest and message.
- Dealbox Data: Your name and, where the sales representative has it, your phone number, entered by the representative who creates a Dealbox for you; the items picked for you; the items you save; and the items you ask about.
- Linked Activity: The units, pages and documents you open, view and save on a Hub or in a Dealbox after you submit an enquiry or open a personal link or a Dealbox, and an interest score calculated from it (section 3).
1.3 Information collected automatically
When you visit the Website or a Hub, or use the Platform, we collect technical information: your IP address, browser and device type, the pages you visit and the time of your visit (server logs); your consent choice and country code; and identifiers stored in your browser that keep your selections and personal links working. With your consent, we also collect the statistics and marketing data described in section 9. Section 9 lists each cookie and similar technology, its purpose and how long it is kept.
1.4 Information you choose to provide
You may voluntarily provide information such as business preferences, feedback, survey responses or other notes when you contact us by email, phone or other channels. This includes records of communications for support and complaints.
1.5 Information from third parties
Clients provide the details of their Authorised Users and sales representatives. Sales representatives provide the name and, where they have it, the phone number of the buyers they create a Dealbox for. Google adds demographic and interest categories to Google Analytics statistics (section 9.3).
2. How we use information
We use personal data only for the purposes below. The legal basis for each purpose is explained in section 4.
- Provide and manage the Services: We use identity, contact, billing, project and service record data to create and administer Accounts, configure Projects, issue invoices and deliver the Platform services.
- Communications: We use your contact details to send confirmations, invoices, Project updates, notices of changes to our services, and other transactional or support messages.
- Account management: We use your data to provide Account access, enforce our Terms and Conditions and notify you about changes.
- Customer support: We use identity, contact and communications data to troubleshoot issues, respond to enquiries and resolve complaints.
- Hub operation and enquiries: We use browser identifiers and enquiry data to display Projects, remember your selections while you browse, keep a personal link working and attributed to the sales representative who sent it, and pass your enquiry to the relevant developer and sales representative.
- Personal links and Dealbox: On behalf of the developer and, where relevant, the sales representative's brokerage, we show the activity linked to you and an interest score to them, and send the representative notifications about it (section 3).
- Payment schedules: On behalf of the developer, we store the payment schedules it records and read the documents it uploads, using an AI service, to extract the schedule.
- Security and integrity: We use server logs and error reports to keep the Platform, Website and Hubs running and secure, to detect and prevent fraud and abuse, and to enforce our agreements. We do not use server logs to build profiles of individuals.
- Developer reporting: We show developers statistics on the activity of the sales representatives and brokers who share their Projects.
- Platform improvement: With consent, we record the pages and features Authorised Users, sales representatives and brokers use on the Platform, and masked session replays, to fix problems and improve the Platform (section 9.5).
- Hub statistics: With your consent, we use statistics to understand which Projects, unit types, features and rooms in virtual tours attract interest and to improve the Hubs (section 9.3).
- Advertising: With your consent, we build audience groups for the developer's advertising on Meta and Google (section 9.4). This involves profiling based on the units and features you view.
- Marketing to Clients: With your consent, we send business contacts promotional updates, offers and surveys.
- Aggregated statistics: We create anonymised, aggregated statistics that do not identify you, for reporting and product planning.
3. Personal links, Dealbox and buyer activity
A sales representative or broker can share a Project with a buyer through a personal link or a Dealbox. The Dealbox features described in this section apply once Dealbox is available. A Dealbox is a personal page the representative creates for a buyer, with the buyer's name and, where the representative has it, phone number. The representative sends the buyer one personal link. The link opens without a login: a code in the link works as the key, and the representative can issue a new link at any time. In a Dealbox, you see the units, documents and offers the representative picked for you, can save items, and can ask about an item, which opens WhatsApp with the representative.
- What we record: After you submit an enquiry, or open a personal link or a Dealbox, and agree to your activity being linked to you, we record the units, pages and documents you open, view and save on the Hub and in the Dealbox, and the rooms of virtual tours you visit and the time spent in them, link this activity to your enquiry, link or Dealbox, and calculate an interest score from it.
- Who sees it: For an enquiry, the developer and, where you arrived through a personal link, the sales representative who sent it see your enquiry, your activity and the interest score. For a Dealbox, only the representative who created it sees your identity. The developer sees your activity and the demand it shows, without your name or contact details.
- Notifications: The representative receives notifications about your activity on WhatsApp, for example when you first open the Dealbox, when there is a new pick, when you are active again, and a daily summary. These are sent through the WhatsApp Business Platform, operated by Meta.
- Who decides: We do this on behalf of the developer and, where the representative works for a separate brokerage, that brokerage. They are the controllers of this data.
- Your choices: You can ask the representative, the developer or us at privacy@getparallex.com to stop linking your activity to you at any time. We will act on your request on the controller's behalf.
- New features: We will update this Policy before reservations, payments, identity verification or other new features are added to the Dealbox.
4. When we process information (legal bases)
Under the UAE PDPL, we process personal data with your consent or where the law allows processing without consent. Where we act as processor, the controller decides the legal basis, and where the Platform asks for your consent on the controller's behalf, we record it. We rely on:
- Contract: Where processing is necessary to conclude or perform a contract, or to take steps requested before entering into one, such as providing the Services, billing, support and developer reporting (section 2(a) to (d) and (i)).
- Providing the service you request: The strictly necessary processing in section 2(e) and (h), without which the Platform, the Website or a Hub you choose to use cannot work or be kept secure.
- Legal obligations: Where processing is necessary to comply with applicable law, such as tax and commercial record-keeping, or a request from a competent authority.
- Legal claims: Where processing is necessary to establish, exercise or defend legal claims.
- Consent: For linking your activity to your enquiry, personal link or Dealbox, Platform usage measurement and session replay, statistics and advertising on Hubs, and marketing to Clients (section 2(f), (j), (k), (l) and (m)). You can withdraw consent at any time. Withdrawal does not affect processing carried out before it.
Where the EU GDPR, the UK GDPR or the Swiss FADP applies to you, the processing in section 2(e), (h), (i) and (n) also rests on our legitimate interests in running a working and secure service. You may object to it under section 7.
5. How we disclose information
We share personal data only with the recipients below. We do not sell personal data.
- Service providers acting on our behalf: The providers listed in the table below process personal data on our behalf under contracts requiring confidentiality and appropriate security. They act only on our instructions, except that Meta and Google also use some of the data they receive for their own purposes, as described in (b).
| Provider | What it does for us | Where |
|---|---|---|
| Vercel Inc. | Hosting of the Platform, the Website and the Hubs, and server logs | United States and global network |
| Neon | Database | United States |
| Google Cloud (Firebase and Cloud Storage) | Project content and media | Qatar (Doha) and Google's global network |
| Clerk, Inc. | Sign-in and account management for the Platform | United States |
| Resend | Transactional email | United States |
| Umami Software, Inc. | Cookieless usage statistics for Hubs and the Platform | United States and Germany |
| PostHog | Error reports and, with consent, product usage and masked session replay on the Platform; usage statistics on Hubs, with consent; cookieless visit counts on the Website | Germany |
| Anthropic | AI service that reads payment-schedule documents a developer uploads, when that feature is used | United States |
| WhatsApp Business Platform (Meta) | Notifications to sales representatives | Meta's global network |
| Google Ireland Limited and Google LLC | Google Analytics and Google Tag Manager, with consent; our copy of statistics data in Google BigQuery; Google Maps | EU and United States |
| Meta Platforms Ireland Limited | Meta Pixel, with consent | EU and United States |
| CloudPano | Virtual tours that are not shown in the Parallex tour viewer | United States |
| Salesforce, Inc. (Marketing Cloud) | For developers that use it: receives the name, email address and phone number from a Hub contact form, as processor for the developer's enquiry handling | EU and United States |
- Advertising platforms: With your marketing consent, Meta Platforms Ireland Limited receives Meta Pixel data (section 9.4). On a developer's instruction, we may also make pseudonymous audience groups available to the developer's or its agency's advertising accounts on Meta and Google. These groups contain no names or contact details. Meta and Google process this data under their own terms and privacy policies.
- Developers, sales representatives and brokers: Enquiries submitted through a Hub go to the developer named on the Hub and, where you arrived through a personal link, to the sales representative or broker who sent it. Where the developer uses Salesforce Marketing Cloud for its enquiry handling, the Hub contact form also delivers your name, email address and phone number there on the developer's behalf. Dealbox Data and Linked Activity are shared as described in section 3. They use this data under their own privacy notices.
- Developers: Statistics on the activity of the sales representatives and brokers who share their Projects.
- Clients: Where Parallex acts as processor, personal data processed on a Client's behalf is accessible to that Client as controller.
- Advertising agencies: Agencies working for a developer receive aggregated reports and, as described above, audience groups in their advertising accounts. They do not receive names or contact details.
- Group companies: Companies in our corporate group, including any holding company of Parallex, for internal administration, reporting and support, under the protections described in this Policy.
- Authorities: Public authorities, law enforcement agencies or regulators, where required by law or in connection with legal claims.
- Business transfers: In the event of a merger, acquisition or sale of assets, personal data may be transferred, subject to applicable law.
6. Data retention
We keep personal data only for as long as necessary for the purposes described in this Policy or to comply with legal obligations:
- Active Accounts: While your Account remains active and you continue to use the Platform.
- After Account termination: Identity, contact, service and transaction records for the period required by applicable tax and commercial record-keeping laws, and as needed to establish or defend legal claims.
- Enquiries, Dealbox Data, Linked Activity and payment schedules: Kept on the instructions of the developer or brokerage that controls them, and in any case deleted within 90 days after the developer's subscription ends. Backup copies are deleted in the ordinary course.
- Server logs: 30 days, held by our hosting provider, Vercel.
- Google Analytics: 14 months within Google Analytics, except age, gender and interest data, which Google keeps for 2 months. We keep our own copy of the event data in Google BigQuery with its random identifiers for 26 months. After that, the identifiers are removed and the anonymised events are kept indefinitely.
- Umami: Up to 2 years.
- Tour statistics: Room visits for 25 months. The daily visitor key cannot be recomputed after 2 days (section 9.3). The daily totals used for reports contain no visitor key.
- PostHog: Usage events for up to 7 years, depending on our PostHog plan, and session replays for 30 days.
- Meta cookies: 3 months.
- Consent records: 3 years, to demonstrate that consent was obtained or withdrawn.
- Consent-based data: Until you withdraw consent or the data is no longer needed for the stated purpose. After withdrawal, we keep only a minimal record of your consent and its withdrawal.
- Aggregated and anonymised data: Indefinitely, because it does not identify you.
- Legal requirements: Longer where required by applicable law, or to address legal proceedings, fraud or security incidents.
7. Your privacy rights
Under the UAE PDPL and, where they apply to you, the EU GDPR, the UK GDPR, the Swiss FADP, the LGPD, the Saudi PDPL or the data protection law of Bosnia and Herzegovina, you may have the right to:
- Access personal data we hold about you and receive information about how it is processed.
- Rectify inaccurate or incomplete data.
- Erase personal data, subject to legal exemptions such as record-keeping obligations.
- Restrict or stop processing in specific circumstances.
- Receive your data in a structured, commonly used, machine-readable format.
- Withdraw consent at any time, including through the "Cookies" control at the bottom of any Hub page.
- Object to processing for direct marketing and to profiling, including the linking of your activity and the interest score described in section 3, and, where the EU GDPR, the UK GDPR or the Swiss FADP applies, to processing based on legitimate interests.
- Object to decisions based solely on automated processing, including profiling, and request human intervention.
To exercise any of these rights, contact privacy@getparallex.com. We may ask you to verify your identity. We aim to respond within one (1) month of receiving complete information. Where we need additional details to identify your records, the one-month period starts when we receive them. We may extend the response period by up to two (2) additional months if your request is complex, and will inform you of any extension and the reasons for it.
Enquiries, Dealbox Data and Linked Activity are controlled by the developer or, for a Dealbox created by a broker, the broker's company. You may contact them directly, or write to us and we will pass your request on and help them respond. For statistics, advertising and cookies, contact us directly.
If you have concerns about how we process your personal data, you may contact us at any time at privacy@getparallex.com. We will acknowledge receipt of your complaint within two (2) business days and aim to provide a full response within one (1) month. If your complaint is complex, we may extend this period by up to two (2) additional months and will inform you of the extension and the reasons for it. You also have the right to lodge a complaint with the UAE Data Office or, if one of the other laws named in this Policy applies to you, with the data protection authority of your country: a supervisory authority in the EU/EEA, the UK Information Commissioner's Office, the Swiss Federal Data Protection and Information Commissioner, the Brazilian National Data Protection Authority (ANPD), the Saudi Data and Artificial Intelligence Authority (SDAIA) or the Personal Data Protection Agency of Bosnia and Herzegovina.
8. Security and incident response
We implement appropriate organisational and technical safeguards, including encryption, access controls, secure storage, staff confidentiality obligations and monitoring, to protect personal data against accidental or unlawful destruction, loss, alteration, disclosure or access. If a personal data breach occurs, we will notify you and the relevant authorities where legally required.
Personal links open without a login, so anyone who has your link can open it. Please do not forward it. If you think someone else has your link, ask the sales representative for a new one.
9. Cookies and similar technologies
The Website, the Hubs and the Platform use cookies and similar technologies, such as browser storage. Strictly necessary items are always on. On Hubs, statistics and marketing tools run only with your consent: on your first visit, the consent dialog lets you accept or refuse them, and nothing other than strictly necessary items and the cookieless statistics in section 9.2 runs before you choose. Google Tag Manager, which loads Google Analytics and the Meta Pixel, is loaded only after you consent. These tools run only on Hubs where audience measurement is switched on. The current list is also shown in the Cookies dialog on each Hub.
9.1 Hubs: strictly necessary (no consent needed)
| Item | Purpose | Kept for |
|---|---|---|
| parallex_consent | Remembers your consent choice | 12 months |
| parallex_consent_pending | Holds your consent receipt until it is delivered to us | Until it is delivered |
| hubViewerId_*, hubParentLeadId_* | Keep your selections while you browse and connect them to an enquiry or personal link you used | Browser session |
| hubLeadId_*, hubShareSlug_*, hubCreator_*, hubOnBehalf_*, hubSalesRep_* | Keep a personal link working and attributed to the sales representative who sent it | 7 days |
| parallex.shareTabSlug | Keeps a personal link working in this tab | Until the tab closes |
| parallex_share_device, parallex_share_sessions, parallex_share_context | Recognise this browser on personal links and record their use, so they keep working and stay attributed to the representative who sent them | 13 months |
| likedApartments_* | Remember the units you save | Browser session |
| hubNeedsSync_* | Keep your saved items in sync | 24 hours |
| hubBrokerToken_* | Keeps the link to the broker who invited you | 30 days |
| px.projectViewMode | Remembers your preferred project view | Until the storage is cleared |
| floor_view_show_labels | Remembers your preferred project view | Until the tab closes |
| px.trackingParams, hub_comparison_params | Carry the link parameters (personal link, sales representative) between Hub pages | Until the tab closes |
| umami_tracked_* | Stops the same usage event being counted twice | Until the tab closes |
| parallex.brokerEmbed, parallex.brokerEmbedChrome (Platform users only) | Remember that the Hub is shown inside the Platform | Until the tab closes |
| parallex_tracking_off (Parallex staff only) | Excludes Parallex staff from statistics | 7 days |
| parallex.trackingOff (Parallex staff only) | Remembers that this tab is a Parallex staff visit and keeps statistics off | Until the tab closes |
| __ph_opt_in_out_* (PostHog) | Remembers your consent choice for PostHog statistics | Until the storage is cleared |
Items kept until the tab closes, until delivered or until the storage is cleared are held in your browser's storage. The others are cookies.
9.2 Cookieless statistics (no consent needed)
We use Umami, a cloud service of Umami Software, Inc., hosted in the United States and Germany, to count visits, pages and interactions, such as the units viewed, on the Hubs and the Platform. Umami does not use cookies and does not track you across websites. It uses your IP address to derive your country and an anonymous visitor identifier, and states that it stores no personally identifiable information. On its own, it produces counts that do not identify you. Where you have submitted an enquiry or opened a personal link or a Dealbox, the events on Hubs also carry the Hub's own random identifiers for that enquiry or link and, on a personal link, for your viewing session and for you as its viewer, so the activity can be shown to the developer and the sales representative (section 3). Umami keeps event data for up to 2 years.
9.3 Hubs: statistics (with your consent)
Google Analytics 4 records which Projects, unit types, floors and features visitors look at and for how long, and Google adds demographic and interest categories where the visitor has a Google profile. We use it to understand which units attract interest and to improve the Hubs. Google assigns a random identifier (_ga and _ga_* cookies, 2 years). Google uses IP addresses to derive approximate location; for users in the EU, Switzerland and the UK, Google states that IP addresses are not logged or stored. The reports we see are aggregated. We also keep our own copy of this event data in Google BigQuery in the United States (section 6).
When a virtual tour opens in the Parallex tour viewer, Parallex records which rooms you visit and in which order, how you moved between them, how long you actively look around in each room, and which parts of each room you look at (in sections of 10°), together with your country, device type (phone, tablet or desktop), the page and the language. No cookies are used: our server derives a visitor key from your IP address, your browser and a random value for that day. The key changes every day, and because the daily value is deleted after 2 days, it cannot be recomputed after that. We do not store your IP address or browser details with the tour statistics. We use them to show the developer which rooms and parts of a unit attract interest. Reports show room-level figures only once at least 10 visitors have seen a tour. Tour statistics are stored with Neon in the United States (section 5).
PostHog records usage events on Hubs, with a cookie (ph_*) kept for 12 months. There is no session replay on Hubs.
9.4 Hubs: marketing (with your consent)
The Meta Pixel records the same interactions (unit viewed, unit added to favourites, enquiry sent) with a Meta identifier (_fbp and _fbc cookies, 3 months). We use it to build audience groups, for example visitors interested in two-bedroom units in a given Project, so that the developer or its agency can show relevant advertising for the developer's Projects on Meta's platforms. On a developer's instruction, we may also make pseudonymous audience groups available to the developer's or its agency's advertising accounts on Meta and Google. This is profiling for advertising purposes. We do not send your name, email address or phone number to Meta or Google: the pixel receives no form data, and Meta's automatic advanced matching is switched off for our pixel.
9.5 Platform
The Platform uses sign-in and session cookies from our sign-in provider, Clerk (__session, __client and __client_uat), kept for your login session; Cloudflare security cookies set through Clerk (__cf_bm, which expires after 30 minutes of inactivity, and _cfuvid), to protect against bots and abuse; and preference cookies that remember settings such as the sidebar, the ranking view and the selected client. The Platform does not use Google Analytics or the Meta Pixel.
We count visits to the Platform without cookies, with Umami, and PostHog records errors. With your consent, PostHog also records, without cookies, the pages and features you use and session replays of signed-in users, in which all text, inputs and images are masked. Parallex staff are excluded.
9.6 Website
The Website sets no cookies. On our pricing page we count visits without cookies, with PostHog.
9.7 What the Hub statistics and marketing tools never collect
- Form content: Anything you type into a form.
- Exact prices and sizes: Only broad bands are recorded, for example AED 2 million to 3 million.
- Professional browsing: The browsing of Parallex staff, and of sales representatives and brokers using a Hub for their work.
9.8 Proof of consent
Each consent choice is recorded with the time, the choice, the version of the cookie list shown, the language, the country and a hashed browser signature. It contains no name or contact details. It carries a random identifier for that choice, also kept in your consent cookie, so that a later change or withdrawal can be matched to the earlier choice. Records are kept for 3 years.
9.9 Your choices
You can change or withdraw your consent on a Hub at any time through the "Cookies" control at the bottom of any Hub page. Withdrawal takes effect immediately and does not affect processing before it. To withdraw consent to usage measurement and session replay on the Platform, contact privacy@getparallex.com. You can also block or delete cookies in your browser settings; the Hub keeps working, but some preferences will not be remembered.
10. Communications from Parallex
Transactional communications (such as service confirmations, invoices and support notifications) are necessary to perform our contract with you and cannot be opted out of. We send promotional communications (such as newsletters or surveys) only with your consent. You may withdraw consent at any time through the unsubscribe link in our communications or by contacting privacy@getparallex.com.
11. Third-party sites and embedded content
The Platform, Website and Hubs may contain links to external websites, including a developer's own website and the platforms of Google and Meta, which have their own privacy practices. We are not responsible for those practices and encourage you to review their policies directly.
Hubs include maps from Google Maps. Virtual tours open in the Parallex tour viewer, which loads the tour images from our own storage (Google Cloud Storage, section 5) and does not connect to CloudPano. Tours not yet shown in the Parallex tour viewer are embedded from CloudPano. Maps and CloudPano tours load with the page. When they load, your browser connects to Google or CloudPano, which receive your IP address and device information. CloudPano sets its own cookies and runs its own statistics inside the tour. Google and CloudPano process this data under their own privacy policies.
12. Cross-border data transfers
Many of our service providers store or process personal data outside the UAE, in the United States, Germany and other EU countries, Qatar and on global networks, as listed in section 5. Our group companies may also be located outside the UAE. Where we transfer personal data outside the UAE, we do so in accordance with the UAE PDPL: to jurisdictions recognised as providing adequate protection or, otherwise, under contractual obligations requiring the recipient to apply protections consistent with the UAE PDPL, or where another ground permitted by the UAE PDPL applies. Where the EU GDPR or UK GDPR applies, transfers are covered by EU standard contractual clauses, the EU-US Data Privacy Framework or other approved safeguards.
13. Children
The Platform, Website and Hubs are not directed at children, and we do not knowingly collect their personal data.
14. Changes to this policy
We update this Policy when our tools, purposes or legal requirements change. The date at the end of this Policy shows the current version. We will notify Clients of material changes in writing, and a change to the cookie list shows the consent dialog again.
15. Contact us
Questions, requests or complaints regarding this Policy can be directed to:
Email: privacy@getparallex.com
Postal: PARALLEX SOFTWARES - FZCO, DSO-IFZA, IFZA Properties, Dubai Silicon Oasis, Dubai, UAE.
Last updated: 29 October 2026