Privacy Policy

Effective date: 2026-06-03 Last updated: 2026-08-10

This Privacy Policy explains how By Way ofLiving ("ofLiving", "we", "us", or "our"), a company registered in the Kingdom of Saudi Arabia, collects, uses, shares, and retains personal data in connection with the ofSports application (the "Service").

This Policy is issued in accordance with the Personal Data Protection Law of the Kingdom of Saudi Arabia (PDPL) and its Implementing Regulations.

By using the Service you confirm that you have read this Policy, understand it, and consent to the processing of your personal data as described — including the transfer of your personal data outside the Kingdom of Saudi Arabia as described in Section 6.

1. Who we are and how to contact us

Data controller: By Way ofLiving Registered address: 8127 3 - Al Jamiah Dist. 34257 - 4285 Contact for privacy inquiries (data access, correction, deletion, complaints): support@ofsports.live

You may also lodge a complaint with the Saudi Data & AI Authority (SDAIA), the supervisory authority under PDPL.

2. Personal data we collect

We collect only the personal data we need to operate the Service. The categories below describe the data we collect and where it comes from.

Some data is required to create and operate your account: your email address (for authentication), date of birth (to confirm you are 18 or over), username, display name, gender, and home country and city. If you do not provide these, we cannot create or operate your account. Everything else — for example your profile photograph, biography, preferred court area, self-presentation tags, and match preferences — is optional; leaving an optional field blank only makes the related feature less tailored and never prevents you from using the core Service.

2.1 Data you provide to create and use your account

• Email address (for one-time-code authentication)

• Username, display name, biography (≤ 280 characters)

• Profile photograph (optional; stored in our Service's image storage)

• Date of birth (required at signup). It is never displayed to other Users, and we do not use it anywhere in the Service other than to confirm you are 18 or over. It is self-declared — see Section 11

• Gender (set at signup; immutable)

• Tennis skill rating (UTR) — a self-estimate on the Universal Tennis Rating scale, set by you; not a verified rating and not affiliated with Universal Tennis

• Preferred court area (optional free-text label, e.g., a neighborhood name)

• Home country and city (selected from a list during onboarding; required, and used to place you on the map so we can show you players near you)

• Geographic coordinates (latitude and longitude), used to work out how far away you are from other players. Your coordinate is one of two things: (a) the fixed centre-point of the city you select, taken from a built-in list — this is the default, and it is what we hold if you never share your device location; or (b) a reading from your device's location, which we round to three decimal places (a grid of roughly 100 metres) before saving it. On the mobile app we take reading (b) only if you grant location permission, and only while the app is open; on the web app, only when you tap "Use my location". We never read your location while the app is in the background, and we do not keep a history of where you have been — we store a single current point, overwritten each time.

  Two things about this coordinate are worth stating plainly. First, although neither value is a live position trail, both are stored with enough decimal places that Apple's App Privacy label classifies them as "Precise Location" — so you may see that term on our App Store listing. Second, the distance you see on a match card is calculated on your device, which means your stored coordinate is sent to the devices of other signed-in Users who can see your posts (see Section 3.1).

• Color theme preference (UI setting)

• Default availability preferences (gender filter, UTR skill range, maximum distance, audience, and default post duration) — used to fill fields you don't specify in a post prompt

2.2 Data you generate by using the Service

• Availability posts — including the full natural-language text of the prompt you type, the time window we extract from it, filter preferences, and any court name or court location you enter as free text
• Match requests you send or receive
• Chat messages (auto-deleted after 7 days — see Section 7)
• Match outcome reports you submit after games, including: did-you-play status, match-quality rating, sportsmanship rating about your partner, would-play-again flag, perceived play style of your partner, and an optional free-text note (≤ 1,000 characters) shared with us
• Private match notes (≤ 2,000 characters) — an optional note you can attach to any past match, for yourself. This is deliberately different from the free-text note above: a private match note is not shown to any other User, is not sent to our AI matchmaker, and is not surfaced in the moderation tools our staff use to review reports. Access rules stored in our database mean only your own account can retrieve it through the Service. As with all data we hold (Section 5), our own technical staff can in principle access the underlying database; we do not read these notes as part of operating the Service. You can edit or delete a private match note at any time from your match history, and it is deleted when the match record or your account is deleted
• Reports you submit about other Users (reason and an optional free-text details field, ≤ 1,000 characters)
• Event sign-ups — the events you sign up for, your sign-up status (confirmed, pending organizer approval, waitlisted, cancelled, or declined), and when
• Event reports you submit about an event or its organizer (reason and an optional free-text details field, ≤ 1,000 characters)
• UTR verification requests you submit to have your self-estimated rating reviewed — the evidence you provide (for example, a link to your Universal Tennis profile or other proof) or the date of an ofSports-hosted rating event you indicate you attended, an optional free-text note (≤ 1,000 characters), and a snapshot of your self-estimated UTR at the time. Our staff review these to decide whether to mark your self-estimate as verified; the verified mark is a staff check on your self-estimate, not an official Universal Tennis rating
• Test feedback you send us during the testing phase — free text (≤ 2,000 characters) about the app itself, such as a bug, something confusing, or a suggestion, together with your account identifier and the time you sent it. This is read only by our team; it is never shown to other Users. Because it is a one-way channel, you cannot retrieve, edit or withdraw a submission through the Service after sending it, and we cannot reply to it there. It is deleted when your account is deleted
• Event announcements you post to attendees, if you organize an event — including a group event you created for your own group (free text, ≤ 2,000 characters)
• Self-presentation tags (attitude / play style / intent), match-preference tags, and an optional "about me" free text (≤ 500 characters)
• Friendships (canonical pairs) and blocks (asymmetric)
• Community memberships (which communities you have joined via a join code, and when)
• Groups you create — the group name, and which of your friends you invite. If you are invited to a group, we record whether you accepted or declined and when
• Group events you create for one of your groups — the event name, an optional description, the start and end time, the number of places, and the court or venue name plus an optional street address you type. If you decline a group-event invitation, we record that you declined
• Timestamps recording when you last looked at each part of the app (each tab, and each community and group), so we can show you what is new since your last visit
• Derived ranking values (a_tag_weights, b_tag_values) computed by our AI matchmaker from your activity — see Section 3

2.3 Data we collect automatically

• IP address (incidental to all HTTP requests)
• Device and browser information (from request headers)
• Authentication session cookies (HTTP-only, secure, set by our authentication provider, required for the Service to recognize you between requests)
• Realtime connection metadata (when the app is open, your client subscribes to real-time updates; the subscription connection includes incidental network metadata)
• Push notification token (a device identifier issued by the Apple Push Notification service (APNs) and obtained through Expo; recorded only if you grant notification permission on the mobile app, and used solely to deliver push notifications to your device)
• Device location while the app is open (on the mobile app only, and only if you grant location permission: while the app is open/foregrounded, we read your device's location to keep your distance to other players current, rounding it as described in Section 2.1. We do not access your location in the background. You can revoke this permission at any time in your device settings; if you do, we simply keep using the city you selected.)
• Anti-abuse counters — when you take an action that we rate-limit (for example sending a friend request, sending a chat message, filing a report, or using the optional text-parsing feature), we record your account identifier, a label for the action, and the time, solely to enforce those limits
• App update checks (mobile app) — each time the app launches it asks our update service whether a newer version of the app's code is available. That request carries your IP address and basic device and app-version information. It happens on every launch and does not depend on any permission you grant.

2.4 Data we receive from other Users about you

• Other Users may report you, block you, or submit a match outcome that names you (always as their partner, not by your account ID being attached to the note text). If you organize an event, other Users may also report your event (which identifies you as its organizer). Reports and outcome notes are written by other Users in free text; the content is provided by them, but the fact of receiving it is part of the data we hold about you.

2.5 Data we collect from visitors who are not Users

Before launch, our website offers a form for registering interest in the Service. If you submit it, we collect: your email address; your display name (optional); whether you identify as a player, a coach, or a venue; your city (optional); an optional free-text note (≤ 500 characters); which form you submitted it through; the time of submission; and a salted, one-way hash of your IP address, used only to limit repeated submissions from the same source. We never store the IP address itself. The hash is pseudonymous, not anonymous.

Registering your interest does not create an account, and this record is separate from any account you may later open — the two are linked only by the email address you used. Because there is no account, the self-service controls in Section 8 do not apply to it; to have a registration deleted, email support@ofsports.live. This form has no age check of any kind; the 18+ requirement in Section 11 applies to creating an account.

We do not collect: payment information, phone numbers, government identifiers, health records, biometric data, racial or ethnic data, religious beliefs, political opinions, or any other special-category personal data.

The Service is for adults aged 18 and over. We do not knowingly collect personal data from anyone under 18. If you believe a minor has registered, contact support@ofsports.live.

3. How and why we use your personal data

We process your personal data for the following purposes:

We do not use your personal data for behavioral advertising, automated decision-making with legal effect, or any purpose not listed above.

3.1 Visibility to other Users

Because the Service is a matchmaking platform, some of your profile information is visible to other signed-in Users — for example when they receive a request from you, browse potential matches, or open your profile from your avatar. This visible information is: your username, display name, profile photo, biography, UTR rating (and whether it has been verified by our staff), gender (unless you leave it undisclosed), the month and year you joined, and your count of completed matches. A User you are connected with may also see whether the two of you are friends or members of the same community, and how many matches the two of you have played together. For events, the list of people who have signed up is visible only to the event's organizer, never to other attendees; your sign-up to an event and its status are visible to that event's organizer, and an organizer's announcements are shown to that event's confirmed attendees. Free-text close-out notes are never shown to other Users (Section 4.2), and Users you have blocked — or who have blocked you — cannot see your profile. For a group event, the exact venue is visible to every accepted member of that group without signing up; for other events it is shown once your sign-up is confirmed.

What other Users can retrieve, as distinct from what the app displays. The Service runs on a shared database with per-User access rules, so some profile fields can be retrieved by another signed-in User through the app's data layer even where no screen shows them. We think it is more honest to tell you what is retrievable than to describe only what is on screen. This applies to any signed-in User you have not blocked and who has not blocked you, across the whole membership rather than only for a profile you open. Coach accounts cannot read other Users' profiles at all.

Beyond the fields listed above, the following are retrievable in this way: your approximate coordinate (Section 2.1) and the country and city you selected; your preferred court area label; your friend code; the expiry date of a promotional membership, if you have one; and your default posting preferences. Your friend code deserves a specific note: another User can obtain it without you sharing it and use it to send you a friend request — which you still have to accept before anything is shared. Some fields are never readable by any client, including whether an account is an administrator and whether it has been suspended. Your date of birth is not readable by other Users and is not used anywhere in the Service other than to confirm you are 18 or over. The timestamps recording when you last opened each part of the app are likewise not readable by other Users; they are used only to show you what is new since your last visit.

Profile photographs. Your profile photo is shown to other signed-in Users as described above. Photos are not publicly addressable: each image is delivered through a short-lived link created for the signed-in User who is viewing it, which expires within a few hours. A User you have blocked, or who has blocked you, cannot obtain a new link to your photo.

Two limits are worth stating plainly rather than leaving you to assume otherwise. A link that has already been created keeps working until it expires, and an image that was recently viewed may remain briefly available from our provider's content-delivery cache. So this protects your photo going forward — it cannot withdraw a copy that someone has already obtained.

Reports and moderation records. No other User can read a report filed about you, or a UTR verification request you submit — those records have no path to another User's client at all. They are readable by our staff, as described in Sections 5 and 7.

4. AI processing — explicit disclosure

Two features of the Service involve sending your personal data to a third-party Artificial Intelligence (AI) provider, Anthropic, PBC (United States). We disclose this here because it is not obvious from using the Service:

4.1 Intent parsing

When you submit a natural-language availability prompt (for example, "tennis at Riverside tomorrow 4-6pm"), the call to Anthropic includes: the complete prompt text; your tennis skill level (UTR); your default posting preferences (Section 2.1); your device's time zone (for example "Asia/Riyadh") and the current date and time at the moment you submit, so that "tomorrow" can be resolved; and — when you are posting availability, so the parser can recognise a name you type — the names of your friends, groups, and communities (friends by display name and username). That list of names is not sent when you use the typed parser to invite one specific friend or group.

Both the text you typed and the extracted result are stored against your post, and the text you typed is shown to other Users on your post and match cards. We do not send your email address or your latitude/longitude coordinates in this call. This happens only when you choose the optional AI text parser; the default guided post builder sends nothing to Anthropic.

4.2 Matchmaker AI

Our matchmaker computes numeric ranking values that influence the order in which Users appear to one another. These values are computed by sending close-out notes (the free-text notes you and other Users write after matches) to Anthropic for analysis:

• A-side computation: the close-out notes you have written about other Users are sent to Anthropic to compute your viewer-side ranking weights.
• B-side computation: the close-out notes other Users have written about you are sent to Anthropic to compute candidate-side values stored on your profile.

The notes are sent to Anthropic only at the moment of computation. Only the resulting numeric values are stored on the relevant User profile — the notes themselves are never added to any User's profile. Other Users never see the raw notes you wrote about them, and you never see the raw notes that others wrote about you — only the influence of those notes on ranking, never the text.

Private match notes are excluded from all of this. The private note you can attach to a past match (Section 2) is never sent to Anthropic and plays no part in ranking, and it is not surfaced in our moderation tools. Only the "share with us" note on the match outcome form is used as described above.

For debugging, however, we do retain in an internal log — for about 30 days — up to the first 500 characters of the prompt we sent, which can include the text of the close-out notes used for that computation, together with your account identifier. That log is readable only by our operational staff and is used for no other purpose.

As of the effective date of this Policy, Anthropic's commercial API terms provide that customer API content is not used to train Anthropic's models by default. Anthropic's terms may change; we are not in a position to guarantee Anthropic's processing practices and we encourage you to review Anthropic's then-current commercial terms if this is material to you.

The debugging log described above applies to the matchmaker only. We do not keep a copy of your intent-parser prompts on our servers beyond the prompt text stored on your own post (Section 4.1).

5. Sharing your personal data with third parties

We share personal data only with the categories of recipients listed below, only to the extent necessary for the purposes listed in Section 3. We do not sell your personal data.

One further item, stated so that the list above is honest rather than merely complete: we have integrated but not enabled an error-monitoring service (Sentry) in both the web app and the mobile app. No error or diagnostic data is being sent to it — it is inert in every build we have shipped. If we enable it, it would receive error and crash diagnostics including device model and operating system, app version, locale and time zone, the screen involved, and a trail of recent activity in the app. We will update this Policy to identify that provider and the country in which it processes data before we enable it.

We do not share your personal data with any other third party for any other purpose.

6. Transferring your personal data outside the Kingdom of Saudi Arabia

By using the Service, you acknowledge and explicitly consent to the transfer of your personal data to, storage in, and processing in countries outside the Kingdom of Saudi Arabia, including Germany and the United States. This consent is the legal basis for the cross-border transfers described in this Section, under PDPL Article 29.

If you register your interest before launch (Section 2.5) you are not yet using the Service, so the same consent is given by submitting that form — the details you enter are stored in Germany by Supabase and pass through Vercel in the United States.

Your account data — the database, authentication records, uploaded photographs, and real-time event data — is stored in Germany, in Supabase's Frankfurt (eu-central-1) region. Supabase, Inc. is itself a United States company, so its personnel and systems in the United States may access that data in the course of operating and supporting that infrastructure.

Our other providers process personal data in the United States: Anthropic (intent-parser prompts and matchmaker close-out notes), Vercel (web request metadata), Expo / 650 Industries (push tokens, notification content, and app-update checks), Apple (push tokens and notification content), and Resend (your email address and the account emails we send you). Your personal data is therefore transferred to, stored in, and processed in both Germany and the United States.

Neither Germany nor the United States has been designated by SDAIA as providing an adequate level of personal data protection. We take reasonable steps to ensure that each provider applies appropriate technical and organizational security measures (encryption in transit, access controls, audit logging).

7. How long we keep your personal data

When you delete your account, your profile and your generated content are removed promptly from our active systems. Some records may persist briefly in backups or where their retention is required by law (for example, to defend against legal claims or to comply with anti-fraud rules).

8. Your rights under PDPL

The PDPL — together with additional commitments we make voluntarily — gives you the following rights with respect to your personal data:

• Right to be informed — the existence of this Policy fulfills this right.
• Right of access — you may ask what personal data we hold about you and how it is processed.
• Right of correction — you may correct inaccurate or incomplete personal data, either directly through the Service or by contacting us.
• Right of erasure (account deletion) — you may delete your account directly from the profile screen at any time, which removes the data described in Section 7. If you registered your interest before launch but never opened an account (Section 2.5), there is nothing to delete from the profile screen — email support@ofsports.live and we will remove that registration.
• Objecting to legitimate-interest processing (offered as a courtesy — the PDPL does not grant a general right to object to or restrict processing) — you may ask us to stop processing that relies on our legitimate interest by contacting us.
• Right to withdraw consent — you may withdraw consent at any time by deleting your account. Withdrawal does not affect the lawfulness of processing performed before withdrawal.
• A copy of your data — you may request a copy of the personal data we hold about you in a readable, structured format.
• Right to complain — you may lodge a complaint with SDAIA.

To exercise any of these rights, contact support@ofsports.live. We will respond within thirty (30) days of receiving a valid request, as required by the PDPL's Implementing Regulations.

9. Security

We apply reasonable technical and organizational measures to protect your personal data, including:

• Encryption in transit (HTTPS / TLS) for all traffic between your device and the Service;
• Row-level security in our database, so that personal data is accessible only to authorized callers (you, in most cases);
• Strict access controls for operational staff;
• Automatic deletion of chat content and operational logs on the schedules described in Section 7;
• Service-role escalations logged and used only for legitimate purposes (account deletion, ops triage, AI matchmaker recomputes).

No system is completely secure, and no transmission of data over the internet can be guaranteed to be entirely secure. We cannot guarantee absolute security of your personal data, and any transmission is at your own risk. If we become aware of a personal data breach affecting your data, we will notify you and the relevant supervisory authority as required by PDPL.

10. Cookies and similar technologies

We use a single category of cookies: authentication cookies (HTTP-only, secure, set by Supabase) that are strictly necessary for the Service to recognize you between requests. We do not use cookies for advertising or analytics.

11. Children's data

The Service is not directed at, and we do not knowingly collect personal data from, anyone under the age of eighteen (18).

When you create an account you must confirm that you are 18 or over, and you must provide a date of birth before your profile can be created; our applications and our database both reject a date of birth indicating an age under 18. This is a self-declared date of birth — we do not verify it against any identity document or third-party age-assurance service, and you should not read the words above as any form of age verification. The pre-launch interest form (Section 2.5) has no age check at all. If we become aware that a User is under 18, we will delete the account and its data.

12. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top of this Policy reflects the most recent revision. Material changes will be communicated by reasonable means (in-app notice, email to the address associated with your account). Your continued use of the Service after the effective date of a revised Policy constitutes your acceptance of the revised Policy.

13. Language

This Privacy Policy is drafted in English. If a translation into another language is provided, the English version controls in case of any conflict. (Note: a Saudi Arabic version may be issued in the future; the controlling-language clause will be reviewed at that time.)

14. Contact

For privacy inquiries, including requests to exercise the rights in Section 8, contact us at:

support@ofsports.live By Way ofLiving 8127 3 - Al Jamiah Dist. 34257 - 4285