← Back to homepage

Privacy Policy

Last updated: September 27, 2026

Your privacy is important to us. This Privacy Policy explains how Rafael Lourenço Rodrigues - Unipessoal Lda ("we", "the Company") collects, uses, maintains, and discloses information collected from users of rafaelrodrigues.pt ("the Site"). This policy applies to the Site and to all products and services offered by the Company. If you are here about rlrOS, our internal tool that connects to Google services, see Google user data (rlrOS).

Information We Collect

We may collect personally identifiable information from you when you visit our site, book a call, subscribe to communications, or interact with other features on the Site. You may be asked for your name and email address. You may visit the Site anonymously. We will only collect personal information if you voluntarily submit it to us.

Cookies and Tracking Technologies

The Site uses cookies to ensure the best experience. Cookies are small text files stored on your device. They allow us to monitor site usage, improve usability, and understand how visitors interact with the Site.

We use Google Tag Manager (GTM) to manage all tracking scripts on the Site. GTM itself does not use cookies, but the tags it loads may set cookies as described below and in our Cookie Policy.

The following third-party services are active on this Site:

• Google Analytics 4 (GA4) -- generates statistical information about site usage (pages visited, time on site, traffic source). Google Privacy Policy.
• Google Ads -- measures advertising effectiveness, conversion tracking, and remarketing. Google Privacy Policy.
• Meta Pixel (Facebook) -- measures ad performance and enables audience creation for Meta advertising platforms. Meta Privacy Policy.

All non-essential cookies are blocked until you provide consent via the cookie banner. You can change your preferences at any time. See our Cookie Policy for full details.

How We Use Your Information

We may use the information you provide to:

• Deliver our services effectively across your device
• Provide information, products, or services you have requested
• Fulfil obligations arising from any agreements between you and us
• Handle enquiries and provide customer service
• Improve and develop our services
• Send email notifications and communications you have opted in to

Disclosure of Your Information

We will not share, sell, or distribute your information without your consent, except as required by law. We may disclose your information to third parties where necessary to fulfil your requests, when required by law, or to enforce our rights under this policy.

We may disclose information to Google Inc. and Meta Platforms Inc. in order to deliver advertising services. You can review Google's Terms of Service and Meta's Terms of Service.

Third-Party Sites

The Site may contain links to websites operated by third parties. We do not control these sites and this Privacy Policy does not apply to them. Please review the privacy policies of any third-party sites you visit.

How We Protect Your Data

We take appropriate security measures to protect your information against unauthorized access, unlawful processing, accidental loss, destruction, and damage. However, data transmission over the Internet is inherently insecure, and we cannot guarantee absolute security.

Data may be transferred to cloud service providers with servers outside the European Economic Area (EEA). By using the Site, you agree to this transfer. Your information will only be kept for a reasonable period or as long as the law requires.

Google user data (rlrOS)

rlrOS is an internal tool we built to run our paid media and tracking work for clients. Only Rafael Lourenço Rodrigues uses it. We don't offer it to anyone else, and it has no public sign-up. rlrOS connects to some Google services through Google sign-in (OAuth). This section covers the Google user data it gets that way. The rest of this policy also applies.

What rlrOS accesses

Rafael signs in with the Google accounts he uses for client work. rlrOS can only reach the client accounts and files that those Google accounts already have access to. Through this sign-in, rlrOS asks for access to:

• Google Tag Manager: containers, tags, triggers and variables. rlrOS reads them and, when the work needs it, creates or edits tags and publishes container versions.
• Google Analytics: account and property settings, and report data such as sessions, conversions and revenue by channel or date. rlrOS reads them and can change property settings.
• Google Search Console: search performance data (queries, pages, clicks and impressions) and site status. Read only.
• Google Merchant Center: product data, feeds, account status and product issues. rlrOS reads them and, when the work needs it, updates product data.
• Google Docs: read only. rlrOS can read documents that the signed-in account can open. It only reads the ones Rafael points it to, such as a client brief.
• Google Sheets: read only. rlrOS can read spreadsheets that the signed-in account can open. It only reads the ones Rafael points it to, such as a budget plan or a product list.

rlrOS does not ask for access to Gmail or Google Ads through this sign-in.

How we use it

We use Google user data only to provide our paid media and tracking services to our clients. For example, to:

• Check that a client's tags and conversions track correctly, and fix them when they don't
• Read search, analytics and product performance to plan and improve a client's marketing
• Find and fix problems in a client's product data
• Build the reports we send to each client

We don't use it for anything else.

What we never do with it

• We don't sell Google user data.
• We don't transfer it to advertising platforms, data brokers or information resellers.
• We don't use it to serve ads, including retargeting, personalised ads or interest-based ads.
• We don't use it to decide credit-worthiness or for lending.
• We don't use it to create, train or improve AI or machine learning models.
• We don't build databases from it for any purpose other than the client work above.

Who reads it

Rafael reads the data as part of his work for the client it belongs to. We share reports and findings with that client, and with the partner agency we work through for that client, if there is one. Nobody else reads it, unless it's needed for security (for example, to investigate abuse) or the law requires it.

Who we share it with

We only share Google user data:

• With the client it belongs to, and with their partner agency where we work through one
• With AI model providers that help Rafael analyse data and draft work: Anthropic (Claude) and, for some tasks, Google (Gemini)
• With GitHub (private code storage and scheduled jobs), Vercel (hosting for a private dashboard behind a login) and Slack (messages to Rafael and to clients)
• When the law requires it

These service providers only process the data to run rlrOS for us. Some of these providers process data outside the European Economic Area.

How we protect it

• Sign-in tokens stay on Rafael's computer, in a private folder outside our code that only his user account can read. The computer's disk is encrypted.
• Tokens that scheduled jobs need are stored as encrypted secrets in GitHub Actions.
• When a task needs to keep results, such as the numbers behind a report, rlrOS saves them in a private GitHub repository or on the same computer. Dashboards built from them sit behind a login.
• Data travels over encrypted connections (HTTPS).
• Only Rafael has access to these systems.

How long we keep it, and how to delete it

• We keep Google user data while we work with the client it belongs to, and use it only for that work.
• When we stop working with a client, we stop pulling their data.
• If a client asks us to delete their data, we delete what rlrOS holds about them within one month.
• Clients can cut off access at any time by removing the Google account we use for their work (Rafael's own, or the partner agency's account we work through) from their Tag Manager, Analytics, Search Console or Merchant Center account. rlrOS can then no longer read that account.
• Anyone who has signed in to rlrOS with a Google account can remove it at any time: go to myaccount.google.com/connections and pick rlrOS from your linked apps.

Changes to how rlrOS uses Google data

If rlrOS ever needs new kinds of Google data, or will use it in a new way, we will update this section before it does and ask for consent again.

Limited Use

Questions about rlrOS or your data? Write to info@rafaelrodrigues.pt. You can also read what rlrOS is on its homepage.

Your Rights

Under the GDPR and Portuguese data protection law (Lei n.º 58/2019), you have the right to:

• Access the personal data we hold about you
• Request correction of inaccurate data
• Request deletion of your data
• Object to processing of your data
• Request restriction of processing
• Data portability
• Withdraw consent at any time

To exercise any of these rights, contact us at info@rafaelrodrigues.pt. We may request proof of identity.

Changes to This Policy

We reserve the right to update this policy at any time. Changes will be reflected by updating the date at the top of this page. Your continued use of the Site after changes are posted constitutes acceptance of the updated policy.

Contact

Rafael Lourenço Rodrigues - Unipessoal Lda
NIF: 519284755
Email: info@rafaelrodrigues.pt