Pista

Legal

Privacy Notice

Updated 5 October 2026Version 1.3Effective 5 October 2026

Summary · plain language, not the binding text

Luka Pejcic, in the United Kingdom, controls your data. Pista collects what it needs to run: your account, profile, matches and community activity. It is stored in Frankfurt. In the app, analytics runs only if you agree, and you can turn it off in Settings. Pista does not sell personal data. Delete your account in the app and identifiable data is deleted or anonymised within 30 days; download your data there too. For anything else, write to luka@pistasocial.com, and you can complain to the ICO.

The notice

1. Who controls your data

Luka Pejcic is the data controller for Pista and is based in the United Kingdom. Contact: luka@pistasocial.com.

This notice explains how Pista handles personal data when you use the Pista app, website, waitlist, support channels, and related services.

2. Information we collect

Depending on how you use Pista, we may collect:

  • account and authentication data, such as email address, provider identifier, authentication events, and session/security records;
  • profile data, such as name, handle, profile photo (if you add one), bio, skill level, play style, home club, main racket, the social-media handles you choose to show (Instagram, TikTok, Facebook, X, or Strava), and community choices;
  • guest profiles: a community leader can add a player who has no Pista account yet by entering a name for them, so that player's matches count. A guest profile holds that name and the guest's matches and results, is shown on the community's boards, including its public board when the leader turns that on, and becomes the player's own profile if they claim it;
  • community and match data, such as memberships, roles, invitations, match participation, results, disputes, votes, posts, comments, and related timestamps;
  • safety and moderation data, such as reports you make or that concern you, players you block, and any warning or suspension on your account;
  • communications and support data you send to us;
  • device and technical data, such as app version, operating-system class, browser or user-agent, IP-derived security information, crash information, and security logs;
  • notification choices and device push identifiers where notifications are enabled;
  • if you agree to analytics in the app, product analytics events, the name of the app screen you are on, and crash information, with a random install identifier that is not linked to your account, name, or email (PostHog is set to discard your IP address);
  • if you agree to analytics on the website, the pages you visit, the links and buttons you click (without their text), a small set of named events, and your browser and device type, with a random identifier kept in your browser that is not linked to your account, name, or email; and
  • waitlist data, including email address, signup source, signup time, and browser or user-agent.

We do not ask for special-category data and you should not post sensitive personal information about yourself or others unless it is necessary and lawful.

3. Where information comes from

We receive information directly from you, from activity in Pista, from other users who participate in shared matches or communities, from clubs or community leaders where appropriate, and from authentication and infrastructure providers.

4. Why we use information and our lawful bases

We use personal data:

  • to create, authenticate, secure, and administer your account and provide requested Pista features, because this is necessary to perform our contract with you;
  • to operate profiles, communities, matches, feeds, support, and service communications, because this is necessary for our contract or our legitimate interests in operating Pista;
  • to prevent fraud, abuse, unauthorised access, and service disruption, based on our legitimate interests in protecting users and Pista;
  • to diagnose faults and improve reliability and accessibility, based on our legitimate interests, using minimised technical information;
  • to measure how the app is used, so we can improve it, based on your consent. This is product analytics: a small set of named in-app events and the name of the screen you are on. We ask you for this in the app and send nothing before you agree. You can refuse, and refusing changes nothing else about Pista. You can withdraw your consent at any time in Settings → Privacy → Analytics. On https://pistasocial.com we ask with a banner, load nothing for analytics before you accept, and let you change your answer at any time with Cookie settings at the foot of every page;
  • to let a leader record matches for players who have no account yet, as guest profiles, based on our and the community's legitimate interest in keeping a complete match record. A guest can claim the profile, and the leader can correct or remove it; you can also ask us to;
  • to manage the launch waitlist and send requested launch information, based on your request and, where required, your consent;
  • to send optional marketing or notifications where consent is required; you can withdraw that consent or change device permissions. Marketing messages are off unless you turn them on in Settings → Notifications;
  • to keep Pista safe after a suspension, based on our legitimate interest in preventing a suspended person from returning by deleting and re-creating their account (see section 7); and
  • to comply with legal obligations and establish, exercise, or defend legal claims.

Where we rely on legitimate interests, we balance those interests against your rights and reasonable expectations.

5. Who receives information

We disclose only the data needed for each service. Current or planned providers for the initial service include:

  • Supabase for authentication, database, file storage, and related backend services, hosted in Frankfurt, Germany;
  • Resend for email delivery: sign-in codes, and service emails such as a welcome email when you finish setting up and a note to a leader when a player claims a guest profile in their community;
  • Apple and Google when you choose provider sign-in;
  • Expo and EAS for mobile application build and delivery services;
  • Expo's push service, which passes notifications you have turned on to Apple or Google for delivery to your device;
  • Vercel for website hosting and request infrastructure;
  • PostHog for product analytics in the app and on the website, and crash reporting in the app, where you have agreed to analytics;
  • Google (Google Sheets) for the launch waitlist, which stores the email address you give us; and
  • professional advisers, authorities, or service providers where reasonably needed for legal compliance, security, or a business transfer.

Other Pista users can see profile, community, match, and content information according to the service's visibility and membership rules. We do not sell personal data.

Some pages on https://pistasocial.com can be opened by anyone who has the link: a shared match, post, vote, or community, and a community's public board. They show first names or initials, scores, and results, and a short excerpt of a shared post. A public board also shows its guest profiles by the name the leader entered. They never show a player's email address, handle, photo, or social-media handles.

6. International transfers

Some providers may process data outside the United Kingdom. Where UK data protection law requires safeguards, we use an adequacy regulation, the UK International Data Transfer Agreement or UK Addendum, or another lawful transfer mechanism, together with appropriate security measures.

Pista's database and uploaded photos are stored by Supabase in Frankfurt, Germany. Analytics data you have agreed to send is processed by PostHog in the European Union (its EU cloud, hosted in Frankfurt). The UK recognises the EU as adequate for data protection, and the in-app consent screen names the region too.

7. How long we keep information

We use these initial retention periods:

  • active-account data: while the account is active and as needed to provide Pista;
  • account deletion: identifiable account data is deleted or anonymised within 30 days of a valid deletion request, unless a longer period is required by law or for a documented security or legal claim;
  • shared match history: may be preserved after account deletion only in anonymised form so other participants' records remain coherent;
  • launch waitlist: 12 months from signup or until you withdraw, whichever is earlier;
  • security and access logs: 90 days, unless a specific incident requires a documented longer hold;
  • support records: 24 months after the support matter closes;
  • moderation and staff-action records: while needed to handle reports, disputes, repeat abuse, and legal claims; after account deletion they refer only to an anonymised participant;
  • the audit log, which records account, community, moderation, and staff actions: 24 months from each entry, after which it is deleted automatically;
  • a match a leader deletes: it leaves every board, feed, and profile, but we keep it, hidden, for audit and to settle disputes, for as long as the community's other match records are kept;
  • a suspended account that asks to be deleted: we delete or anonymise its profile as for any deletion, but keep its email address, sign-in record, and the suspension itself until the suspension is lifted, so that the same person cannot return by deleting and signing up again. This relies on our legitimate interest in keeping Pista safe. When the suspension is lifted, we finish the deletion; and
  • product analytics, in the app and on the website: events are not linked to your account, name, or email and are kept only as long as needed to understand how Pista is used.

We review retained data and securely delete or anonymise it when no longer needed.

8. Account deletion and anonymisation

You can delete your account in the app, under Settings → Data → Delete account. Your account closes straight away and we erase or anonymise your identifiable data within 30 days. You can sign up again with the same email at any time, as a new player; the old account does not come back. If you can't use the app, email luka@pistasocial.com; we may need to verify that the request concerns your account. https://pistasocial.com/delete-account explains both routes.

Deletion removes or de-identifies the account link and directly identifying profile data, including your profile photo. Shared records may retain an anonymous participant so match, ranking, moderation, or dispute records involving other people remain accurate. Posts and comments you wrote may stay in their community, shown as [Deleted User]; you can delete your own posts in the app before you delete your account. Anonymised information is no longer used to identify you.

9. Your rights

Subject to UK data protection law, you may have rights to:

  • be informed about our use of your data;
  • access a copy of your personal data;
  • correct inaccurate or incomplete data;
  • request deletion or restriction;
  • object to processing based on legitimate interests;
  • receive portable data where applicable;
  • withdraw consent without affecting earlier lawful processing; and
  • ask for review of a significant decision made solely by automated means.

You can download a copy of your data yourself in the app, under Settings → Data → Download my data, and correct most of your profile in the app. The download leaves out matches a leader has deleted, which we keep for audit (section 7); ask us and we will include them. To exercise any right, contact luka@pistasocial.com. We may ask for proportionate identity verification. You can also complain to the UK Information Commissioner's Office at https://ico.org.uk/make-a-complaint/.

10. Children

Pista is for adults aged 18 or older. We do not knowingly allow anyone under 18 to create an account. Contact us, or report the player in the app as an underage user, if you believe a person under 18 has supplied personal data; we will close the account.

11. Security

We use access controls, encryption in transit, restricted administrative access, server-side authorisation, data minimisation, and monitoring appropriate to the risk. No online service can guarantee absolute security.

12. Website storage, analytics, and auth callbacks

The initial website may use strictly necessary storage or similar technology to operate requested features. It sets no cookies, and it serves its own typefaces, so loading a page sends nothing to a font provider.

Website analytics is provided by PostHog and is off until you agree to it. A banner at the foot of the page asks, with Accept and Reject given equal weight. Nothing for analytics loads before you accept, and nothing loads if you reject. If you accept, PostHog keeps a random identifier in your browser's storage, under names beginning ph_, and the site sends the analytics described in section 2, tagged with the website's address. It sends no name, email address, handle, or account identifier, records no session replays, and PostHog is set to discard your IP address. The site remembers your answer in your browser for 12 months and then asks again. You can change it at any time with Cookie settings at the foot of every page. Withdrawing stops any further collection and clears what is stored in your browser; to delete what was already sent, contact us. Marketing technology is not used on the website. The site's Cookies page, https://pistasocial.com/cookies, lists what it stores.

In the mobile app, optional product analytics is provided by PostHog and is off until you agree to it. The app asks during onboarding and records your answer on the device. Nothing is sent before you answer, and nothing is sent if you refuse. You can change your answer at any time in Settings → Privacy → Analytics; turning it off stops sending at once and discards anything not yet sent. If you allowed analytics, the app may ask you a short survey once. Your answers, including any words you type, are sent with your analytics to PostHog in the European Union, never with your name or email.

Under the Privacy and Electronic Communications Regulations (PECR), Pista stores or reads information on your device only where it is strictly necessary for a service you asked for, such as keeping you signed in, or with your consent, such as analytics.

The /auth/callback fallback does not display, persist, or application-log callback parameters and loads no analytics or error-reporting SDK. Hosting infrastructure may process the requested URL in restricted operational logs; access and retention must be limited.

13. Changes and contact

We may update this notice when Pista, our providers, or legal requirements change. We will publish a new last-updated date and provide additional notice where required.

Privacy questions and rights requests can be sent to luka@pistasocial.com.