Privacy Policy
Last updated:
Information you send us
The inquiry forms on this website ask for your name, email address, telephone number, project location, property type, the service you are interested in, an approximate budget, your desired timeline and a short description of your project. Only your name, email address, project location, service and message are required; the remaining fields help us prepare for the first conversation and are entirely optional.
How your inquiry travels
When you send an inquiry, the form is processed by our website's own server, not by a third-party form service and not by your email client, and delivered as an email toinfo@paulaambrosio.com. If the inquiry reaches us, you also receive a confirmation email at the address you provided. We keep your message in our mailbox and in our project records. Our website does not manually send inquiry messages to advertising services; the optional OpenAI Pixel behavior is described below.
How information is used
Inquiry information is used to answer your message, schedule consultations and communicate about a potential project. We do not sell your personal information, and we do not share it with third parties for their own marketing.
Service providers
This website is hosted by Vercel, which processes requests, including form submissions, on our behalf. Email is delivered through the mailbox provider that hosts info@paulaambrosio.com. Both act as service providers under our instructions and receive only what is required to deliver the service.
Automated inquiry triage
When automated triage is enabled on this website, the following data about your inquiry is sent to TypeSafe AI (api.typesafe.ai), a classification service that returns an advisory score: your name, the page your inquiry came from, the text of your message (first 1,600 characters), and the project details you filled in: location, property type, service requested, budget stated and timeline stated. Our team uses the score to sort and prioritize inquiries. TypeSafe AI does not send replies and does not automatically reject or approve inquiries. Whether triage runs is a server-side configuration of this website, separate from the Privacy choices for analytics and advertising. When triage is disabled, nothing is sent.
Analytics and performance data
We use Vercel Web Analytics and Vercel Speed Insights to understand which pages are visited, broadly where visitors come from and how the site performs on real devices. These reports are aggregated and do not build advertising profiles. The contents of an inquiry (your name, contact details and message) are never included in that data; we only record which page a form was sent from and which service was selected.
Optional Google tools and your consent
Our Privacy choices control offers separate, optional choices for website analytics and advertising measurement. Both are off until you choose them. Google Tag Manager loads only after you allow at least one category. Loading it sends Google a network request, which includes technical connection information such as your IP address and browser information. Google Analytics 4 runs only when you allow website analytics. Google Ads measurement runs only when you allow advertising measurement. Remarketing and personalized advertising remain disabled.
Analytics measures visits to public pages and selected interactions with our services and website controls. Google may use analytics cookies and technical identifiers and process device, browser and approximate geographic information to produce these reports. We do not send names, email addresses, telephone numbers, inquiry messages or other contact-form fields to these Google tools. Automatic collection of user-provided contact data, Google Signals, enhanced conversions and personalized advertising are not enabled. An interaction or form attempt is not recorded as proof of an accepted or qualified lead. When advertising measurement is allowed, Google Ads receives an accepted-inquiry event only after our server confirms that the inquiry passed its acceptance checks and was saved in persistent project records. This event includes a random, opaque transaction identifier to avoid duplicate counting, not contact fields. Google may use first-party attribution cookies, advertising click identifiers and technical browser information to associate it with an ad. Acceptance does not mean a qualified opportunity, an email delivery or a sale. We retain up to 100 opaque Google event identifiers in this tab's session storage while advertising measurement is allowed and remove them when it is withdrawn. See Google's Privacy Policy for how Google handles data.
Our preference record saves your optional-tool choices and their date in this browser. Your choices are valid for up to 90 days before we ask again. You can reject or change them through Privacy choices without losing access to our forms. Withdrawing permission immediately stops our site from sending further measurement events and attempts to remove first-party Google measurement cookies. If tools have already loaded, we offer a reload after you finish your form to unload them. Previously sent data is not undone by changing your browser choices.
Optional OpenAI advertising measurement
If you allow Advertising measurement in Privacy choices, we load the OpenAI Pixel. The request shares technical connection information, including your IP address and browser information, with OpenAI. The Pixel may use first-party cookies and advertising click or browser identifiers for attribution. Its __oppref cookie can last up to 30 days and its __obref cookie up to 365 days, subject to your browser's restrictions.
We do not manually supply contact details, hashes of contact details, budgets or inquiry messages to the Pixel. Depending on the Pixel's account settings, OpenAI's automatic advanced matching may detect supported contact information entered on this site and hash it in your browser for conversion matching. We have not verified that this automatic matching is disabled. Hashing does not make this information anonymous. With advertising measurement permission, we send a lead-created event only after our server confirms that an inquiry passed its acceptance checks and was saved in our persistent project records. The event contains an opaque random identifier and the event type, not the inquiry fields. We opt these events out of future user-level personalization. This records acceptance of an inquiry, not a qualified opportunity, an email delivery or a sale.
To avoid counting the same accepted inquiry again, we retain up to 100 opaque event identifiers in this browser tab's session storage while advertising measurement is allowed. These identifiers contain no contact fields. Our server keeps a retry record for seven days so an unchanged retry can reuse the same acceptance identifier. The Pixel is not loaded before advertising permission is granted. Withdrawing permission instructs the Pixel to stop measurement and removes its first-party attribution cookies and our session event identifiers. Reload after finishing your form to unload code already loaded; previously transmitted data cannot be recalled by changing these choices. SeeOpenAI's Privacy Policy andOpenAI's Pixel documentation.
Optional Meta advertising measurement
If you allow Advertising measurement in Privacy choices, we load Meta Pixel for Paula Ambrosio's advertising account. It may share technical connection and browser information with Meta and use cookies or similar identifiers for ad measurement. We do not send contact fields, form values or inquiry messages to Meta. This integration does not use advanced matching, Conversions API or custom conversion events. After permission, it sends one standard PageView for the document. When the server confirms acceptance of an inquiry, we send a standard Lead event with an opaque receipt ID to prevent duplicates, without contact fields. When direct checkout measurement is enabled on Change Order, activating a configured Hotmart checkout link also sends the standard InitiateCheckout event to our pixel. This measures a click-through, not a sale, payment or confirmation that the checkout loaded. No form values or checkout URLs are included in that event payload. The Pixel is not loaded before advertising permission. Withdrawing permission stops further measurement and requires a reload before any future initialization. See Meta's cookie policyand Meta's Privacy Policy.
Security
All traffic to this site uses HTTPS. Email credentials live only on our server and are never sent to the browser. Submissions are validated on the server and protected against automated abuse.
Your choices
You may ask us to correct or delete the information you have sent us at any time. Write toinfo@paulaambrosio.com and we will remove it from our records, except where we are required to keep it for accounting or legal reasons.
Contact
For any privacy question, contactinfo@paulaambrosio.com.