Privacy Policy
This English text is a translation provided for convenience. The Arabic text is the official version and prevails in case of any difference. Read the Arabic version
1. Who We Are and Scope of This Policy
This policy explains the personal data Suffarah processes when you use the website or its mobile app, why we process it, who we share it with, how long we keep it, and your rights over it. It has been prepared in accordance with the Personal Data Protection Law of the Kingdom of Saudi Arabia and its implementing regulations.
The Service is currently operated under the name "Suffarah" without a registered legal entity, and Suffarah is the controller responsible for processing your data. For anything concerning your data, contact us at [email protected]. If the Service and its data are transferred to a legal entity in the future, we will notify you on the Service before the transfer.
This policy should be read together with the Terms of Use and the Cookie Policy.
2. Quick Summary
- You can browse the entire Service without an account and without providing any personal data.
- We use no visitor analytics tools and no advertising or tracking cookies, and we do not sell your data.
- We collect the minimum needed: account data if you create one, notification data if you enable notifications, and security data to protect the Service. The mobile app registers its install on its first start to protect the Service (an install key, the platform type, the language, the time zone and the app version), as set out in section 3.5.
- Our servers are in the United States, so your data is stored outside the Kingdom. Section 7 explains this and its safeguards.
- You can delete your account yourself at any time, and request a copy of your data or its correction by email.
3. Data We Collect
3.1 Account data (only when you create an account)
- Your email address and display name.
- Your password: we do not store it; we store a one-way Argon2id hash from which the password cannot be recovered.
- Your preferences: language, time zone, theme (light, dark or automatic), the favourites order on the matches page, and match event sounds.
- The account creation date, and the version of the Terms and Policy you accepted with the date of your acceptance.
- Favourites: the teams, competitions, players and matches you choose to follow.
- In-site notifications (the bell): such as goals by your favourite teams and the outcome of competition requests.
3.2 Data you send when using optional features
- Requesting a competition: the requested competition and your language, linked to your account if you are signed in. If you are a visitor, instead of your address we store an encrypted fingerprint derived from it with a secret key, to prevent duplicate requests, and we erase it after 30 days.
- Activating a competition at once: if you activate a competition from the competition catalog, we store which competition you activated and when, linked to your account, to count the daily activation limit. If you delete your account, the activation record stays with no link to you.
- Your messages to us by email: their content and your email address, used only to reply to you.
3.3 Security and protection data
- Last sign-in: we store the time of your last sign-in and the full IP address you signed in from. It is replaced at each new sign-in, kept as long as the account exists, and deleted with it.
- Failed sign-in attempts: a counter on your account, and a temporary lock of the account when they repeat.
- Request limits: to prevent abuse (such as password guessing and form flooding) we keep temporary counters linked to a fingerprint derived from your address, not the address itself, erased within one hour at most.
- Captcha: on the sign-up page and the two visitor competition request pages we use an arithmetic question and Google's reCAPTCHA service. During verification we send Google the token the service generated in your browser and your IP address. Google collects device and interaction information in your browser according to its own policy.
- Session: when you visit the website we create a session for you in a file on the server, to protect forms against forged requests and to keep you signed in if you sign in. It expires two hours after your last activity, and its file is deleted in the daily clean-up.
3.4 Two-step verification (optional)
- When enabled, we store the authenticator app's secret key encrypted, and the number of the last code used to prevent its reuse.
- During setup, the key stays in your session for 15 minutes at most until you confirm it.
- The Service does not currently provide backup recovery codes, so if you lose your authenticator device, write to us from your account's email address.
3.5 Mobile app
The Suffarah app for Android is available from the Get the app page on the website, and from Google Play once it is published there.
- When you sign in from the app we issue a short-lived access token (15 minutes) and a refresh token (30 days), storing only their hashes, not the tokens themselves, together with the device name the app sends, if any.
Mobile app: on its first start, the app registers its install, even without an account and before notifications are enabled: a random install key issued by our server and kept in the app (the server stores only its hash), the platform type, your language, your time zone and the app version. We use it to protect the Service and to count request limits per install (such as account creation and competition requests), and no notification is sent to it until you enable them. If you sign in from the app, the install is linked to your account, and it is unlinked when you sign out. It is deleted under the same rule as notification devices (section 8), and deleted immediately when you delete your account if it is linked to it (section 9). Uninstalling the app does not notify our server, so the install record remains until it is deleted automatically under that rule.
3.6 Push notifications (optional)
They are enabled only after you press the notifications or follow button yourself and allow them in your browser or in the app. Once enabled, we store:
- The notification token issued for your browser or device by Google's Firebase service, the platform type, your language, your time zone, and the app version if it comes from the app.
- What you follow (teams or matches), the notification types you chose, and your quiet hours.
- A random device key in a cookie in your browser; the server stores only its hash.
- A log of the notifications sent to your device and their text, to prevent duplicates and investigate failures.
- If you are signed in, we link the device to your account and add your favourite teams and matches to what it follows.
You can enable notifications without an account.
3.7 Technical data
- Your requests pass through the Cloudflare network for protection and faster browsing, which processes your IP address and technical request data (such as browser type) for that purpose.
- The hosting server keeps standard technical access logs (including the IP address, requested page, request time and browser type), deleted according to the server's settings.
- When you search on the website or in the app, your search text is sent to our server only to run the search. We do not store it in our database, link it to your account or your device, or build a search history from it. Because it is part of the request address, it appears in the access logs of the hosting server and Cloudflare mentioned above, and is deleted with them under their retention period (section 8).
- The server error logs written by our software do not include your IP address or email, and we delete them after 90 days.
3.8 What we do not collect
- We use no tool to analyse or measure visits, and no advertising or tracking cookies.
- We do not ask for your date of birth, mobile number or geographic location.
- We store no payment data, as the Service is free.
4. Purposes of Processing
- Providing the Service: creating your account, saving your preferences and favourites, and showing times in your time zone.
- Sending the notifications you requested, and emails necessary for your account (such as the account activation link, valid for 24 hours, and the password reset link, valid for 60 minutes).
- Protecting accounts and the Service: preventing automated sign-ups, password guessing and abuse.
- Replying to your messages and requests.
- Meeting legal obligations.
We do not use your data for marketing or for automated decisions that affect you.
5. Legal Bases for Processing
- Consent: when creating an account, enabling push notifications, and two-step verification. You can withdraw it at any time (section 10).
- Necessity to provide the service you requested: such as keeping your account, favourites and session.
- Legitimate interest: protecting the Service and its users (request limits, captcha, account lockout, storing the last sign-in address, and technical logs), without prejudice to your rights.
- Legal obligation: when requested by a competent authority under the law.
7. Transfer of Data Outside the Kingdom
All user data is stored and processed outside the Kingdom of Saudi Arabia:
- The server holding the database is with PrivateSystems Networks in Atlanta, United States of America.
- Backups are with Cloudflare, and your requests pass through its global network.
- Google's reCAPTCHA, Firebase and YouTube services process the data listed in section 6 on their servers outside the Kingdom (YouTube only if you press play on a highlight).
We rely for this transfer on your consent when creating an account or enabling notifications, and on its necessity to provide the service you requested, limited to the minimum data. We apply the following safeguards:
- Encryption of all connections between your browser and the Service, and between the Service and external parties.
- Passwords stored as irreversible hashes, and two-step verification keys and operating secrets stored encrypted.
- Backups in Cloudflare storage, which encrypts stored data as stated by its provider.
- The administration panel is protected by three layers: a Cloudflare access gateway, a password, and mandatory two-step verification. Server access is limited to the operator and protected by a firewall.
- We keep only the data that is needed, and delete it according to the periods in section 8.
We do not claim these safeguards prevent every risk; section 11 explains what we do if an incident occurs.
8. Data Retention
| Data | Retention period |
|---|---|
| Account data, favourites and last sign-in address | As long as the account exists; deleted immediately when it is deleted |
| In-site notifications | 90 days |
| Password reset link | 60 minutes |
| Account activation link | 24 hours |
| Account not activated from the email link | 7 days from sign-up, then deleted with all its data |
| App sign-in tokens | 15 minutes for the access token and 30 days for the refresh token; deleted seven days after expiry |
| Session on the server | Expires two hours after the last activity; its file is deleted in the daily clean-up |
| Push notification devices | Until you turn notifications off from their settings page, when the device is deleted immediately. If the token becomes invalid (such as when permission is revoked in the browser), the device is disabled and deleted after 60 days. If the device receives no successful notification and you do not visit the website from it (or open the app) for a full year, it is deleted automatically with its follows |
| Log of sent push notifications | 30 days |
| Competition activation record | As long as your account exists; when you delete it, the record stays with no link to you |
| Visitor fingerprint on competition requests | 30 days, then erased; the request remains with no link to you |
| Request limit counters | One hour at most |
| Log of sent emails (address masked: first letter and domain) | 90 days |
| Server error logs (written by our software) | 90 days |
| Administration action log | One year |
| Hosting server and Cloudflare access logs | According to the server's and provider's settings |
| Backups (a daily full account backup with Cloudflare, and a daily database backup on the server itself) | 7 days each, then replaced |
9. Account Deletion
You can delete your account yourself; the methods are explained on the Delete Account page. On deletion:
- Deleted immediately: the account and all its data, favourites, in-site notifications, competition requests, app sign-in tokens, password reset links, and the devices linked to your account with their notification subscriptions.
- Kept temporarily: backups for up to 7 days, the masked email log for up to 90 days, an entry with your account number (without your email) in the administration action log if an administrator took action on your account for up to one year, and request limit counters for up to one hour.
- Kept with no link to you: aggregate counts, such as the number of requests for each competition.
If you enabled notifications in a browser without signing in, turn them off from their settings page in that browser so the device is deleted.
10. Your Rights
The Personal Data Protection Law grants you the following rights:
- Right to be informed: of the data we collect and its purposes, which this policy fulfils.
- Right of access and to obtain a copy: write to us at [email protected] from the email address registered on your account, and we will send you a copy of your data within 30 days.
- Right to correction: change your display name, language, time zone, theme and password in your account settings. To change your email address, write to us, as the Service does not currently allow changing it from the settings.
- Right to destruction (deletion): delete your account yourself, or request it by email.
- Right to withdraw consent: turn off push notifications from their settings page, disable two-step verification, or delete your account. Withdrawal does not affect processing carried out before it.
We respond to rights requests within 30 days, and may ask you to prove ownership of the account (such as writing from its email address) before acting on the request. If you are not satisfied with our response, you may file a complaint with the Saudi Data and Artificial Intelligence Authority (SDAIA).
11. Data Security and Incidents
We apply reasonable security measures, including: encrypted connections, password hashing, encryption of two-step verification keys, protection of forms against forged requests, request limits, account lockout after repeated failed attempts, and restricted access to the administration panel. However, no method of transmission or storage is completely secure, and we cannot guarantee absolute data security.
If an incident of leakage or unauthorised access to personal data occurs:
- We will notify the Saudi Data and Artificial Intelligence Authority (SDAIA) within 72 hours of becoming aware of the incident.
- We will notify affected users without undue delay where the incident may harm them, explaining what happened and what they can do.
- We will take the necessary steps to contain the incident and prevent its recurrence.
12. Children
No one under 13 may create an account, we do not knowingly collect their data, and if we learn of such an account we will delete it. If the user is under the legal age of majority, their use must be with the knowledge and consent of their guardian. A guardian may write to us to request deletion of the account of a person in their care.
14. Future Advertising
The Service does not currently show any advertising. If we show direct advertising in the future, we will not share your data with advertisers. Before adding any advertising that involves tracking or external ad networks, we will update this policy and ask for your consent.
15. Changes to This Policy
The version number and effective date of this policy appear at the top of the page. For any material change (such as collecting new data, adding a party we share data with, or changing the purposes of processing), we will ask for your consent the next time you sign in to your account. Non-material changes take effect on publication with an updated version number and date.
16. Contact
For any question or request concerning your data, write to us at [email protected].
For the limits of the data shown and Suffarah's independence from any official body, see the Disclaimer.