Your data

Privacy policy

This policy explains what personal data ASU Property processes, why it is used and what rights you have.

Last updated: 5 November 2026

Controller

Novo Valores S.A. · Teniente Hector Vera 1843, Asunción, Paraguay · RUC 80123986-DV-9

info@asuproperty.com

1. Controller and contact

The controller for ASU Property is Novo Valores S.A., Teniente Hector Vera 1843, Asunción, Paraguay, RUC 80123986-DV-9. Send privacy enquiries to info@asuproperty.com.

2. Data we process

  • Property enquiries: name, email address, optional telephone or WhatsApp number, message, selected project, language and consent timestamp.
  • Newsletter: email address, chosen language, consent timestamp, status and the page where the subscription was made.
  • Personal advice: purchase goal, budget, desired home profile, ranked priorities, location preferences, recommendation results, account identity and membership status.
  • Development submissions: contact and company details, project data, links, photographs, floor plans, brochures, price lists and submitted confirmations.
  • Portal usage: random session identifier, page viewed, referring domain, language, device type and interactions such as project views, phone reveals or WhatsApp clicks.
  • Browser storage: language, display mode, favourites, comparison choices and an unfinished advice session are stored locally on your device.
  • Technical data: servers may process customary connection data such as time, IP address and browser information for security and operations.

3. Purposes and legal bases

We process data to provide and protect the portal, handle and forward enquiries, review submitted developments, improve content and evaluate reach and usage in aggregate. Newsletter data is stored with your consent for market updates in your chosen language.

Depending on the activity, processing is based on your consent, steps taken at your request, legal obligations or our legitimate interest in a secure, clear and functional information portal. Consent may be withdrawn for the future.

4. Sharing and international transfers

With your consent, a property enquiry is forwarded to the developer or provider responsible for that project. That recipient then processes the information under its own responsibility. Depending on the project, a recipient may be in Paraguay or another country.

Paddle acts as Merchant of Record and receives the information needed for purchase, subscription management, payment, tax compliance and invoicing. Technical providers receive data only as needed for hosting, storage, security, email delivery or portal operations. We do not sell personal data.

5. Google Maps

Map views use Google Maps. When a map loads, Google may process technical information, particularly your IP address and device or browser data, and may transfer it to other countries. Google's privacy terms also apply. The remaining project information can be used without interacting with a map.

6. Retention

We retain personal data only as long as necessary for its purpose, handling an enquiry, documenting consent or complying with legal retention duties. Rejected or discontinued project submissions and related files are deleted or anonymised once no longer needed for review, legal evidence or abuse prevention. Local settings can be deleted through your browser.

7. Security

We use reasonable technical and organisational safeguards. Submission files and internal contact details are not publicly accessible, and access is limited to authorised persons. No online service can guarantee absolute security.

8. Your rights

Subject to applicable Paraguayan law, you may request access, correction, updating or deletion of your data, object to processing, and withdraw consent. To the extent Law No. 7593/2025 becomes applicable, we will also honour its additional rights, including portability.

Email info@asuproperty.com to exercise a right. We may request reasonable proof of identity to prevent unauthorised disclosure.

9. Minors and changes

The portal is not directed at minors. Please do not submit a minor's data without the required authorisation.

We update this policy when functions, recipients or the legal framework change. The current version and its revision date are available on this page.

10. Legal framework

This policy considers Law No. 1682/2001, as amended, and is proactively aligned with the principles of Law No. 7593/2025 on personal data protection. Transitional provisions and future implementing rules remain reserved.

11. ASU Scout – Mobile Application

ASU Scout is the mobile application for reporting residential developments and construction progress to ASU Property. Novo Valores S.A. is also its controller. The following information supplements the policy above and distinguishes account and review data from optional information and potentially public project content.

11.1 Phone number, SMS and account

Phone-based sign-in processes your mobile phone number, account and Scout identifiers, and the timestamp of acceptance of the participation terms. Verification codes are sent by SMS through seven.io, which receives the phone number for delivery. Code requests also record the IP address, request time, expiry, attempts and use of the code. The code is stored as a hash.

Session management processes a hashed access-token identifier, a device description if supplied by the app, last-use time and revocation time. Signing out revokes the current session but does not delete the account or associated data.

11.2 Location and location verification

Depending on the task, we process submitted GPS coordinates, location accuracy in metres, distance to the construction site and, where provided, a placed site pin. These support project and task matching and review of your report. Construction-photo submissions require location information. Distance above 150 metres does not by itself cause rejection; it is shown as information during review.

The inspected interface processes location information sent with requests or submissions; it does not implement continuous background tracking. The mobile app’s actual permission prompts and any local storage still require confirmation.

11.3 Camera, photographs and image metadata

You submit construction photographs through the camera or image picker and, for price tasks, screenshots as evidence. The service receives these files when uploaded; the mobile app’s device-level camera and photo permissions require separate confirmation.

Image files, storage paths and file hashes for duplicate detection are stored. The inspected upload processing does not explicitly remove image metadata, so files may contain capture time, device information or embedded location data if sent by the app. Please avoid unnecessary faces, vehicle plates, private messages or other personal information about third parties. Metadata removal and the actual storage access configuration still require confirmation.

For automated construction-progress estimation, up to four photographs and the previous progress record may be sent through Lovable AI Gateway to an OpenAI model. The estimate is saved for review; approval is carried out by the ASU Property team.

11.4 Reports, optional information and review

We process task type, associated project, submitted project or developer names, residential use, floors or units, construction stage and active work, as well as the relevant corrections, source links and price evidence. Free-text notes and additional information not required for the selected task are optional. Required information depends on the task.

Submissions are linked to your Scout identifier. Submission time, status, review outcome, rejection reason where applicable, reviewer, review time and automated assessment are also recorded. These data support verification, traceability, abuse prevention and reward allocation.

11.5 Optional voice notes

Voice recordings are optional. Submitted audio files are processed in memory and sent through Lovable AI Gateway for transcription using the requested OpenAI model openai/gpt-transcribe. Successful transcripts are appended to the submission note and then stored as its text. The inspected submission interface does not persist the audio files themselves in the application database or file storage.

If transcription fails, the submission is retained and the error is logged. The transcription service’s retention, further processing and subprocessors, and any local audio storage in the app, still require confirmation. No unverified provider deletion period is promised.

11.6 Rewards, balances and payouts

Participation involves processing reward amounts, approved or rejected tasks, balances, ledger entries, timestamps and payout requests, including status and references. These data support accounting and linking a reward to the reviewed activity.

Payout details are only required if you request a payout. Bank transfers may involve bank name, account number, account holder and identity information such as a Cédula number (CI). USDC Polygon payouts involve wallet address, amount, status and, where applicable, transaction hash. Bank transfers are manual; USDC transfers follow an explicit administrator action. The bank or blockchain network receives the payment information necessary for execution.

Polygon transactions, including wallet addresses, amount and transaction data, can be traced on a public blockchain. Deleting your ASU Scout account cannot remove those blockchain entries. A separate identity-verification service is not evidenced in the inspected implementation.

11.7 ASU Property, recipients and public content

Data is sent from ASU Scout to ASU Property and reviewed by authorised team members. Verified construction photographs, progress information and related notes may appear on public project pages; new project reports may enter the public catalogue after further review. Please do not include confidential information in notes or images suitable for publication.

Phone numbers, access tokens, bank and identity information, internal reward accounts and review records are not intended as public project content. A screenshot or note may itself contain personal information. Actual public or private access to uploaded original files still requires confirmation; a blanket confidentiality promise for all Scout files is therefore not possible.

Verified services are Lovable Cloud for accounts, data and file storage; seven.io for SMS; Lovable AI Gateway with requested OpenAI models for transcription and photograph analysis; and, for USDC Polygon, the Polygon network and the RPC service used to communicate with it. Google Maps, where used, is described above. Exact provider configurations, additional subprocessors, processing locations, provider retention and international-transfer arrangements still require confirmation; additional services in the external mobile app have not been verified.

11.8 Retention, rights and account deletion

The rights above also apply to Scout data. You can request access, correction or deletion of your Scout data and account at info@asuproperty.com. Reasonable proof of identity may be needed to match your request. Automatic, complete deletion of phone-based Scout accounts within the mobile app has not yet been evidenced in the inspected implementation; signing out or removing the app is not account deletion.

A complete, automatically implemented deletion schedule has not been evidenced for Scout profiles, GPS data, submissions, original images, transcripts, review logs, SMS requests, sessions and accounting records. Purpose-specific periods and legally required retention of payout or evidence records must be confirmed case by case. We therefore do not state fixed or already automatically enforced periods. A code’s expiry or a session’s revocation does not mean its record is deleted.

A deletion request needs to address account and submission data, including any published content; legal retention duties and immutable public blockchain data may prevent complete erasure. The scope and remaining duties must be assessed case by case. Outstanding information on app permissions, providers, access, retention and deletion procedures must be confirmed before a final App Store privacy sign-off.