Parsla

Parsla Legal

Privacy Policy

Last updated: September 13, 2026

This Privacy Policy explains how Parsla collects, uses, discloses, stores, and protects personal information when you use the Parsla website, application, reports, calculators, parcel analysis tools, and related services (collectively, the “Services”). Parsla is designed to align with applicable Canadian privacy laws, including Alberta’s Personal Information Protection Act (PIPA) and, where applicable, Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA).

1. What This Policy Covers

This Policy applies to personal information Parsla collects in connection with the Services, including through:

  • account creation and login;
  • parcel and address searches;
  • saved projects, scenarios, assumptions, and reports;
  • communications with Parsla; and
  • usage of the Parsla website and application.

2. What Parsla Collects

Depending on how you use Parsla, the following categories of information may be collected:

A. Account and contact information

  • name
  • email address
  • company or organization name
  • phone number, where you provide one for contact or notifications
  • login credentials or authentication identifiers, including the Google account identifier if you sign in with Google

B. Project and property-related information

  • precise property addresses you search, analyze, or save, and the parcel and coordinates they resolve to
  • parcel lookup activity
  • saved sites and project scenarios
  • feasibility assumptions, notes, preferences, and report inputs
  • uploaded or entered project-related information

C. Financial information you enter

Parsla is a feasibility tool, so some of what you enter is financial and personal. Where you choose to provide it, this includes:

  • personal net worth
  • liquid capital available for a project
  • budget ceiling and financing approach
  • purchase price, land value, and project cost assumptions
  • rent, revenue, and other pro forma inputs

D. Technical and usage information

  • IP address
  • browser type
  • device information
  • pages viewed and session activity
  • timestamps and log data
  • cookie or similar technology data

E. Agreement and acceptance records

When you accept a beta agreement or sign a non-disclosure agreement in the application, Parsla records an audit entry so the acceptance can be evidenced later. That entry includes:

  • the legal name you sign under and the email address on your account
  • the organization you sign on behalf of, where you indicate one
  • the version of the agreement and the date and time of acceptance
  • the IP address and browser user agent the acceptance was made from

F. Communications

  • messages sent to Parsla
  • support requests
  • feedback you choose to provide

3. Product Analytics

Parsla uses PostHog to collect product usage information, including pages visited and key product events. For users who are signed in, this information is linked to the email address on the account. Parsla also uses PostHog session replay, which is enabled by default. Before session replay recording begins, Parsla shows a notice with a link to Privacy Settings, where you can turn it off.

A session replay is a playback of activity within Parsla and may include information displayed on screen, such as property addresses, project details, maps, site plans, financial figures, and analysis results. Passwords and other information entered into form fields are masked in session replays. Payment pages hosted by Stripe are not recorded.

For users who are signed in, recordings are linked to the account. Recordings are processed and stored by PostHog Inc. in the United States and are configured to expire after 30 days. Parsla uses these recordings to diagnose problems and improve the product.

You can turn session replay off at any time in Privacy Settings. Turning it off stops future recording but does not delete replay data already collected.

4. Why Parsla Collects Information

Parsla collects, uses, and discloses personal information for purposes such as:

  • creating and managing user accounts;
  • authenticating users and securing the Services;
  • providing parcel analysis, scenario modeling, reports, and related outputs;
  • storing projects, saved assumptions, and user preferences;
  • communicating with users about the Services;
  • monitoring performance, debugging, preventing fraud, and protecting the Services;
  • understanding how users interact with the Services;
  • improving existing features and developing new features, models, workflows, and analytical tools;
  • producing aggregated or de-identified analytics, benchmarking, and product insights; and
  • complying with legal, regulatory, contractual, and security obligations.

5. Consent

By using the Services and providing information to Parsla, you consent to the collection, use, and disclosure of your personal information for the purposes described in this Policy, except where applicable law requires a different form of consent. You may withdraw consent in some cases, subject to legal or contractual restrictions and reasonable notice.

6. How Parsla Uses Project and Usage Data

Parsla uses project data, parcel search activity, assumptions, report inputs, and usage data to operate and improve the Services. Parsla may use aggregated or de-identified data for product development, research, analytics, commercialization, and business operations, provided that the data does not reasonably identify you. Identifiable personal information is not treated as something Parsla can freely sell simply because you used the platform.

7. Cookies and Similar Technologies

Parsla may use cookies, pixels, local storage, and similar technologies to keep users signed in, remember settings, maintain security, and understand app performance. See the Parsla Cookie Notice for more details. You can control cookies through your browser settings, although blocking some cookies may affect functionality.

8. When Parsla Shares Information

Parsla may disclose personal information:

  • to the service providers who help operate the Services, named in the next section;
  • when needed to comply with law, regulation, court order, or lawful request;
  • when needed to investigate, prevent, or address fraud, security, or technical issues;
  • in connection with a merger, financing, acquisition, or similar business transaction; or
  • with your consent or at your direction.

9. Service Providers Parsla Uses

Parsla relies on a small number of established third-party providers to run the Services. Each provider receives only the information needed for its function, and each handles that information under its own privacy policy and terms. The providers currently used, and what each receives, are set out below. Several of them operate outside Canada, which is addressed in the next section.

A. Stripe, for payments

Stripe processes payments for Parsla plans, one-time purchases, and subscriptions. Card and billing details are entered on Stripe's own hosted checkout page rather than on Parsla, and Parsla does not receive or store your full card number. Stripe receives your email address and the details of the purchase, and returns a customer identifier together with payment and subscription status, which Parsla stores to determine what your account is entitled to.

B. Google, for sign in

If you choose to sign in with Google, authentication takes place on Google's own pages. Google provides Parsla with your email address, your Google account identifier, and your name where available, so that Parsla can create or match your account. Parsla never receives your Google password.

C. Google Workspace, for email

Parsla sends account, transactional, and support email through Google Workspace mail servers. That service receives the recipient email address, the sender and subject, and the contents of the message, including any attachment such as a signed agreement copy.

D. Google Maps Platform, for street level imagery

When the application displays a street level image of a property, the location of that property is sent to Google Maps Platform in order to retrieve the image.

E. PostHog, for product analytics

PostHog receives information about pages visited and key product events, along with technical information such as the browser, device, and IP address. For users who are signed in, this activity is linked to the account.

When session replay is enabled, PostHog also receives replay data. This may include information displayed on screen, such as property addresses, project details, maps, site plans, financial figures, and analysis results. Passwords and other information entered into form fields are masked in session replays.

If you turn session replay off in Privacy Settings, Parsla stops collecting and sending new session replay data.

F. Sentry, for error monitoring

Sentry receives technical diagnostics when part of the application fails or performs poorly, including error messages, stack traces, the page or request involved, browser and device details, and network level information such as IP address. Error monitoring runs only in the live production application.

G. Cloudflare, for bot protection

Sign in, registration, password reset, and public request forms are protected against automated abuse by Cloudflare Turnstile. This check runs automatically in the background, without a visible challenge unless something looks unusual. Cloudflare receives your IP address, browser and device information, and the result of the verification, and also uses these signals to improve its bot-detection service. See Cloudflare's Turnstile Privacy Notice at https://www.cloudflare.com/application-services/products/turnstile-privacy/ for details.

H. Twilio, for internal SMS alerts

Twilio delivers short SMS alerts to Parsla's own team when a user requests a property or neighbourhood that is not yet covered. The alert text can include the requesting user's email address together with the address or neighbourhood requested. Twilio is not used to send text messages to users.

I. Hosting and database providers

The Parsla application is hosted on Replit and its data is stored in a Neon PostgreSQL database. These providers store and process the information described in this Policy on Parsla's behalf in order to operate the Services.

J. Changes to this list

This list reflects the providers in use as at the date at the top of this Policy. Providers may be added, replaced, or removed as the Services develop, and this Policy will be updated accordingly.

10. Cross-Border Processing

Parsla or its service providers may process or store personal information outside Alberta or outside Canada. When that happens, information may be subject to the laws of those jurisdictions. Parsla uses reasonable measures to ensure comparable protection through contractual or other appropriate safeguards.

11. Retention

Parsla retains personal information only for as long as reasonably necessary for the purposes for which it was collected, and as needed for legal, operational, dispute-resolution, audit, fraud-prevention, and record-keeping purposes. Account, project, and analysis information is retained while your account is active. Records of agreement or non-disclosure acceptance, and records of payments and purchases, are kept as legal and business records for a reasonable period after an account closes. When personal information is no longer required, Parsla will delete it, anonymize it, or securely destroy it, as appropriate.

12. Safeguards

Parsla uses reasonable administrative, technical, and physical safeguards designed to protect personal information against unauthorized access, collection, use, disclosure, copying, modification, disposal, or destruction. No method of transmission or storage is completely secure.

13. Access, Correction, and Deletion

Subject to applicable law, you may request access to the personal information Parsla holds about you, request correction of inaccuracies, and request deletion of your account and the personal information associated with it. To make a request, email support@parsla.ca. Identity verification may be required before responding. Some information may be retained after a deletion request where retention is required or permitted for legal, accounting, security, audit, or dispute-resolution purposes, as described in the Retention section above.

14. Breach Response

If a privacy or security breach occurs involving personal information, Parsla will take steps appropriate to the circumstances, including containment, investigation, risk assessment, and notice where required by applicable law.

15. Children

The Services are not intended for children under the age of majority in their jurisdiction, and Parsla does not knowingly collect personal information from children for consumer use of the Services.

16. Changes to This Policy

Parsla may update this Privacy Policy from time to time. The revised version will be posted and the “Last updated” date refreshed. If required by law, additional notice or consent will be obtained for material changes.

17. Contact

For questions about this Policy, access requests, correction requests, deletion requests, or privacy complaints, contact Parsla at support@parsla.ca. Parsla’s mailing address is Unit 416, 17008 90 Avenue NW, Edmonton, AB T5T 1L6. Parsla aims to respond within the time required by applicable privacy law. If you are not satisfied with the response, you may contact the Office of the Information and Privacy Commissioner of Alberta or the Office of the Privacy Commissioner of Canada, as applicable. Questions about personal information handled by service providers outside Canada may be directed to Parsla’s Privacy Officer at support@parsla.ca.