Privacy Policy

Who is responsible for your information

This policy describes personal information handled through Plryer at plryer.dev and its player-development workspace. Jose Fernandez, operating Plryer, based in the United Arab Emirates, is responsible for account administration and operating the service.

When a club or coach enters player or staff information, that club or coach determines why it is collected and how it is used. Plryer processes those workspace records to provide the service on their behalf. If your club added your information, you do not need a Plryer account for this policy to be relevant. Ask your club for its own privacy notice as well.

Questions about your account or Plryer’s handling of information can be sent to privacy@plryer.dev. For player records, contact the club that manages the workspace first.

Information we handle

• Account and staff details: email, name, profile photo, authentication credentials and session information, invitations, club memberships, access role, job title and department. Authentication is handled through Supabase Auth.
• Player and club records: names, date of birth, photo, squad membership, position, shirt number, external identifier, active or archived status, club name, city, branding and team structure.
• Development and training: plans, targets, measurements and dates, review history, coaching notes and authors, player commitments and buy-in ratings, activity prescriptions, schedules, attendance, session values and reasons for missed or modified sessions.
• Uploaded and linked content: photos, videos, documents and other attachments supplied by workspace members. Free-text notes, injury or illness reasons, and physical, psychological or nutrition records may contain health or other sensitive information.
• Contact requests: your name, reply email, signed-in account email and account ID, subject and message. Bug reports include reproduction steps, expected and actual behaviour, frequency and impact. Feedback includes the problem and desired outcome. If you choose to include technical details, a bug report also contains the page name, browser and window size. We do not automatically attach player records, screenshots, full page URLs or console logs to these forms.
• Connected apps: which AI apps you have connected, when, and the permissions you granted, with the sign-in records that let an app act as you (sessions and refresh tokens, handled by Supabase Auth). When a connected app records something for you, the entry is labelled with the app it came from, for example “via Claude”.
• Service and billing information: preferences, support messages you send, and technical request information such as IP address, browser information, timestamps and errors processed by hosting and authentication services. If paid billing is enabled and used, this also includes customer and subscription identifiers, chosen plan, billing interval, status and renewal dates.

Information comes from you, your club’s administrators and colleagues, your use of the service, and our authentication or payment providers. Only enter information that is necessary for an authorised coaching purpose.

Why information is used

We use account information to register and authenticate users, send account and invitation emails, provide support, manage memberships and operate subscriptions when available. Workspace information powers development plans, training records, progress charts, reports and collaboration. Technical information supports service delivery, troubleshooting and protection against misuse.

Under applicable UAE data-protection law, processing requires consent unless a permitted exception applies, such as processing necessary to perform a contract or meet a legal obligation. Where EU or UK law applies, account administration may rely on contract, legal obligations may require certain records, and security or service reliability may rely on legitimate interests balanced against individuals’ rights. Consent, where required for a particular purpose, must be obtained separately and may be withdrawn. The applicable basis for each use is described in this policy and may be updated when our practices change.

Your club is responsible for establishing the legal basis for its player records, including any additional condition needed for health information or junior-player data. Agreeing to our Terms is not blanket consent to process somebody else’s sensitive information.

Progress indicators summarise the values and ranges entered by users. The guided assistant uses application rules. Plryer does not itself send entries to a generative AI service; they reach one only through an AI app you choose to connect (see Connected AI apps). These features support human coaching decisions; they do not make recruitment, medical or eligibility decisions for you.

Who can see information

Within a club: administrators can access the club’s records and manage membership and team assignments. Coaches can access player records, targets and related coaching and training information for players in their assigned teams. Shared club resources, including its game model, activity library and staff directory, remain visible to members. Department labels and on-screen team filters do not add further confidentiality boundaries. Your name and photo may be used across clubs you belong to.

Service providers: Supabase provides authentication, database and file storage. The app is configured for Vercel hosting. Account emails are sent through Supabase’s configured email service. For paid subscriptions, Paddle processes payments and receives the billing user’s email, club name and club identifier. Plryer’s checkout does not collect or store full payment-card details. Contact forms are delivered through Postmark to support@plryer.dev. Support, privacy and legal correspondence is received and managed in Google Workspace. These email providers process the message and contact details needed to deliver and handle it.

Read the provider notices: Supabase, Vercel, Paddle, Postmark and Google Workspace. Their processing may also be governed by agreements with the Plryer operator.

AI apps you connect, and their providers, are not Plryer’s service providers. They receive information only as described in Connected AI apps.

Information may also be disclosed where legally required or necessary to address fraud, security incidents or legal claims, subject to applicable law. Plryer does not include an advertising-data sale or targeted-advertising integration in the current service.

Connected AI apps

You can connect an AI app, such as Claude or ChatGPT, to your own Plryer account through Plryer’s connector (built on a standard called the Model Context Protocol). Nothing is connected unless you do it: you sign in to Plryer, read what the app is asking for, and choose Allow. Only you can connect an app to your account.

What the app receives. A connected app acts as you, with your access and no more. When you ask it something, it can request what you can see in Plryer, which can include player, staff and club records, development plans, targets, results, notes and training, and health-related or junior-player information if your workspace holds it. Plryer sends what it asks for to the app, and so to the app’s provider (for example Anthropic for Claude or OpenAI for ChatGPT), as part of your conversation. Plryer does not send information to these providers on its own initiative; it answers requests made through the connection you set up.

What the app can do. An app can also record things for you, such as results, notes, comments, targets and training and, for administrators, changes to the game model and club structure. It cannot invite or remove people, change who has access, change billing, your account or your password, create or delete a club, or upload files. Closing or deleting something needs your explicit confirmation. What an app records is attributed to you and labelled with the app it came from. The label is there for people to read; it is not a security record.

The app and its provider are separate from Plryer. What they receive is handled under their own terms and privacy notice, including how long it is kept, whether it may be used to improve their products, and where it is processed. Plryer does not control or see that, cannot recall or delete information from their systems, and disconnecting an app does not delete what it has already received. Check the provider’s settings and plan terms before you connect. Your club decides whether its staff may use AI apps with player information, gives any notice and obtains any permission the law requires, and should not connect an app it has not approved for that information.

Mistakes and misleading text. AI apps can misread a request or make mistakes, and can be misled by text inside notes and comments. Plryer tells the app to treat that text as information and not as instructions, but this cannot be guaranteed. Check what an app has recorded.

Disconnecting. You can disconnect an app at any time under Account settings, then Connected apps. That ends its sign-in to Plryer straight away, so it can no longer read or record anything. The app keeps its own list, so also remove Plryer there. Entries it already recorded stay in the club’s workspace like any other entry. Deleting your account ends all of your connections. Requests made through a connected app are handled by the same hosting and authentication providers as the rest of the service.

Files, links and exported reports

Uploaded workspace files are stored in a private storage bucket and displayed using signed links. Newly issued links expire after 15 minutes and are renewed subject to the user’s access permissions. Older links may remain valid until their original expiry. Anyone who receives a valid signed link may be able to open the file without signing in. Removing a workspace member does not, by itself, invalidate an existing link.

Treat file links and downloaded reports as confidential. People with access can save or forward copies, and Plryer cannot recall those copies. Exported reports are generated in your browser and saved or printed at your request.

If a member adds an externally hosted image or other media, displaying it may send request information to that host. Following external links is subject to the destination’s privacy practices. Navigation URLs can contain player names or record identifiers, so treat shared page links and browser history with care.

Cookies and browser storage

Plryer uses browser storage to keep you signed in and remember preferences such as theme, sidebar state and dismissed guides. The guided assistant keeps its conversation and unfinished steps in session storage so it can resume after a reload.

The fictional demo workspace, including edits and files you add to it, is saved locally in your browser rather than to a real club’s database. Offline mode also stores workspace information locally. Resetting or leaving the demo clears or replaces its local snapshot. Do not put real confidential player information into the demo.

The application does not currently add advertising pixels or a third-party behavioural analytics SDK. Hosting, authentication and payment providers may use their own necessary storage and technical logs. Our fonts and landing-page images are served with the app.

You can clear site data through your browser. This can sign you out and erase locally stored work and preferences; it does not delete records already saved to a club’s server. On shared devices, sign out and clear local site data when appropriate.

Retention and deletion

Workspace records are kept while the club uses them and until they are deleted through the available controls or an applicable deletion request. Archiving a player, closing a plan, or removing a staff member from access does not erase their historical records.

You can request account deletion through Account settings. If other people still use a club, your account leaves it and the shared records, including notes attributed to you, can remain. A sole administrator may need to appoint another administrator first. If you are the last member, the account-deletion flow also deletes that club’s database records.

Deleting database records does not guarantee immediate removal of every uploaded file. Unreferenced media is cleaned up separately during certain saves. Deleting a club queues cleanup of its uploaded files, with retries if a provider is unavailable. Account deletion preserves files belonging to clubs that continue to operate. Contact the operator if you need help with a deletion request. Existing downloads, copies held by your club and information an AI app you connected has already received are outside Plryer’s deletion controls.

Backups, security logs and payment records may remain separately for recovery, security or applicable legal obligations. Exact provider retention periods and the operator’s retention schedule may apply; no fixed erasure deadline is represented here.

Contact form messages and replies are held in the support mailbox and the email providers’ delivery records. Deleting an app account does not automatically delete that correspondence. You can ask about or request deletion of these messages at privacy@plryer.dev, subject to any applicable retention obligation.

Security and international processing

The application uses authenticated sessions, organisation membership checks and database access policies to restrict workspace access. Administrative actions have additional role checks. No online service can guarantee absolute security; protect your credentials and take care when sharing files or inviting staff.

Our infrastructure providers may process information outside your country. The provider agreements and any required international-transfer safeguards apply to that processing. The providers of AI apps you connect may also process information outside your country, under their own terms. This policy does not promise that all data stays within a particular country.

Junior players and sensitive information

Plryer is a workspace for coaches and clubs and can contain records about junior players entered by authorised staff. A player record is separate from a user account. Accounts are restricted to adults aged 18 or older. Minors may be recorded as athletes but do not operate the app.

Clubs must provide appropriate information to players and, where relevant, parents or guardians, have authority to collect their information, and obtain any permissions required by applicable law. Be especially careful with dates of birth, photographs, health information and free-text coaching notes. Do not use general workspace notes as a confidential medical record.

Your choices and rights

Depending on the law that applies, you may have rights to access, correct, delete, restrict or object to processing of your personal information, obtain a portable copy, or withdraw consent where processing relies on it. These rights can have exceptions. You may also complain to your local data-protection authority.

You can update your profile and use the available account controls. For player information entered by a club, ask that club to handle your request; Plryer can assist the responsible club. For information handled by the operator directly, use privacy@plryer.dev. We may need to verify your identity and which records the request concerns. Do not send passwords or unnecessary health information with a request.

We will update this page when our practices change and identify the revision date. Where required, we will provide additional notice of material changes.