Privacy Policy

This Privacy Policy explains how Modula AI (Modula, we, us, or our) handles personal data when people visit our website, create or use an account, contact us, purchase a plan, use our property-media and location tools, or open and interact with a buyer presentation.

For account, billing, website, security, and support information, Modula generally decides why and how the data is handled. When a property agent or agency gives us personal data about a buyer, seller, owner, or other person so that we can provide the Service on its instructions, that customer may be the organisation primarily responsible for the data and Modula may act as its data intermediary. In that situation, you can contact the agent or agency for the context in which they collected your data, and you may also contact us for help routing a request.

This Policy does not govern an agent's own website or communications, or third-party services that publish a separate privacy policy. Our Terms of Use separately govern use of Modula.

Account and professional profile

Name, email address, authentication identifiers, account status, agency name, role, profile and contact details, brand settings, preferences, and communications choices.

Property projects and media

Property names and addresses; listing photographs; floor plans; material references; prompts; style choices; property briefs; annotations; agency templates; generated images and videos; and technical metadata needed to connect, order, secure, and delete those files. Property media can incidentally reveal people, possessions, unit layouts, or location details, so account holders should remove unnecessary personal or sensitive content before upload.

Buyer presentations and responses

Presentation title and message, selected media, optional property address, optional agent contact information, recipient or buyer label, expiry and revocation settings, and brand snapshots. If a buyer voluntarily responds, we collect their selected reaction, comment, preferred presentation item, and optional name and email address.

Presentation interactions

Page views, before-and-after comparison interactions, image views, video plays and completions, contact clicks, the relevant item position, limited event metadata, and event time. We use a random browser-session identifier stored in session storage and transform it into a keyed hash before storage. We also transform network information such as an IP address into a keyed network hash for security, deduplication, rate limiting, and aggregate engagement reporting. These hashes reduce direct identifiability but may still be treated as personal data.

Location scenarios

The buyer anchor address, selected property addresses already stored in the agent's property records, travel mode, time bands, routing preference, and operational information about each report run. Section 3 explains the server-side Google Maps processing in detail.

Billing, support, and technical data

Subscription and plan status, customer and transaction identifiers, billing period, usage allowances, payment outcome, contact-form entries, support correspondence, and service logs. Card and other payment details entered at checkout are handled by our payment provider; Modula ordinarily receives identifiers and transaction status rather than full card details. Technical data can include IP address, user agent, request time, route, error and security logs, device or browser information, and referring URL.

The travel-time shortlist is an agent-only feature that is available only where explicitly enabled. When an authenticated agent runs it, the browser sends the scenario to Modula. From our server, Modula sends the buyer anchor and each selected property address to the Google Maps Geocoding API v4. We then send the resolved anchor coordinates, travel mode, time band, direction, and routing preference to the Google Maps Isochrones API. Google processes these inputs to return address matches and road-network polygons.

Modula uses the returned geometry in server memory to classify selected property points. Raw isochrone polygons are not persisted by Modula and are not sent to the browser. The authenticated response can include formatted address matches, classification groups, settings, caveats, source, and fetch time and is served with private, no-store cache controls. Our run ledger retains operational details such as user, status, operation counts, and timestamps for quota, security, and cost governance; it does not retain the report address, coordinates, place data, or polygon. Property addresses remain part of the underlying property record until the account holder changes or deletes them.

Google receives the request data and related service information needed to operate its APIs and handles it under its applicable terms and privacy materials. Google's own logging and retention practices are outside Modula's direct control. Review theGoogle Privacy Policy, theGoogle Maps Platform Terms, and theGoogle Maps security and compliance overview.

As at this Policy's effective date, Google labels Isochrones as a pre-General Availability Preview offering. Results and availability may change. A band is not an exact journey time, and Modula does not use a location report as a substitute for an entrance check or point-to-point route. See our Terms of Usefor the full reliance boundary.

We receive personal data:

• directly from you, when you register, configure a profile, upload content, create a property, run a report, purchase a plan, submit buyer feedback, or contact us;
• from an agent or agency, when it creates a property project, includes information in a buyer presentation, or invites you to review one;
• automatically from your browser and our systems, through authentication cookies, local or session storage, requests, service logs, security tools, and buyer-presentation events; and
• from service providers, such as authentication, cloud, payment, AI-generation, email, and maps providers, when they return an account, transaction, generation, delivery, or location result.

We collect, use, and disclose personal data where reasonably needed to:

• create and secure accounts, authenticate users, and provide the features requested by an agent, agency, or buyer;
• store, organise, transform, generate, stream, share, and delete property media and buyer presentations;
• process subscriptions, allocate usage, reconcile generations, prevent duplicate charges, and support billing enquiries;
• record buyer feedback and produce engagement summaries for the agent who created the presentation;
• geocode addresses and produce an agent-only travel-time shortlist when the account holder asks us to run one;
• answer questions, troubleshoot, communicate service notices, and provide support;
• monitor reliability, diagnose errors, enforce limits, protect accounts, detect fraud or misuse, and maintain audit records;
• understand and improve the Service using appropriate aggregated, de-identified, or limited usage information; and
• comply with law, respond to lawful requests, establish or defend legal claims, and enforce our agreements.

Depending on the context and applicable law, we rely on consent (including deemed consent where permitted), performance of our agreement or your request, reasonable business and security purposes, and other grounds or exceptions allowed by law. We do not sell personal data or use buyer presentation interactions for third-party advertising.

We may disclose personal data to:

• the relevant account holder, agency, or presentation recipient, such as when an agent publishes a buyer link or reviews a buyer's feedback and engagement summary;
• cloud, database, authentication, storage, and hosting providersthat keep the Service and private media available;
• AI and media-generation providers, including Google services where configured, which receive the property media, prompt, and generation settings needed to create or assess the requested output;
• Google Maps Platform, for the address and isochrone processing described in Section 3;
• payment and communication providers, including Stripe for checkout and subscription processing and email infrastructure for service and support messages;
• professional advisers, auditors, insurers, authorities, or other parties where reasonably necessary to meet legal obligations, protect rights and safety, investigate misuse, or resolve a dispute; and
• a successor or transaction participant in a merger, financing, reorganisation, or transfer of all or part of the Service, subject to confidentiality and applicable law.

We require service providers to handle data only for the services they provide to us and with appropriate protections, subject to their own applicable terms. We do not make an agent's private property project or buyer feedback public unless the account holder shares it through a buyer presentation or another publishing feature.

Modula uses cookies and similar browser storage that are needed to run the Service. These can include authentication cookies, security and session state, theme or interface preferences, the selected property and workflow state, temporary signed-media references, and a random buyer-review session identifier. They help keep you signed in, preserve a workflow between pages, display the correct content, prevent abuse, and associate buyer events within one browser session.

You can remove cookies and site storage through your browser controls, but doing so can sign you out, clear an in-progress design workflow, reset preferences, or create a new buyer-review session. Modula does not currently use buyer-presentation session storage for cross-site advertising.

Modula is built for Singapore property-marketing workflows, but our cloud, payment, email, AI, and maps providers may process or store data in other countries. Those countries may have different data-protection rules.

Where Singapore's Personal Data Protection Act 2012 (the PDPA) applies to an overseas transfer, we take steps required by the PDPA to ensure that the transferred personal data receives a standard of protection comparable to that under the PDPA. Depending on the service and transfer, those steps can include contractual protections, provider security and privacy commitments, access controls, and limiting the data sent to what is needed for the requested function.

We keep personal data only while it is reasonably needed for the purposes described in this Policy, including to provide the Service, maintain security and continuity, complete deletion work, resolve disputes, and meet accounting, tax, contractual, and legal obligations. Retention varies with the type of record and why it is held.

• Account and subscription records are generally kept while the account is active and for a reasonable period afterwards where needed for support, fraud prevention, disputes, and legal records.
• Property content, media, outputs, and buyer presentations are generally kept until the account holder deletes them, closes the relevant account, or they are no longer needed to provide the Service. Deletion can take additional time in backups and queued storage-cleanup systems.
• Buyer events and feedback are kept with the related presentation or account for agent follow-up, reporting, security, and dispute purposes, then deleted or de-identified when no longer reasonably needed.
• Contact messages, security logs, billing records, and audit information are kept for periods appropriate to the enquiry, risk, and applicable legal or business requirement.
• Raw Google isochrone geometry is processed in memory and is not persisted by Modula. Google's independent retention is governed by its policies.

We may retain a minimal record after a request where needed to document the request, honour an opt-out, prevent fraud, comply with law, or establish, exercise, or defend legal claims.

We use reasonable technical and organisational safeguards appropriate to the nature of the Service. These include authenticated account boundaries, private storage and time-limited media access, server-only supplier keys, restricted administrative access, same-origin and input checks, buyer-link expiry and revocation controls, hashed buyer session and network identifiers, private/no-store buyer responses, usage limits, and monitoring and cleanup workflows.

No internet or storage system is completely secure. Protect your account, use a unique sign-in method, limit who receives buyer links, keep your own source-media copies, and contact us promptly if you believe an account, link, or file has been exposed. Do not email us passwords, full payment card details, identity documents, or unnecessary sensitive data.

Subject to the PDPA and its exceptions, you may ask for access to personal data about you in our possession or control and information about how it was used or disclosed during the relevant period. You may also ask us to correct an error or omission. You can update some account and presentation information directly in Modula or ask the relevant agent to do so.

You may withdraw consent to a collection, use, or disclosure by giving reasonable notice. We will explain any likely consequence; for example, withdrawing processing needed for an account, generation, buyer response, or map report can mean that we cannot continue that feature. A withdrawal does not affect processing already lawfully completed and does not require us to delete a record that we must or are permitted to keep.

You may also ask us to delete data, close an account, revoke a buyer link, or stop optional marketing messages. Some requests may be subject to legal, security, contractual, or technical limitations. To protect people's data, we may verify identity, authority, account ownership, or the presentation concerned before acting. If an agent or agency controls the relevant data, we may send the request to that organisation or ask you to contact it directly.

Modula is a business property-marketing service and is not directed to children under 18. Account holders must not intentionally upload children's personal data unless they have a lawful, necessary reason and appropriate authority. If you believe a child has provided personal data to Modula without appropriate permission, contact us so that we can review it.

We may update this Policy when the Service, suppliers, practices, or legal requirements change. We will publish the new version with an updated effective date. If a change is material, we will provide additional notice through the Service or account email where appropriate.

For an access, correction, withdrawal, deletion, complaint, or other privacy request, contact the Modula privacy contact at support@usemodula.com or use our privacy contact route. Tell us your relationship to Modula, the relevant account or buyer presentation, what you are requesting, and how we can reach you. Please do not include more personal data than is needed for us to understand the request.

We aim to address privacy concerns directly. Information about the PDPA and individual rights is also available from Singapore'sPersonal Data Protection Commission.