Privacy Policy

How we collect, use, and protect your personal data.

Last updated 5 October 2026Questions: privacyhindaai.ee

Controller and Contact

HindaAI is operated by the following contracting party and personal data controller: J&L Serverid OÜ.

Registry code: 11478495

VAT number: EE101657514

Registered and postal address: Haaviku tee 9, Külitse alevik, Kambja vald, Tartu maakond, 61702, Estonia

Contact: infohindaai.ee · Privacy: privacyhindaai.ee

1. Information We Collect

Personal Information

When you create an account or use our services, we may collect your name, email address, and property addresses you search for.

Public Valuation Snapshots

When you request a public valuation snapshot without creating an account, we collect the searched property address, the verified public-register match, optional email if you enter it, valuation request/result metadata, and a private guest-access token link. The guest token is stored server-side only as a hashed guest token, but anyone with the complete private link can reopen the guest result until the link expires or is claimed into an account.

Guest Report Purchases

If you buy a report as a guest, we use the email address and, if supplied, name from checkout to create an account or associate the purchase with your existing account. We store purchase and report-access records to deliver the report. A new account receives a private emailed sign-in link, valid for 24 hours; this can grant account access, so do not share it. Existing account holders sign in with their own credentials.

Homeowner records

For homes saved to your account, we process the address, property and ownership facts you enter, energy bills and consumption, cost and land-tax inputs, maintenance schedules and completed work, notes, attachments or document references, contractor names and contact details, reminders, and local-change and transport-alert preferences. We use these records to provide your home dashboard, cost estimates, history and reminders. Account-linked records can reveal information about your household and other people, even when the underlying property facts are public.

Buyer and renter workspaces

We process your budget, preferred areas, property requirements, saved searches, shortlisted properties, comparisons and notes to provide the workspace and recommendations you request.

Home portraits and AI search

Where home portraits are available, we process the selected home, building and location information, source imagery, generated illustrations, generation requests and quality checks. Where AI search is available, we process your query, detected language, model response, selected filters, validation errors and timing. The search log is linked to your account. Removing some identifiers from a query does not make free text anonymous.

AI search and home-portrait generation are not active on the public service as checked on 5 October 2026. If enabled in a later release, AI search sends the cleaned query and language context to a model service; portrait generation can send building imagery and generation instructions. We will identify the provider and applicable transfer safeguards before enabling those features. Ordinary property valuations use statistical calculations and public-register data.

Usage Data

We automatically collect information about how you interact with HindaAI, including pages visited, features used, and actions taken within the platform.

Technical Data

We collect technical information such as your IP address, browser type, device type, and operating system to ensure platform security and performance. For public valuation snapshots, client IP data is also used for security processing, rate limiting, abuse prevention, and Cloudflare Turnstile verification where enabled.

3. How We Use Your Data

  • Provide and maintain our property intelligence services
  • Generate statistical valuations and property reports
  • Create and protect private guest valuation links, and let you claim a guest snapshot into an account
  • Improve platform accuracy and user experience
  • Send service-related communications and, with your consent, marketing updates
  • Prevent fraud and ensure platform security, including IP-based rate limiting and bot checks
  • Comply with legal obligations

4. Data Retention

The periods below are the application retention rules checked against the deployed configuration on 5 October 2026. Automated cleanup runs periodically, so expiry and deletion are not simultaneous. These settings do not establish that every cleanup run has succeeded or that independent provider copies have been erased.

Account and saved home/workspace records
Account identity, saved homes, homeowner bills and facts, maintenance and contractor records, buyer/renter preferences, saved reports and portraits remain while you keep them in the service. You can remove supported items or request account erasure. Records needed for a specific legal duty or dispute are handled separately; deleting a guest link is not deletion of the underlying report.
AI search logs
90 days from creation, where the feature is enabled; includes account linkage, cleaned query, response and diagnostic information.
Product funnel events
395 days from creation. This is the retention of our own event records, not a statement of Google or PostHog account retention.
Guest valuation access
Links expire after 30 days. The guest-access email and token hash are redacted 45 days after link expiry. This does not erase the underlying valuation or every copy of an email.
Personal fields in valuation input
Email and client IP fields in raw valuation input are removed after 30 days from request creation. Other property inputs and report data follow the saved-report criteria above.
Home change feed
180 days from creation for home-change event records. Saved maintenance history has a separate purpose and is retained with the home record.
Authentication and account emails
Authentication security events: 365 days from creation. Sent or failed authentication-email delivery records: 90 days from creation. Session and verification tokens expire separately; see the Cookie Policy for browser token lifetimes.
Support messages
Messages marked as read are deleted after 365 days from creation. Unread requests remain for handling; this automatic rule does not set an expiry for an unresolved request.
Invitations and guest claims
Unaccepted organisation invitations: 90 days after expiry. Guest-claim continuation records: 30 days after completion, or after expiry if not completed.
Payment records
Stripe webhook and reversal payloads are redacted after 395 days. Completed, failed, expired or revoked report-purchase attempt records are deleted after 2,555 days since their last update. Accounting evidence and unresolved claims may require separate statutory retention.
Backups and deletion evidence
Backups can contain earlier copies after live records are deleted. A verified maximum backup age and rotation schedule must still be confirmed; we cannot promise a specific backup-erasure deadline at present. Contact our privacy address for the status of an erasure request and any remaining copies.

Erasure rights have exceptions under the GDPR, for example where keeping specific records is necessary to meet a legal obligation or establish, exercise or defend legal claims. Any continued retention of personal data, including in security logs or backups, must have a valid legal basis and last no longer than necessary. A source license or routine backup schedule does not by itself justify refusing a request.

Guest valuation access links currently expire after 30 days.

5. Third-Party Processors

We disclose data only for the relevant service purpose. Providers may act as processors under our instructions or, for some payment/security duties, as separate controllers. Provider names and contractual roles must be read with the applicable service terms.

Hosting and authorised support
Our infrastructure hosts the account, property and service records described above. Authorised staff access them only as needed for service operation, support and rights requests.
ZeptoMail / Zoho
Transactional email delivery: recipient address, message content and delivery information. The configured mail endpoint is api.zeptomail.com; this does not establish EU-only processing.
Cloudflare
CDN, network security and bot protection: requests, IP addresses, device/browser information and challenge results.
Hetzner
Hosting infrastructure. Hosting location alone does not determine where all recipients and their subprocessors can access personal data.
Stripe, where checkout is enabled
Payment, billing and fraud checks: customer contact/billing details, purchase and payment identifiers. Payment-card details are entered with Stripe.
Google Analytics and PostHog, after analytics consent
Browser identifiers, page and feature events, timestamps, device information and event properties. These are pseudonymous personal data, not necessarily anonymous. PostHog is configured for its EU service; provider access and subprocessors must still be considered.
AI providers
No active production AI-search provider or home-portrait worker was identified on 5 October 2026. A future model connection requires an updated recipient disclosure before use.
Public data sources and workspace recipients
Public-register and statistical sources supply property facts. Ordinary lookups do not send your account identity to those sources. Information you share in an organisation workspace is visible according to its access permissions; anyone holding a private guest link can open its result until expiry or claim.

6. International Transfers

EU hosting does not mean that all processing stays in the EEA. Email delivery, network security, payments and analytics may involve provider entities, support access or subprocessors outside the EEA, including in the United States. The applicable destination and mechanism depend on the recipient and service configuration.

Transfers require an applicable adequacy decision or appropriate safeguards, such as the European Commission’s Standard Contractual Clauses and any necessary supplementary measures. An EU–US Data Privacy Framework adequacy decision applies only to a covered, currently certified recipient and transfer. Consent to analytics is not, by itself, a general safeguard for international transfers.

Our provider-specific destinations and contractual transfer mechanisms are still being verified. We do not represent a provider’s public DPA or certification as proof that it applies to our account. To request the relevant safeguards or a copy, contact privacyhindaai.ee.

7. Cookies

We use cookies and similar technologies to operate our platform and improve your experience. For detailed information about the cookies we use, please see our Cookie Policy.

8. Your Rights

Under the GDPR, you may request access, rectification, erasure, portability, restriction, objection, and review of relevant automated processing.

Submit and track a request in the dashboard under Settings → Privacy & Data, or email privacyhindaai.ee. Email is also available if you have no account, cannot sign in, or need to exercise a right not listed in the form. Describe the request and the data concerned. We review requests manually and ask for only the additional information necessary to verify identity if we have reasonable doubts about who is making the request.

We respond without undue delay and normally within one month of receiving your request. Where necessary because of the complexity or number of requests, the GDPR allows up to two additional months. We will notify you of any extension and its reasons within the initial month. Requests are normally free of charge.

Any refusal, restriction or fee must have a valid GDPR justification. Source-license terms, public availability, backup retention or fraud-prevention records are not automatic grounds for refusing your rights. For example, the GDPR permits refusal or a reasonable fee for a demonstrably manifestly unfounded or excessive request. If we do not act on all or part of your request, we will explain the reasons and legal basis within one month and tell you how to complain to a data protection authority or seek a judicial remedy.

Many property facts come from public or open registers, but public availability does not remove GDPR transparency, lawful-basis, objection, and retention obligations when those facts are linked to your search, guest valuation, account, report, PDF, export, admin view, security log, or support request.

9. Privacy Contact

HindaAI has a privacy contact for data-protection questions. This contact is not presented as a formally appointed Data Protection Officer unless we publish that appointment separately. Email privacyhindaai.ee.

10. Complaints

If you believe your data protection rights have been violated, you have the right to lodge a complaint with the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon), or another competent EU/EEA supervisory authority, in particular where you habitually reside, work or where the alleged infringement occurred. You may also seek a judicial remedy. The Estonian authority can be reached at:

Website
aki.ee

11. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will notify you via email and by posting a notice on our website. We encourage you to review this policy periodically.

Earlier notices

Your record preserves the version acknowledged at the time; an update does not rewrite that record or constitute consent to optional analytics. Earlier pages are retained below. A historical version label alone cannot prove exactly which page an individual saw during the previous version mismatch.