Paisagia privacy policy

01Introduction

Paisagia is committed to protecting your privacy and the secure handling of your personal data. This Privacy Policy describes how we collect, use, share, store and protect your personal information when you use our AI-powered landscape design services. The controller of your personal data is Bliz Soluções Digitais LTDA, registered in Brazil under CNPJ no. 22.117.215/0001-20, with its registered office at Ed. Impacto Empresarial, Av. Nossa Sra. da Penha, 2796, 8º andar, Santa Luíza, Vitória – ES, Brazil ("Paisagia").

This policy complies with the General Data Protection Law (LGPD - Law No. 13,709/2018) and other applicable data protection legislation.

02Data Collected

We collect different types of information to provide and improve our services:

2.1 Registration and Profile Data

• First and last name
• Email address
• WhatsApp number (on the Portuguese site) or phone number (in the other languages): required to complete the free trial's sign-up and optional otherwise; you can change or delete it in the settings
• Password, stored only as an irreversible hash (Argon2id)
• Profile photo (optional), uploaded by you or brought from your Google account
• If you sign in with Google: your Google account identifier, e-mail, name and photo address, which Google sends us with your authorization (the "openid", "profile" and "email" permissions). We do not receive your Google password or access to any other data in the account

2.2 Content and Usage Data

• Photos you upload and the images generated from them. Photos are stored without the camera's metadata, such as location and device model
• Answers and texts you write in the tools, such as your Freestyle Mode choices and your With Prompt description
• Projects, scenes and compositions you create and save, and your editor preferences (favorites, colors)
• Plan usage: AI generations made, version history and, if you use the courses, your lesson progress and reactions
• Requests for catalog items and messages you send us
• Conversations with the virtual assistant: the messages you exchange with it in the app — in the support conversation and in each scene's conversation, in the editor —, with date and time, and what is kept with them: the ratings you give its answers and how far you have read; the images you attach, reduced and without their metadata (such as the location), and a description of each one, written by the assistant and not shown to you; the tickets you open for our team and its replies, with the first name of whoever replied — or, when it writes on the assistant's behalf, without it, with who wrote it recorded for the team; and, in the editor, the assistant's proposals and notices, with your choices about them, and its notes on what it saw in the scene, which you do not see

2.3 Technical and Security Data

• IP address, date and time of each access, and the records of sign-ins, sessions and actions taken on the account (audit records)
• Browser and device type, and operating system
• Approximate location of access, inferred from the IP address by Cloudflare (country, state, city, postal code and city-level coordinates), the browser's language and the time zone it reports, which is kept on your account to date our e-mails. We do not ask for or use your device's precise (GPS) location
• Opening of the e-mails we send: a tracking pixel records how many times each e-mail was opened and, on the first opening, the IP address, browser and country
• Which pages of the site you keep open and visible, with the date and time, the IP address, the browser and the approximate location Cloudflare reports (country, state and city) — and, if you are signed in, your account — so we know how many people are using the platform at any moment and where they access it from. Of these records we keep aggregate counts (screens, devices and accounts per minute, per day, per place and per page), with no IP, browser or account; to count the devices of each day and each page, we keep for at most 2 days a code of the IP with the browser, from which neither can be recovered, and, if you are signed in, a code of your account. No cookies are used: the browser keeps, only in that tab's session storage, a random code of the tab, so the next page in the same tab is recognised as the same screen
• If you use Paisagia installed as an app: on what kind of device (computer, Android or iPhone/iPad), when the app first showed up and the date you last opened it, so we know how many people use the installed app

2.4 Billing Data

• Billing profile: tax ID (CPF or CNPJ in Brazil, or a foreign tax ID when there is one), name or company name, and address (in Brazil, at least the postal code). When you change these details, the previous ones remain in the account history
• Payment data received from Stripe: card brand, last 4 digits and expiry date, invoices and payment status, and the cancellation reason you give in Stripe's portal. The full card number is typed on Stripe's page and never reaches us
• Details you type on Stripe's payment page, such as phone number, address and tax ID, which we receive back to pre-fill your profile

2.5 Origin and Acceptance

• The partner seller's code, coupon or trial invitation through which you arrived (see section 10)
• If your first visit came from a campaign or ad link: the link's campaign parameters (UTM) and the ad click identifiers (fbclid, gclid), stored on your account when it is created (see section 10)
• The record of your acceptance of the Terms and of this Policy (date, IP address and version accepted) and your choice about promotional e-mails

2.6 The Full Video Form

• The name, e-mail and WhatsApp number (on the Portuguese site) or mobile number (in the other languages) you give to watch Paisagia's full video, even without an account
• The IP address, the date and time of the submission, the page's language and, if your first visit came from a campaign or ad link, its parameters (UTM, fbclid, gclid)

2.7 The Contact Form

• The name, e-mail, WhatsApp number (on the Portuguese site) or mobile number (in the other languages) and message you send through the website's contact form, even without an account
• The IP address, the date and time of the submission, the page the message was sent from and its language

03How We Collect Your Data

We collect your personal data through the following methods:

• Directly: When you sign up, fill out forms — such as the full video's and the contact form — or upload images
• Automatically: Through your use of the platform: the server's technical logs, cookies and similar technologies (see section 10)
• By interaction: When you use the tools, the editor and the virtual assistant, including the images the artificial-intelligence providers produce for you and the assistant's answers
• By communication: When you contact us
• From third parties: From Stripe (payment data), from Google (if you sign in with your Google account), from Cloudflare (approximate location of access, and an indication that a password used appears in public data leaks), and from our team or a partner seller when they record a referral or a sale made outside the website

04How We Use Your Data

We use your personal data for the following purposes:

4.1 Service Delivery

• Send your photos, compositions and texts to the artificial-intelligence providers to generate the images you ask for
• Keep track of your plan's generation allowance, your trial and your access to the courses
• Provide access to 4 creation modes (Freestyle, Prompt, Clear Space, Garden Editor)
• Save and manage your created projects
• Bill your subscription, send receipts, handle the guarantee, refunds and payment disputes, and pay partner sellers' commissions
• Answer your messages in the conversation with Paisagia's virtual assistant — an artificial intelligence, not a person —, which uses, to help you, the conversation and the data of your account it needs (section 6); in the editor, also the scene and the catalog, to talk about the garden and propose edits of the scene's photo; and, when you save a scene in the editor, to check — sending nothing to OpenAI — whether it puts full-sun plants beside plants that do not take full sun, to let you know

4.2 Service Improvement

• Analyze usage patterns to optimize our platform
• Have our team review generations and failures to fix problems and improve the instructions used in compositions; your photos are not used to train artificial-intelligence models
• Develop new features and functionalities
• Have our team read the conversations with the virtual assistant — the support conversation and the scenes' conversations — and the ratings of its answers, to help you and improve the assistant's answers. The conversations are not used to train artificial-intelligence models

4.3 Communication

• Send notifications about your projects
• Communicate service updates
• Respond to your questions and requests
• Send emails with news and promotions — you can stop receiving them at any time through the unsubscribe link in the email itself
• Know whether e-mails were opened (tracking pixel), to monitor message delivery
• Show the full video to whoever fills in its form, and talk to that person about Paisagia by e-mail, WhatsApp or phone

4.4 Security and Fraud Prevention

• Protect accounts and the platform: bot verification, attempt limits, blocking of abusive IP addresses, audit records, detection of stolen-card testing and, on your account's security page, the approximate location of each access and an indication that your password appears in public data leaks (Cloudflare runs that check without storing the password)
• Comply with legal obligations and defend our rights, including in payment disputes

4.5 Partner Seller Referrals

• Credit your subscription to the partner seller who referred you and calculate their commission

4.6 Measuring Visits and Ads

• Measure the visits to the public pages, the sign-up, the plan choice and the profile filled in when the free trial starts or after payment, the clicks on the WhatsApp button, on the plans' buttons and on the play button of the home page's video and of the full video, the submission of the full video's form, and the results of our ads, with the Google tag (Google Analytics and Google Ads) and the Meta Pixel
• Tell Meta, from our server (Conversions API), about your sign-up, the activation of a free trial, the start of a payment and each new subscription — never the renewals —, to measure and optimise our campaigns on Facebook and Instagram
• Show Paisagia ads to people who visited those pages (remarketing), on Google — in Search, on YouTube and on its partner sites and apps — and on Facebook and Instagram: Google and Meta build these audiences from their cookies' identifiers (section 10) and from the visits and events described in section 6

05Legal Basis for Processing

The processing of your personal data is based on the following legal bases of LGPD:

• Contract execution: To create and maintain your account, provide the contracted services (including sending photos and texts to the AI providers when you trigger a generation and, when you talk to the virtual assistant, your messages and the account data it needs to OpenAI), bill your subscription and send e-mails about your account and billing; and, at your request, to show the full video to whoever fills in its form, answer the messages sent through the contact form and answer about signing up (preliminary procedures related to a contract, article 7, V, of the LGPD)
• Consent: To share your data in situations this Policy does not describe, only with your express authorization; you may withdraw your consent at any time (section 9)
• Legitimate interest: For service improvement, platform security and fraud prevention, crediting referrals to partner sellers, measuring visits and the results of our ads and showing ads to people who visited the site (section 4.6), our team reading the conversations with the virtual assistant and keeping support conversations after they end (section 8), sending news and promotions to everyone with an account on the platform, customer or not, who can unsubscribe at any time, and following up, by e-mail, WhatsApp or phone, with whoever left their details to watch the full video. You may object to these processing activities (section 10.2), and to the follow-up at any time, by replying to it or through the e-mail in section 9
• Legal obligation compliance: To keep access records for the period required by Brazil's Internet Civil Framework (Marco Civil da Internet) and billing documents for the period required by tax law
• Regular exercise of rights: To keep records that may be needed in legal proceedings or payment disputes

06Data Sharing

We do not sell, rent or trade your personal data. We share information only in the following situations:

• Hosting and network: Our servers are at Oracle Cloud, in São Paulo (Brazil). All website traffic goes through Cloudflare, which protects and delivers the pages: it sees the IP address and the content of requests, runs the bot verification (Turnstile) on the sign-in and sign-up screens, on the full video's form and on the contact form (loaded only once you start filling it in), and caches the images of your projects
• Payments: Stripe processes payments. It receives your name, e-mail and language, and collects your card details on its own payment page. We do not send it your CPF, CNPJ, address or phone number
• E-mail: The e-mails we send are delivered by Google Workspace, which receives the recipient's address and the content of each message
• Artificial-intelligence providers: When you use an artificial-intelligence feature ("Apply Realism" in the editor, Clear Space, Freestyle Mode or With Prompt), the working image (the photo you uploaded or, in the editor, the composition with the elements you placed, which may show people, façades or licence plates), the tool's instructions and the text you wrote are transmitted to image-generation providers, currently OpenAI (USA) and Google Gemini, solely to produce the image you requested. Editing a scene's photo as the virtual assistant proposes (removing an object or clearing the sky, for example) takes the same path: when you confirm the proposal, the scene's photo and the editing instruction it shows are transmitted to those providers. It is sent only when you trigger a generation and does not include your name, e-mail or any other identifier; those providers process the content under the terms of their paid APIs, which do not allow your images to be used to train their models. If our team sets up an API key of your own for your account, that provider's generations run through your own account with it, under the terms you agreed with them
• Virtual assistant: When you write to the virtual assistant, your message, the earlier messages of the same conversation, the assistant's instructions and the data of your account it needs to answer are sent to OpenAI (USA), solely to produce the answer. That is the data of your account related to the subject, such as your registration and profile, your plan, billing and invoices, your use of the platform, your projects, your settings, your account's security and the sign-ins to it, the e-mails we send you, and your tickets to our team with the replies they received. In the editor, it also uses the scene — its items as they are in the editor, even before you save them, and, when you ask for a change to the photo or ask something that can only be answered by seeing the scene, the photo as it was saved and the composition — as it was saved or, when it needs to see what you are editing, as it is on your screen at that moment, without keeping that image — and Paisagia's catalog. When you ask about one of the scene's AI-generated versions, it also uses that version and the composition or the photo the version was generated from. Of what it sees in these images, the assistant writes notes, which it keeps with the scene's conversation and uses in later answers instead of sending the images again, while they stay unchanged. If you attach images to a message, they are sent to OpenAI with it, reduced and without metadata, and the assistant writes a description of each one, which is sent in the image's place in later messages. If you dictate a message through the microphone, the recording is sent to OpenAI only to be transcribed and is not kept: the transcribed text appears in the message box, where you review it before sending, and only what you send stays in the conversation. To help our team answer a ticket of yours, the assistant may also write suggested replies, which the team reviews before sending; for that, the conversation, the ticket and your account's data are sent to OpenAI, always through Paisagia's own account there. OpenAI processes this content under the terms of its paid API, which do not allow it to be used to train its models; under the API's default setting, which we keep, OpenAI stores requests and answers for 30 days and abuse-monitoring logs for up to 30 days, unless the law requires longer. If our team registers an OpenAI API key of your own for your account, the conversation — and what you dictate — also goes through your own account there, under the terms you agreed to, and is stored there according to that account's settings. Do not write in the conversation — nor show in the images you attach, nor dictate — passwords, card numbers or other data the assistant does not need: what you write, dictate and attach is sent to OpenAI, and what you send is stored with the conversation (section 8)
• Sign in with Google: If you choose to sign in with Google, authentication is done by Google, which sends us the data described in section 2.1
• Services your browser calls: When you fill in a Brazilian postal code (CEP), your browser queries ViaCEP to complete the address. In the editor, your browser checks its connection against Google addresses, without cookies, to know whether you are online. In every language, the home page's presentation video is loaded from Vimeo (USA), and the full video from YouTube, Google's (USA), only when you click to watch them; from then on, each records playback statistics (how many times and how far the video was watched), which we use to evaluate the videos, and sets cookies of its own (see §10). These services receive your browser's IP address
• WhatsApp support: If you message us on WhatsApp (the button on the Portuguese site), or we message you there at the number you left in one of the site's forms, the conversation — your number, your profile name and the messages — goes through WhatsApp, from Meta (USA), under its own terms
• Measurement and ads (Google and Meta): On the public pages, the sign-up, the plan choice and the profile filled in when the free trial starts or after payment, your browser loads the Google tag (Google Analytics and Google Ads) and the Meta Pixel, from Meta (Facebook and Instagram), which receive the page address, the IP address, the browser's details and their cookies' identifiers (section 10); the Meta Pixel may also link to the visit, encoded (hashed), the details typed into those pages' forms that it recognises — e-mail, phone, first and last name, city, state, postal code and country. On those pages your browser also tells Google and Meta about your sign-up and the purchase of a subscription, with the amount, the currency and an identifier of the subscription, and tells Meta alone when you activate a free trial. It also tells Google and Meta about a click on the WhatsApp button; on the home page and the full video's page, a click on a plan's button, with the plan and the billing period chosen and whether the button led to a free trial; on the home page, the play of the presentation video; and, on the full video's page, the submission of the form (the event itself carries none of the details typed into it; the Meta Pixel may link, hashed, those it recognises, as said above) and the play of the video. When you sign up, activate a free trial, start a payment or subscribe to a new plan, our server tells Meta about the event, with your e-mail, phone, name, city, state, postal code, country and account identifier encoded (SHA-256 hash), the IP address, the browser's details, the ad click identifiers and, for the payment and the subscription, the plan, the amount and the currency. Google and Meta also use these visits and events to build the audiences we show Paisagia ads to (section 4.6). We do not send your CPF or CNPJ, nor the content of your projects
• Partner sellers (affiliates): If you reached Paisagia through a partner seller's link, coupon code or campaign, or the seller referred you to our team, we e-mail that seller your first name, the plan you subscribed to and the corresponding commission amount, so they are paid for the referral. No other data of yours — surname, e-mail, projects or payment details — is shared with them
• Legal requests: When required by court order or competent authorities
• Rights protection: To protect our rights, property or security
• With your consent: In other situations with your express authorization

These suppliers process the data to provide the service we contracted, under their own data protection terms.

The bot verification (Turnstile) follows Cloudflare's Turnstile Privacy Addendum.

Some of these suppliers (Cloudflare, Stripe, Google and OpenAI) process data outside Brazil, including in the United States. These international transfers are necessary to perform the contract with you, at your request — processing your payment, generating the images you ask for, answering your messages in the conversation with the virtual assistant and delivering our e-mails —, under article 33, IX, of the LGPD. Vimeo and Google's YouTube, which show the site's videos when you click to watch them, and Meta's WhatsApp, when you message us there or we message you at the number you left, also process data in the United States; those transfers happen at your request, as steps before signing up — when you click to watch a video, message us or leave your number to be contacted —, under the same article 33, IX, of the LGPD. Google, through Google Analytics and Google Ads, and Meta, through the Meta Pixel and the Conversions API, also process the measurement and advertising data described above in the United States.

07Data Security

We implement appropriate technical and organizational measures to protect your data:

• Encryption: Connections use HTTPS (TLS); passwords are stored only as a hash; access keys and two-factor authentication secrets are stored encrypted
• Access control: The admin panel is restricted to our authorized team, requires two-factor authentication and only accepts access from Brazil; every administrative action is logged. You can also turn on two-factor authentication for your account
• Monitoring: Bot verification, attempt limits, automatic blocking of abusive IP addresses and audit records of account actions
• Secure backups: Daily database backups, kept on the server
• Updates: Regular system maintenance and security patches
• Minimal access: Our team accesses customer data and content only when needed for support, security, billing, fixing errors or improving the virtual assistant's answers
• Project images: Your project images are delivered from signed addresses that are practically impossible to guess, which Cloudflare caches for up to 2 months. Anyone with an image's exact address can open it during that period, even without signing in; so do not share those addresses

08Data Retention

We retain your personal data for as long as necessary for the described purposes:

• Account data: For as long as your account exists. Accounts are not closed for inactivity; an account is deleted at your request (section 9.1). The record of your use of the installed app (section 2.3) follows the same period
• Created projects: Your projects, photos and images are kept for as long as your account exists. We do not delete them automatically, not even when your subscription ends. What you move to the trash is permanently deleted 30 days later
• Communication data: The record of the e-mails we send is deleted after 90 days, except for three e-mails (the notice that a card is about to expire, the unfinished-payment reminder and the come-back invitation), which are kept as history with no time limit. Messages exchanged with support stay in our mailbox
• Security and access records: Sign-in attempts, with their approximate location: 90 days. Devices whose sign-in is remembered ("Remember me", or signing in with an account from another service, such as Google) — the browser, the system, the IP address and the approximate location of their last use and, with two-step verification on, the countries where the code was typed on it (each one until 4 months after its last use there): until the remembered sign-in expires (about 400 days, or 4 months without use) or is ended in Settings → Security. Technical server and application logs: 7 to 90 days. Records of the pages kept open (section 2.3), the device and account codes included: 2 days; the aggregate counts made from them: up to 3 years. Account action history (audit records, with IP, city, state, date and time): for as long as the account exists and, after deletion, for the legal period (section 9.1)
• Legal obligations: Invoices, payments, refunds, seller commissions and records of sales made outside the website are kept even after the account is deleted, for the period required by tax and accounting law
• AI-generated images: Kept with the scene until you delete the version or the scene; the composition sent to the provider is deleted as soon as the generation finishes and, when it fails, kept for up to 7 days for diagnostics; a copy of your composition at the moment of each generation is kept with the version, for the before/after comparison, and deleted together with it. The technical record of each generation (date, tool, model and the instructions sent, including the text you wrote) is kept for statistics and cost control even after you delete the version. A photo edit made through the virtual assistant is deleted as soon as you discard it and, if it is not used as the scene's background, 30 days after it is ready; used as the background, it stays with the scene like the scene's other images. For such an edit, the image sent to the provider and the copy kept for the comparison are the scene's own photo, with the same periods
• Backups: Daily database backups are replaced by rotation; deleted data may remain in them until the backup that contains it is discarded
• Ad measurement: Your first visit's origin (UTM, fbclid, gclid): while the account exists. The record of what our server told Meta, with the IP address and the browser's details: 90 days. What Google and Meta keep follows their own periods
• The full video form: The details you give to watch the full video (section 2.6) are deleted 24 months after the form's last submission — earlier, if you ask (section 9)
• The contact form: The details and messages sent through the contact form (section 2.7) are deleted from our records 24 months after they are sent — earlier, if you ask (section 9); the e-mail exchange that follows stays in our mailbox, like any other correspondence
• Conversations with the virtual assistant: Each scene's conversation is deleted 24 months after its last message, when the scene is permanently deleted from the trash, when our team moves its project to another account, or when your account is deleted. The support conversation ends when the assistant or our team closes it, or after 1 hour without messages — never while there is a message you have not read or a ticket open with our team; if you read a message after that hour, it ends 1 hour after that reading. Once ended, it no longer appears to you and is kept for 24 months, for our team only, then deleted; one that never ended (because a message was never read or a ticket stayed open) is deleted 24 months after its last message or its last reading, whichever is later. Tickets, ratings, read markers, the assistant's proposals and notices, with your choices about them, its notes on what it saw in the scene, and attached images, with their descriptions, are deleted with the conversation; an attached image that was never sent is deleted when you remove it or 24 hours after it was attached. The technical record of the assistant's use (date, model and amount of text processed, without the content of the messages) is kept for cost control. What OpenAI keeps follows its own periods (section 6)

At the end of each period, data is deleted or anonymized; in backups, when the backup is discarded.

09Your Rights as Data Subject

According to LGPD, you have the following rights over your personal data:

• Access: Request information about what data we have about you
• Correction: Request correction of incomplete, inaccurate or outdated data
• Deletion: Request the deletion of your account and your data (see how it works in section 9.1)
• Portability: Request a copy of your data in a structured format, including the photos and images of your projects, to take them to another provider
• Opposition: Object to processing based on legitimate interest
• Revocation: Revoke consent at any time
• Information: Obtain information about data sharing

To exercise your rights, write to legal@paisagia.com from the e-mail address registered on your account (or, if you only filled in the full video's form or the contact form, from the e-mail you gave there); account deletion is asked for as section 9.1 explains. We may ask you to confirm your identity first. You can turn off promotional e-mails yourself, through the unsubscribe link in any of them.

9.1 Account Deletion

Our team deletes your account at your request, sent to support@paisagia.com from the e-mail registered on your account, or made in a ticket you open in the support conversation with the virtual assistant while signed in to your account. If there is an active subscription, it is canceled when the account is deleted.

• We delete: your registration and profile data, profile photo, billing profile (tax ID and address), the link to your Google account, your preferences, all your projects, photos and generated images, the conversations with the virtual assistant about your scenes, with the images attached to them, the images you attached but never sent, and the details you gave in the full video's form and the contact form with your account's e-mail
• We keep, for the legal period: invoices, payments and refunds; access records (IP, date and time) and the account's action history; the commission of the seller who referred you, with your first name; and the record of a sale made outside the website, with your e-mail
• We keep for 24 months, for our team only, your support conversations with the virtual assistant, with the images attached to them — one still open is ended by the deletion —; and the technical records of artificial-intelligence use (date, model and amount processed, without texts or images), unlinked from the account, for the cost history
• For a while, the following may still exist: copies in backups, until rotation discards them (section 8); project images in Cloudflare's cache, for up to 2 months (section 7); and the data Stripe keeps about your payments, under its own obligations

We confirm the deletion by e-mail within 15 days of your request.

10Cookie Policy

We use cookies and similar technologies, such as the browser's local storage, to make the platform work, remember your preferences, credit partner sellers' referrals and the campaigns visits come from, measure visits and the results of our ads and show ads to people who visited the site, with the Google tag and the Meta Pixel (section 4.6). The site's videos, if you click to watch them, bring Vimeo's or YouTube's cookies (see Analytics, below).

10.1 Types of Cookies

• Essential: paisagia_sid (your session, 24 hours), _req_token (protection against forged requests, 24 hours), remember_web_… ("Remember me", about 400 days, or 4 months without use, when the option is ticked at sign-in or when you sign in with an account from another service, such as Google; with two-step verification on, it also skips the code on that device while it lasts, and the secret inside it is replaced every time it brings you back), _locale_redirected (2 seconds, prevents redirect loops), courses_stream (authorizes lesson playback, 3 hours) and paisagia_maint_admin (admins only, during maintenance, 4 hours). Cloudflare may also set its own protection cookies, including for bot verification
• Functionality: paisagia_locale (chosen language, 1 year) and timezone (the browser's time zone, 1 year). The editor also keeps drafts, copied items, preferences and the image-cutout model in your browser, and the browser keeps your choice in the cookie notice. Once you send the full video's form, the browser's local storage keeps a mark (paisagia_video_unlocked), with no details of yours, so the video opens straight away next time. In the installed app it keeps the day your use was already recorded, per account (paisagia_web_app_seen), and a copy of the page that says when there is no connection. A photo you share with the app or open with it stays on the device until it reaches the tools: if you sign out first, it is deleted at once; if it is not used within a day, it lapses and is deleted the next time the app is opened
• Analytics: Google Analytics 4, on the public pages, the sign-up, the plan choice and the profile filled in when the free trial starts or after payment: _ga and _ga_… (up to 2 years), which measure visits and the use of the site and, with Google Ads, build the ad audiences of section 4.6. If you click to watch the home page video, Vimeo's player sets its own: vuid (identifies the visitor in the playback statistics, about 400 days) and player (player preferences, 1 year), besides security cookies from Vimeo's own Cloudflare. If you click to watch the full video, YouTube's player sets its own: YSC (the playback session, until you close the browser) and VISITOR_INFO1_LIVE, VISITOR_PRIVACY_METADATA, __Secure-YNID and __Secure-ROLLOUT_TOKEN (YouTube's own playback statistics, preferences and protection, about 6 months), besides data in the browser's local storage, under YouTube's address
• Marketing: Google Ads, on the same pages: cookies such as _gcl_au (90 days) and, when you arrive from a Google ad, _gcl_aw (90 days), which link the visit to Google's ads and build the audiences of section 4.6. Meta Pixel, on the same pages: _fbp (90 days) and, when you arrive from a Meta ad, _fbc (90 days), which link the visit to the ads on Facebook and Instagram and build the audiences of section 4.6. Google and Meta may also use cookies of their own domains, according to your settings in your accounts with them
• Referral and campaign links: When you open a partner seller's link, a cookie (aff_ref) keeps their code and when you opened it — up to 5 links, each for up to 30 days — so your subscription is credited to whoever referred you first; a code that belongs to no seller is dropped. If the link was one of the seller's coupons or trial invites, a second cookie (aff_origin) keeps which one, for the same period. Coupon and trial invitation links keep the code in a cookie (promo_code or trial_invite) for up to 7 days, until you sign in. The trial invitation is also kept in your browser's local storage (paisagia_trial_invite) for up to 7 days, with the campaign's public details (plan, days and generations), so the home page's plans can show the trial; it is deleted when the invitation stops being valid or when you sign in to your account.When your first visit comes from a campaign or ad link, a cookie (paisagia_campaign) keeps its parameters (UTM, fbclid, gclid) for up to 90 days, until your account is created; they then move to the account and the cookie is deleted

10.2 Management

The website's cookie notice says that we use cookies and links to this policy. You may object to the measurement of visits and ads at any time, without affecting your use of the platform: by blocking or deleting the Google and Meta cookies in your browser settings, using the Google Analytics opt-out add-on, adjusting your ad preferences at Google (My Ad Center) and at Meta, or writing to our data protection officer (section 12.1). Blocking the essential cookies prevents signing in and using the platform.

11Changes to This Policy

We may update this Privacy Policy periodically to reflect changes in our practices or legislation. Significant changes will be communicated through:

• Email notification to registered users
• Prominent notice on the platform
• Update of the "last updated" date

We recommend that you review this policy periodically to stay informed about how we protect your data.

12Contact and Data Protection Officer

For questions related to data protection, exercise of rights or clarifications about this policy:

12.1 Data Protection Officer (Encarregado)

Paisagia's data protection officer (encarregado, under Brazil's LGPD) is Rodrigo Gomes, who can be reached at legal@paisagia.com.

12.2 Contact Channels

• Email: legal@paisagia.com
• Response time: Up to 15 days
• Supervisory authority: ANPD (National Data Protection Authority)

We are committed to responding to your requests clearly, completely and as quickly as possible.