Privacy Policy

Version 1.0 · Effective date: July 27, 2026

This policy covers Podio, the app for tracking amateur padel matches on Android and iOS, and also this site, including the pre-launch waitlist. This English version is a courtesy translation: if anything differs, the Spanish version prevails.

The short version

• Podio is free and has no ads. We do not sell your data, and we do not hand it to advertisers or data brokers. Ever.
• We keep what the app needs to work: your account, your profile, and the matches and leagues you record.
• Your profile and your results are public inside the app. It is a ranking app: the whole point is that other players can see the table.
• We run on Google services (Firebase). At launch we will add analytics and error tools (Google Analytics for Firebase, Mixpanel, Crashlytics, Sentry). You will be able to turn analytics off from the app.
• If you delete your account, your personal data is wiped. Matches remain, but without your name: they become anonymous. Below we explain exactly what remains and why (see “How long we keep it”).
• If you join the waitlist, we keep your email to notify you exactly once when the app launches. Nothing else.
• Questions or requests: sanchez.gonzalo94@gmail.com.

That is the essence. What follows is the full detail.

Who is responsible

The data controller is Gonzalo Sánchez, in Argentina, the same name listed as the developer of Podio on the app stores. You can reach him by email at sanchez.gonzalo94@gmail.com.

The personal data described in this policy is part of databases under his responsibility, hosted on the infrastructure of the providers detailed below.

Contact for anything privacy related: sanchez.gonzalo94@gmail.com.

What data we collect

We collect only what the app and this site need. Here is everything, by category.

Account and profile data

Required to create an account (Argentine law, Ley 25.326, asks us to state what is mandatory and what happens if you do not provide it: without this data an account cannot be created, and that is the only consequence):

• Email and password, or the profile Google or Apple shares with us if you sign in with those providers (name and email; Apple lets you use a relay email that hides yours).
• First name, last name, and username (@handle).
• Year of birth: we ask for it only to verify you are 16 or older. It is not shown on any screen of the app, but today it is stored inside the same profile record that other users can technically read (see “Who we share it with”).
• Gender and playing category: used to match competitive categories and compute the rating.

Optional (nothing happens if you skip them): profile photo, short bio, and playing preferences (dominant hand, preferred side, style).

Generated by the system: your internal user identifier (UID), your internal rating and its confidence margin (never shown as such to anyone), your account status (active, suspended, deleted), and moderation annotations if any exist.

Content you create in the app

• Match results: teams, sets, format and outcome, with an edit history recording who changed what and when.
• Match photos you upload and YouTube video links you paste into a match.
• Leagues you create or join: name, points scheme, administration, and your statistics inside the league.
• Social relationships: who you follow (visible to anyone) and who you block (only you can see that).
• Moderation reports you submit (a reason plus an optional free-text note) and guest identity claims.

Data about other people that you enter

If you record a match with players who do not have an account, you enter their first and last name as guests. That data identifies a real person: enter it only if that person agrees. The same applies to people you mention in the note of a moderation report. If someone without an account wants their name removed from the app, they can write to us (see “Your rights”).

Technical identifiers and notifications

• Your device’s push notification token (Firebase Cloud Messaging) and the state of the operating system’s notification permission.
• Your in-app notification tray (type of notice, reference to the event, read date). These expire and delete themselves.
• IP addresses in Google’s internal infrastructure logs (Firebase Auth, Firestore, Storage, Cloud Functions). We do not see or use them ourselves: they are part of the platform’s normal operation.

Analytics and diagnostics (from launch)

Today the app does not send product analytics or error reports to any external provider: events stay in a local debug log on your phone and never leave it. Activating these tools is confirmed for launch, so we declare them now:

• Usage events (which screens and features are used), installation and device identifiers (Android ID or IDFV, instance identifiers, Mixpanel’s distinct ID), device model, operating system, and app version.
• Crash and error reports: installation identifier, IP address, stack traces (the technical trail of the error), and device characteristics.
• Approximate location (city level) that analytics providers derive from the IP. We never collect your precise location and we do not use the phone’s advertising identifier.

Waitlist (this site)

If you sign up to be notified about the launch, we store:

• Your email and the language you signed up in (Spanish or English).
• If you arrived from a campaign or another site: the utm_source, utm_medium and utm_campaign tags in the URL, and the address of the page you came from (referrer). This only tells us which channel you arrived through.

Signup is single opt-in: we do not send a confirmation email, and the only message you will receive is the launch notice.

Analytics on this website

This site uses Google Analytics 4 to measure traffic in aggregate: how many people visit, which channel they arrive through, and which pages they look at. That is how we decide which content is worth keeping. Google Analytics sets measurement cookies and processes a shortened version of your IP address. We use no advertising features, we do not cross this data with your waitlist email, and we do not track you across other sites. If your browser sends a Do Not Track or Global Privacy Control signal, we do not load analytics. You can also block it with the Google Analytics opt-out add-on or by refusing cookies in your browser.

What we use it for

Each use with its GDPR legal basis (Art. 6), where that applies. In Argentina the general basis is your consent: you accept this policy when you create an account or join the waitlist (Ley 25.326, Art. 5).

• Operating your account: creating it, authenticating you, and sending you account notices (password recovery, important changes). Basis: performance of the contract.
• Recording matches and leagues: storing results, resolving opponent confirmations, guest identity claims, and standings. Basis: performance of the contract.
• Computing ratings and rankings: your rating and category are computed automatically from your match results. It is a transparent calculation of the game’s mechanics: it orders the table, it does not make decisions with legal effects about you and it does not profile you for anything else. Basis: performance of the contract.
• Push notifications: telling you about matches, confirmations and followers. Basis: your consent (the system’s notification permission); revoke it any time from your phone’s settings.
• Moderation and safety: reviewing reports, applying sanctions, preventing abuse. Basis: legitimate interest in keeping the community safe.
• Product analytics (from launch): understanding which features are used, to improve the app. Basis: legitimate interest, or your consent where the law requires it; you can turn it off from the app.
• Error diagnostics (from launch): detecting and fixing failures. Basis: legitimate interest in a working app.
• Waitlist: sending you a single launch notice and measuring which channel you arrived through. Basis: your consent; withdraw it by requesting removal by email.

We do not use your data for advertising, ours or anyone else’s, and we do not combine it with data from other companies.

Who we share it with

With other users of the app

Your profile (name, username, photo, bio, gender, category, and playing preferences) and the matches you play are publicly visible inside the app: any user can see them, search for you, and find you in the ranking. Leagues are visible to their members. Who you follow is public; who you block is not. One honest note: the public profile record also includes your year of birth, even though the app does not display it on screen; we would rather you hear that from us.

Service providers (data processors)

All of these providers act as data processors, under data processing agreements that require them to protect your data with a level of protection equivalent to this policy and forbid them from using it for their own purposes.

Google Analytics for Firebase, in detail (disclosure required by its terms of service): it uses installation and device identifiers to measure usage events. We use only standard event measurement and aggregated statistics: no advertising features and no phone advertising identifier. You can read how Google uses that data in How Google uses information from sites or apps that use its services. And you will be able to turn analytics off from the app’s settings: the switch shuts collection down completely (internally it calls setAnalyticsCollectionEnabled(false)).

YouTube videos: if a match has a video attached, the app embeds the YouTube player. When you play it, YouTube (Google) receives the request from your device and applies its own privacy policy.

Nobody else

We do not sell your data. There is no advertising in the app or on this site. We do not share data with advertisers or data brokers. We would only hand data to a public authority if a valid law or court order compels us to.

How long we keep it

While your account is active, we keep your data to run the service. When you delete the account we apply a tombstone model: we do not erase the whole record, we empty it. We want to be precise about what is deleted and what remains.

Deleted or emptied when you delete your account:

• Your authentication user (Firebase Auth) is truly deleted: your email and login credentials cease to exist.
• First name, last name, username, bio, playing preferences, year of birth, and the email stored in your settings are nulled.
• Your profile photo is physically deleted from storage.
• Push notification tokens are emptied; Firebase installation identifiers are purged from Google’s systems within 180 days.

What remains, and why:

• Confirmed matches are never deleted: they are also the history of the other three people who played, and those people’s ratings must remain recomputable. Your name stops being displayed (the match becomes anonymous), but the match and your internal identifier (a code, without your name) persist.
• Your gender and category are kept indefinitely as the seed for that recomputation of third parties’ ratings. They are the only part of the profile that is not emptied.
• Your internal rating is kept; it was never visible to anyone.
• Leagues are not deleted. Your membership inside a league is marked as that of someone who left; if you were an admin, administration passes to another active member, and the league is archived only if no active members remain.
• Guest names entered in a match persist for as long as the match exists.
• Moderation reports are kept indefinitely (they have no automatic deletion); identity claims are deleted once resolved.
• Follow and block relationships are removed when you undo them; today they are not cleaned up automatically when you delete your account, although they end up pointing at an emptied profile.

Provider retention periods:

• Crashlytics keeps crash reports for 90 days.
• Firebase Auth logs containing IPs are kept for a few weeks; Google Cloud infrastructure logs, for short periods defined by Google.
• Google Analytics and Mixpanel retain events according to each project’s configuration; we will publish the exact periods in the first update of this policy after activating them.

Waitlist: your email is stored until we send the launch notice. There is no automated removal mechanism today: if you want out earlier, write to sanchez.gonzalo94@gmail.com and we will delete it by hand.

Legal obligations: if a rule requires us to retain something for longer, we comply and retain only what is strictly necessary.

Your rights

All of these rights are exercised free of charge by writing to sanchez.gonzalo94@gmail.com, from the app, or from this site’s account deletion page.

In Argentina (Ley 25.326) you have the rights of access, rectification, updating, and deletion:

• Access: we respond within 10 calendar days of your request. It is free of charge at intervals of no less than 6 months, unless you show a legitimate interest in asking sooner.
• Rectification, updating, or deletion: within 5 business days.

If the GDPR applies to you (for example, if you live in the European Union) you also have the rights of access, rectification, erasure, restriction of processing, data portability, and objection, plus the right not to be subject to automated decisions with legal effects (the rating calculation is not one: see “What we use it for”).

Withdrawing consent: you can withdraw it at any time, without affecting the lawfulness of prior processing. In practice: by deleting your account, turning analytics off in the app, revoking the notification permission, or requesting removal from the waitlist.

Deleting your account: from the app (Profile, Settings, Account) or from the account deletion page if you already uninstalled the app. Important: deletion works as the previous section explains; your personal data is wiped, but matches become anonymous, they do not disappear.

If you do not have an account: if your data appears in the app because someone entered you as a guest in a match or mentioned you in a report, write to us all the same: same email, same deadlines.

Supervisory authority

The Agencia de Acceso a la Información Pública (Argentina’s data protection authority), in its role as the enforcement body of Ley 25.326, has the power to handle complaints and claims filed by those whose rights are affected by a breach of the rules on personal data protection. You can reach it through argentina.gob.ar/aaip.

If you are in the European Union, you also have the right to lodge a complaint with the supervisory authority of your country of residence, your place of work, or the place where you believe the infringement occurred.

International transfers

The main database (Firestore) and photo storage are hosted in Google Cloud’s southamerica-east1 region (São Paulo, Brazil). Some services process data outside that region: Firebase Auth operates in the United States, and the analytics and diagnostics providers (Google, Mixpanel, Sentry) process data globally.

Those transfers rest on data processing agreements with contractual clauses of the kind approved by Argentina’s Disposición 60/2016 and on the European Union’s standard contractual clauses; Google, Mixpanel and Sentry additionally participate in the EU-US Data Privacy Framework. Argentina holds an adequacy decision from the European Union regarding its level of data protection.

Minors

Podio is for people aged 16 or older. When you create an account we ask for your year of birth with a neutral form (no pre-ticked boxes, no suggested answers). We do not knowingly collect data from children under 16: if we detect an account belonging to someone under 16, we delete it. If you are a parent or guardian and believe a child under 16 created an account, write to sanchez.gonzalo94@gmail.com and we will remove it.

Security

• Data travels encrypted (TLS) and is stored encrypted at rest on Google’s infrastructure.
• Access rules are defined per piece of data: private data (your email, your notifications, your blocks) can only be read by your own session, and some internal data (your raw rating) cannot be read by anyone, not even you.
• Passwords are managed by Firebase Auth: they never reach our database and we never see them.
• Administrative access is limited to the controller and the server-side functions.
• At launch we add Firebase App Check, which rejects traffic that does not come from the genuine app.

With this we meet the security duty of Article 9 of Ley 25.326 and we take the measures recommended by the AAIP (Resolution 47/2018) as our reference. No system is infallible: if a security incident affects your data, we will let you know.

California

If you live in California: Podio does not meet the thresholds that make the CCPA/CPRA applicable (not by revenue, not by volume of California residents’ data, not by selling data). Even so, here is what matters: we do not sell or “share” (in the CCPA sense of that word) personal information, and you can exercise the same access, correction, and deletion rights in this policy by writing to sanchez.gonzalo94@gmail.com. You will not be treated any differently for exercising them.

Changes to this policy

When we change this policy, we publish the new version here with its number and effective date. If the change is significant (new data, new providers, new uses), we will tell you before it takes effect, in the app or by email.

The Spanish and English versions are published together, with the same version number and date. This policy is drafted in Spanish; the English version is a courtesy translation and, in case of any discrepancy, the Spanish version prevails.

Version 1.0 · Effective date: July 27, 2026

Questions? Write to sanchez.gonzalo94@gmail.com.