Privacy policy

1. Who handles your data

OrchOps, S.L., tax ID B93940880, Calle de Luchana 23, 4.º, 28010 Madrid (España), provides the Ojaldrado service. For privacy matters, write to privacidad@ojaldrado.com. Our Data Protection Officer can be reached at dpo@ojaldrado.com.

We are the controller of the accounts of people who use the service. For the campaign data an organization connects for its reports, we act on behalf of that organization.

2. What data we handle and why

• Account: email address, language, role and organization, to give you access. Sessions: browser and dates, so you can see and close them.
• Security: access and change logs, passkeys (their public part only), a mark of each browser you sign in from (kept irreversibly hashed, to tell you by email when a new one signs in) and, temporarily, the IP address to limit attempts, to protect the account.
• Advertising platforms connected by an organization's administrator (Meta, Google Ads, Display & Video 360, YouTube, TikTok and others): the ID of the person authorizing, access tokens, names and IDs of accounts, campaigns, ads and creatives, currency, time zone and performance metrics, to build the reports.
• Audience: only figures aggregated by age, gender, region or device, as each platform provides them. We neither receive nor keep data about the people who see the ads.

The basis is the performance of the contract with your organization, our legitimate interest in protecting the service and, for each platform, the authorization given when connecting it.

3. Data from Google, YouTube, Meta and TikTok

We access these platforms to read only, and solely to show reports to the organization that connected them. We do not sell this data, do not use it for advertising or to train models, and do not share it except with the providers listed below.

Some platforms offer only a permission whose wording on their screen also says edit, create or delete: Google Ads ("See, edit, create and delete your Google Ads accounts and data"), Display & Video 360 and TikTok Ads through MCP. We ask for it because there is no read-only one, and our code only reads: it does not create, change or delete campaigns, ads or accounts. In Display & Video 360 it only creates and deletes report definitions, which do not affect anything that runs.

Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

We do not use data received from Google APIs to develop, improve or train generalized artificial intelligence or machine learning models. Anthropic, which writes the insights, does not train models on what we send it either.

For the YouTube channels their owners connect we use YouTube API Services. By connecting one you agree to the YouTube Terms of Service (https://www.youtube.com/t/terms), and the Google Privacy Policy (https://policies.google.com/privacy) explains how Google handles your data.

From YouTube we read the channel's name, picture and figures; its videos, with their views, watch time, impressions, likes, comments and shares; and its audience as figures aggregated by age, gender, country, device and traffic source. We keep it for the reports of the organization that asked for it, only the people that organization gives access to see it, and only the providers in section 4 also handle it. We neither read nor answer comments, and we change nothing on the channel.

We check at least every 30 days that your authorization still stands. If you withdraw it, or 30 days go by without the channel being read, we delete what you authorized: within 7 days if you remove the connection in Ojaldrado, and within 30 if you withdraw it at Google. You can withdraw it at any time in your Google account's security settings (https://security.google.com/settings/security/permissions).

Access tokens are stored encrypted.

4. Who we share it with

Reports are seen by the people your organization gives access to. To give support, someone at OrchOps with platform administration access can enter your organization: only with their passkey, for at most 8 hours each time, and everything they open or change is recorded in «Support access», which your administrators can see. We use providers that handle data on our behalf: Railway (hosting), Cloudflare (network and security, including the anti-bot check), Resend (email) and Anthropic (writes the insights of reports that have them turned on, from their figures and the context your organization adds; it does not receive the list of readers or the names of social profiles, which it knows only by a number, and we take mentions, emails and phone numbers out of the texts it receives). Where any of them handles data outside the European Economic Area, it does so with the safeguards the GDPR requires.

5. How long we keep it

• Sign-in codes expire after 10 minutes, and sessions after 30 days at most. A browser’s mark is deleted 400 days after you last signed in from it.
• The record of sign-ins is deleted after 12 months, and the record of changes (who changed what in rules, permissions, reports and deliveries) after 3 years. Only who created a report is kept longer, while that report exists.
• Account data and reports are kept for as long as the relationship with your organization lasts.
• The data of a connection is kept until it is disconnected and its deletion requested, or until you withdraw authorization from the platform.
• A social profile's data (followers, posts and their figures) is kept while a report uses it: the days of the campaigns of the reports that follow it, while those reports exist. What falls in none is deleted 30 days after no active report follows the profile, and all of it once no report follows it.

6. How to disconnect and delete data

An organization's administrator can disconnect a source in Connections: access is revoked where the platform allows it, and data stops being read. From the same place they can ask for that connection's data to be deleted.

You can also withdraw access from the platform itself. If you do so on Meta, we receive the notice and act on it. For any other deletion request, write to privacidad@ojaldrado.com.

7. Cookies

We use a session cookie, needed to sign in, another that recognises your browser so we can tell you when your account is entered from a new one, and others that remember a report's language and theme. We use no analytics or advertising cookies. Cloudflare may use its own for the anti-bot check. The public website, ojaldrado.com, sets no cookies at all.

8. Your rights

You can request access, rectification, erasure, restriction, objection and portability at privacidad@ojaldrado.com. If your data reached us through an organization, you can also contact it. You can complain to the Spanish Data Protection Agency (aepd.es).