Wakeel Privacy Policy
This English text is a translation of the Arabic privacy policy. The Arabic text governs, and where the two differ, the Arabic prevails.
Effective date: 17 February 2028
This policy explains what personal data we keep in Wakeel, why, who sees it, how long it stays, and what your rights over it are under the Personal Data Protection Law of the Kingdom of Saudi Arabia and its Implementing Regulations. It is addressed to five groups: account holders in Wakeel, the people whose data workspaces enter (creators and the contacts at brands), anyone who sends a collaboration request from a creator page or from a manager workspace's page, anyone who reports a creator page listed in Wakeel's directory, and anyone who opens a document link without an account.
1. Who we are and what our role is
Wakeel is a service operated by وكيل المبدعين, under Commercial registration no. 188377373777, whose address is جدة حي المروة ١٢٦٠.
For anything about personal data: hello@usewakeel.com
Our role differs with the data:
- Your Wakeel account's data, and the technical trace of using the service: we are its controller.
- The data a workspace enters about other people (creators, the contacts at brands, and the recipients of documents), and the collaboration requests it receives from a creator page, from its own page or from a brand workspace: the workspace is the controller, because it collected this data and decided how to use it, and Wakeel is a processor that keeps and processes it on the workspace's behalf and according to its instructions.
- Listing creator pages in Wakeel's directory, and the reports sent about listed pages: we are their controller, because we decide what the directory shows and we alone deal with the reports.
2. The data we keep and where it comes from
Account holders (taken from you directly):
- The name, the email address and the password (kept encrypted with encryption that cannot be reversed, so we cannot see it).
- The date the account was created, the date the email was confirmed, the last sign-in, and the workspaces linked to your account and your role in each.
- The display language you choose (Arabic or English): kept with your account when it is created, in the language of the sign-up page, and changed from the menu or from your account settings, so that the service appears to you in it on every device you sign in from.
- Invitations: the email of whoever was invited to the workspace, who invited them, and when.
- If the workspace was created from a join link (a link sent in a creator's name or a business's to invite people to Wakeel, or the general one): which kind of link it was (a creator's, a business's, or the general link that names nobody) and the numbers that identify the sender's workspace and creator in Wakeel, where the link has them, kept with the new workspace. Wakeel's team sees it, with the sender's current name, and counts how many workspaces are created this way. A business that sent the link sees, on its home page in Wakeel, the creators who signed up through it, only while Wakeel's directory shows their page, never before. No other sender is told, and nobody receives a reward or credit for it. It is deleted with the workspace.
- If the workspace was created from a sign-up link on Wakeel's directory (on the directory itself or one of its pages): that it came from the directory, kept with the new workspace when it is created and never changed afterwards. Wakeel's team sees it with the workspace's details, and counts how many workspaces are created from the directory each day, by kind, and how many of them have a creator page listed in the directory. Nothing is stored in the browser for it. It is deleted with the workspace.
Workspace data (entered by the workspace owner):
- The workspace's name and kind, the legal name, the commercial registration or freelance document number, the VAT number, and the address.
- The bank name, the account holder's name, and the IBAN. They are printed on payment requests so that the client transfers to them directly. We keep no card details, and no money passes through Wakeel.
- The plan and the record of its changes.
- The manager workspace's address and every earlier address it had. It is a public address: the pages of the creators the workspace represents open under it.
- The manager workspace's own page, if a member sets it up: whether it is switched on, its one-line introduction and its introduction, and their English versions if entered. It opens at the workspace's address.
- The page's logo, if one is uploaded: a small square copy of it is kept in the database after its metadata (including where it was taken and the type of device) is removed, and the original file is not kept. It is deleted whenever the workspace removes it or replaces it with another.
Creators (entered by the workspace, or by the creator themself if they manage their own business):
- The name, the one-line introduction, business notes, and the Mawthooq licence number and its expiry date.
- What the creator page shows about them, if entered: the bio, the name, one-line introduction and bio in English, the specialties, the city, the content languages, the gender if chosen (it stays unset, and is not shown, unless it is chosen), and whether they make UGC.
- The availability line, if entered: a city from a fixed list, a start date if there is one, and an end date. A city only, with no venue, map or live location, and it disappears from the page after its end date.
- Social accounts: the platform, the account name, and the average views as entered; and the follower count as Wakeel reads it from the account's public profile on the platform, as the platform shows it, with the day it was read. Of the page it reads, Wakeel keeps the follower count alone, and it never signs in to the platforms.
- The list of services and their prices, each service's description and what it includes, and its name and description in English if entered.
- Audience figures as the creator reports them, if entered: the share of women, the main age band, the share of the audience in Saudi Arabia, the top city, and the date they were read. We do not check them, and the page shows them as reported by the creator.
- The creator page: its address and every earlier address it had, whether it is switched on, how it shows each service's price, and whether gift deals are welcome.
- The creator page in a creator's workspace can hand its collaboration request button over to the creator's page at a manager workspace that represents them: that page's address is kept, and the request then reaches that workspace.
- The page's photo, if one is uploaded: a small square copy of it is kept in the database after its metadata (including where it was taken and the type of device) is removed, and the original file is not kept. It is deleted whenever the workspace removes it or replaces it with another.
- The images of the page's gallery, if uploaded, nine at most: of each image, a copy whose longest side is at most 1,280 pixels and a small square copy are kept in the database after its metadata (including where it was taken and the type of device) is removed, and the original file is not kept. An image is deleted whenever the workspace removes it.
- Work examples, six at most: the link to the post, the brand's name as text, the month and year it was posted, and what is added to it if entered: a title, the brief, the creator's role, the deliverables, and the result as the creator reports it. We do not open the link or fetch anything from the post, and we do not check the result; the page shows it as reported by the creator.
- A creator's mandate to a manager workspace: which member of the workspace asked for the creator's approval and when, the name the creator typed when approving, as typed, and the time of every approval and every withdrawal of the mandate. No mobile number, IP address or browser type is recorded with it. The member sends the request for approval, or the mandate link after approval, from their own WhatsApp, and Wakeel sends the creator no message. The record stays with the creator in the workspace, and is deleted when the creator is deleted.
- A creator page's listing in Wakeel's directory, if a member of the workspace asks for it: the account chosen for the check (its platform and name), the code put in that account's bio, the time the member confirmed that the creator's name, photo and page will be public and found by search engines, the dates of the ask and of the listing, the message Wakeel's team writes when it does not list the page or removes it from the directory, and which member asked, cancelled the ask, took the page out of the directory or listed it again, and when. A creator who ticks "List my page in Wakeel's directory" when signing up gives this confirmation then: its time is kept with the creator from the sign-up, and the first ask records it. If they signed up through a brand's invitation link, that ask is sent in their name when they confirm their email address, and Wakeel's team may list the page without the code; when Wakeel trusts that brand, Wakeel lists the page itself at once, and the record says so. Otherwise Wakeel reads that account's public profile through TinyFish (named below) to look for the code: every few minutes at first, then hourly, for up to a day after the ask, and again when the account's name changes while it is listed or waiting. When the code is there, Wakeel lists the page itself, the record says the account check listed it, and Wakeel's team reviews it afterwards; when it is not there after a day, the record says the code was not found; when the profile cannot be read for a day, the ask waits for Wakeel's team, who check it by opening the profile themselves, and a listing whose account's name changed waits for a new ask. The record stays with the creator in the workspace, and is deleted when the creator is deleted.
Brands and their contacts (entered by the workspace):
- The brand's name, its field, its website and business notes.
- The contact: the name, the job title, the email address, the mobile number, and business notes.
Deals and documents:
- Deals, the payments agreed and received (the date, the method and the reference), quotations, contracts and payment requests.
- The text of the inquiry that a workspace member pastes into the deal as it came from the brand, if pasted. It stays with the deal for the workspace's members to refer to, and it does not appear in any document and is not sent to anyone.
- The text of every document as issued, with its digital fingerprint, and the recipient's name and email.
- The deal's history: which member of the workspace created it, changed its stage, marked it lost or reopened it, or recorded a payment received or a gift's arrival, and when.
Anyone who sends a collaboration request from a creator page or from a manager workspace's page (taken from you when you send the form, with no account needed):
- The brand's name, the name, the WhatsApp number, the email address if written, the services chosen, the timing, the budget, and the gift and its value if mentioned, the text of the request as written, and the time it was sent.
- An encrypted fingerprint of the IP address: the address itself is not kept, and it cannot be recovered from the fingerprint. It is used to limit the number of requests from the same sender (three an hour for each page) and to prevent automated sending.
- The request reaches the workspace that owns the page alone, and stays with it even if it decides to set it aside, so that it can contact you on WhatsApp. Wakeel does not write to the email address given in the form, and sends no message to the WhatsApp number.
- The workspace's members are told about every new request by an email that carries only the structured details: the brand's name, the name, the services chosen, the timing, the budget if mentioned, and that a gift is offered. The email carries neither the text of the request, nor the gift's description, nor the WhatsApp number, nor the email address given in the form.
- From a manager workspace's page, one form can ask several of the creators it shows at once: the workspace keeps one request for each creator chosen, each with the same details, and its members are told by one email naming them all, which carries only what the email above carries.
Brand workspaces (entered by their members):
- The company details: the brand workspace's name, its commercial registration and VAT numbers if entered, and its contact mobile, the number the creators it asks reach it on. Any of its members can change them.
- Shortlists: their names, and the creators saved to them, each with the name the directory showed and when they were saved. Only the brand workspace's members see them, and no shortlist has a public link.
- An ask, to one creator or to up to ten at once: what is needed, the timing, the budget, the gift and its value if mentioned, and the message, and with them the brand workspace's name, its commercial registration and VAT numbers if entered, its contact mobile, and the email address of the member who asked, with their name if their account has one. All of this reaches the workspace of each creator asked as a collaboration request, with an encrypted fingerprint of the IP address it was sent from as for any request, and stays there as that workspace's data. The brand workspace keeps of it only a list of the creators asked, each with the name the directory showed, when it was asked, and the ask's state.
- The state moves from sent to opened into a deal when the creator's workspace opens the request into a deal, and to quotation received when it issues a quotation on that deal. The brand workspace is not told when a request is set aside, a deal is lost, or a document is voided.
- The creator's workspace's members are told about every ask by the same email as a request from a creator page, which also says that it came from a business signed up on Wakeel. When a member opens the request into a deal, the brand workspace's details are offered to fill in the brand and its contact, and nothing is kept until the member saves; the brand they chose then keeps the identifier of the brand workspace the request came from, so that the next ask is matched to it. The brand workspace never changes the records of the creator's workspace.
- A creator's workspace can block a brand workspace from one of its requests: it keeps the brand workspace's identifier, the name its request gave, and the time. The brand workspace is not told: its later asks keep showing as sent, and nothing of them reaches that workspace.
Anyone who reports a creator page listed in the directory (taken from you when you send the form, with no account needed):
- The reason chosen (impersonation, wrong information or inappropriate content), the note if written, and the time it was sent. No name, email address or phone number is asked for or kept.
- An encrypted fingerprint of the IP address: the address itself is not kept, and it cannot be recovered from the fingerprint. It is used to limit the number of reports from the same sender (three an hour for each page) and to prevent automated sending.
- The report reaches Wakeel's team alone: the workspace that owns the page is not shown it, nor told who sent it. A report changes nothing on the page by itself: Wakeel's team looks at it and marks it dealt with, and the internal administrative log records who did so and why. The report stays with the page's creator, and is deleted when the creator is deleted.
Anyone who opens a document link without an account (taken from you when you use the page):
- Opening the page, downloading a PDF copy, a decline and its reason if written, and a report of a transfer and its reference if entered, with the time of each step, the IP address and the browser type.
- When a quotation is accepted: the name as written, the time of acceptance, and the fingerprint of the accepted quotation. No IP address or browser type is recorded with the acceptance.
- When a contract is signed: the full name as written, the acknowledgement, the email the contract was sent to, the time, the IP address, the browser type, and the fingerprint of the signed document. The same data is recorded about the workspace member who signs for the first party.
Technical data:
- Failed sign-in attempts: the email entered, the IP address, the browser type and the time. They are used to stop guessing attempts (five failed attempts stop sign-in for 15 minutes). We do not record successful sign-ins in this log.
- Server logs: the IP address, the page requested, the browser type and the time. They are used to diagnose faults and to protect the service.
- Email delivery status: if a document's email bounces or is reported as spam, this is recorded on the document with the address that bounced.
- An internal administrative log: every action Wakeel's team takes on a workspace or an account (such as changing the plan, suspending or deleting) is recorded with its reason and who carried it out.
What we do not collect:
- We use no third-party analytics or tracking tools and no advertising, and we load no fonts or files from outside servers.
- We do not ask for ID numbers or card details, and we collect no sensitive data. Please do not write sensitive data in the notes fields.
3. Why we process data, and on what basis
- Running the service for you: creating the account, confirming the email, managing the workspace, and issuing and sending documents. The basis: the agreement between us (the terms of use) and your consent when you create the account.
- Service emails: confirmation, password recovery and invitation emails, telling the workspace about a client's response to a document, and telling its owners and the member who asked whether a page was listed in the directory, not listed, or removed from it. The basis: performing the agreement. We send no marketing emails, and if we wish to in the future it will only be with a separate consent.
- Documenting documents: keeping the frozen text, the event record and the signatures with their technical trace, so that both parties have a reference to rely on. The basis: the signer's explicit consent when signing, and the legitimate interest of both parties in proving what they agreed.
- The directory: listing the creator pages whose workspaces ask for it, checking that the account belongs to the creator, and dealing with reports about listed pages. The basis: the consent given when the listing is asked for (and, for a creator a manager workspace represents, the creator's mandate, whose link names the directory), and our legitimate interest in keeping impersonation out of the directory.
- Asks from brand workspaces: delivering each ask, with the brand workspace's details, to the workspace of every creator it chose, and telling the brand workspace whether the request was opened into a deal and whether a quotation was issued on it. The basis: performing the agreement with the brand workspace (the terms of use). Once delivered, the request is the receiving workspace's data, which we process on its behalf.
- Join links: keeping, with a workspace created from a join link, which kind of link it was and whose, so that Wakeel's team can see how many people sharing brings to Wakeel. The basis: our legitimate interest in knowing whether sharing works.
- The directory as a source of sign-ups: keeping that a workspace was created from the directory, so that Wakeel's team can see whether the directory brings people to Wakeel and whether they list their pages in it. The basis: our legitimate interest in knowing whether the directory works.
- Protection and operation: stopping guessing attempts, diagnosing faults and preventing misuse. The basis: our legitimate interest in protecting the service and its users.
- The data about creators and contacts that the workspace enters: we process it on the workspace's behalf so that it can manage its deals. The lawful basis for collecting it is the responsibility of the workspace, as the controller.
- Legal obligation: if a competent authority in the Kingdom requires us to provide data, we provide the minimum the law requires.
We do not use the data for any other purpose, we do not sell it, and we make no automated decisions that affect you.
Creating an account requires the name and the email address, and without them the service cannot be provided. The rest of the data is optional, but some features depend on it: no payment request is issued without an IBAN, and no tax is calculated without a VAT number.
4. Who sees the data
- The workspace's members: every member sees all of their workspace's data, including the collaboration requests that came from its page or from brand workspaces. No workspace sees another workspace's data.
- Anyone who opens a creator page that is switched on: they see what it shows, which is the photo, the name, the one-line introduction and the bio, the specialties, the city, the content languages, the gender if chosen and whether they make UGC, the availability line until its end date, the accounts with their follower counts (in ranges, and exact to the signed-in members of brand workspaces) and average views, the services with their descriptions and what each includes (and their prices where the workspace chose to show them), the gallery's images, the work examples and their results, the audience figures, the Mawthooq licence number while the licence is valid, and the name of the manager workspace that represents the creator, if there is one. Unless the page is listed in Wakeel's directory, it appears in no search, and in no list but the page of the manager workspace that represents the creator while that page is switched on, and it opens only from its link or from that page. Who opened it is recorded only in the server logs.
- Anyone, while a creator page is listed in Wakeel's directory and switched on: the page can be found in the directory and through search engines (such as Google), in Arabic and in English, and the directory shows a card of it: the photo, the name, the one-line introduction, the name of the manager workspace that represents the creator if there is one, the city and the specialties, each account's follower count (in ranges, and exact to the signed-in members of brand workspaces), the lowest price the page shows, whether gift deals are welcome and whether they make UGC, and the availability line until its end date. The card shows nothing the page does not. A page is listed only after a member of the workspace asks for it and confirms that the creator's name, photo and page will be public and found by search engines, and then only by Wakeel itself, when it finds the code in the account's bio or when the creator signed up through the invitation of a brand Wakeel trusts, or by Wakeel's team after checking the account. Anyone who opens a listed page can report it to Wakeel's team.
- Anyone who opens a manager workspace's page that is switched on: they see the workspace's name, its logo, its one-line introduction and its introduction, and a card of every creator it represents whose page is open, showing what the directory's card shows, each marked if the creator's page is listed in the directory. The page can be found through search engines only while at least one of those creators is listed in the directory; otherwise it opens only from its link. A creator leaves it as soon as their page closes, including when the mandate is withdrawn.
- Anyone a join link is sent to: they see the name the link was made in, as it was then (a creator's name as their page shows it, even when the manager workspace that represents the creator sends it, or a business's workspace name), and the link's page shows nothing else about the sender. The link itself carries that name, its language, its kind and the numbers above, readable by whoever has it: it is signed, so it cannot be changed, but it is not encrypted. Opening the link stores nothing in the browser and is recorded only in the server logs, and the link does not expire.
- The members of a brand workspace: its shortlists and its list of asks, and of each creator's workspace only whether their request was opened into a deal and whether a quotation was issued on it.
- A document's recipient: sees the document addressed to them and the sender's details in it (including the legal name, the bank account details on a payment request, and the Mawthooq licence).
- A document's sender: sees the document's record, including the client's response, its time and the technical trace.
- Wakeel's team: for support and operation only (checking directory listings and dealing with reports included), through an internal read-only console protected by two-step verification. Any administrative change is made through a defined action that is recorded with its reason.
- The competent authorities in the Kingdom, whenever the law requires us.
To run the service we rely on three providers who process data on our behalf:
- Railway (an American company): hosting the application, the database and the backups. All the data in this policy is kept with it.
- Postmark (part of the American company ActiveCampaign): sending email. The recipient's name and email, the text of the message and the document link pass through it, it keeps a delivery record under its own policy, and it tells us about bounced emails.
- TinyFish (Tiny Fish, Inc., an American company): reading the public profile of an account a workspace adds as the creator's own, to read its follower count (on Instagram, TikTok, Snapchat and X, where the profile shows it) and, while a page's listing is checked, to look for the code in its bio. It is sent the address of that public profile and nothing else: for the follower count, when the account is added or its name changes and once a week while the page is listed, each time tried again for up to a day while the profile cannot be read; for the code, while a page's listing in the directory is checked, and a follower count that read finds is kept as the account's. It returns the page as anyone sees it without signing in.
We share the data with no other party. If a workspace member shares a document link, a mandate link, a creator page's share image or a join link through another app, such as WhatsApp, this is done from their own device and account, and Wakeel's servers send nothing to that app.
5. Transferring data outside the Kingdom
The hosting provider has no data centre inside the Kingdom at present, so the data is kept and processed outside it:
- Hosting and the database: أوروبا الغربية.
- Email: the United States of America (Postmark).
- Reading accounts' public profiles: the United States of America (TinyFish).
We keep the transfer to the minimum needed to run the service, and we rely in it on contractual data protection commitments with each provider (its data processing agreement). If suitable hosting becomes available inside the Kingdom, we will reconsider this.
6. Retention and deletion
- The account's and the workspace's data stay as long as the account exists. We do not delete inactive workspaces automatically at present.
- Issued documents, their records and their signatures stay as long as the workspace does, because they are a reference for both parties. A document is not edited after it is issued, so no particular data is deleted from it; it is deleted with its workspace.
- Document links sent to clients expire 90 days after they are created, and the sender can send a new link.
- A page leaves Wakeel's directory at once when a member of the workspace takes it out from the page's settings, switches the page off or deletes the creator, when the account chosen for the check is removed (a new ask is then needed) or changed (Wakeel then looks for the code on the changed account, as for an ask, and lists the page again when it finds it; otherwise a new ask is needed), when a creator a manager workspace represents withdraws the mandate (approving it again brings the page back), when the workspace is suspended, or when Wakeel's team removes it. From then on the page asks search engines not to index it, but search engines, and the copies others keep, may take time to forget it, which is outside our control. Taking a page out of the directory does not close it: it stays open from its link unless it is switched off, the mandate is withdrawn or the workspace is suspended.
- An ask stays with the workspace of each creator who received it, as its collaboration request, even if the brand workspace that sent it is deleted. A brand workspace's shortlists and its list of asks are deleted with it. A block stays with the workspace that made it until it is lifted or that workspace is deleted.
- There is no self-service deletion or export tool at present. The request is sent to hello@usewakeel.com, and when the workspace owner asks for the workspace to be deleted, we delete it with everything in it (creators, brands, contacts, deals, documents, signatures and records) within 30 days, and with it the accounts of the members who belong to no other workspace.
- After the deletion, one entry remains in our internal administrative log saying that the deletion was made: the workspace's name, its members' emails and roles, the number of records deleted, and the reason for the deletion and who carried it out. We keep it to prove that we carried out the request.
- Backups keep deleted data for at most 30 days, after which it disappears from them automatically.
- The log of failed sign-in attempts and the server logs are short-lived, and are used only for protection and diagnosis.
7. How we protect the data
- The separation of workspaces is enforced at the level of the database itself, not only at the level of the application: every query is limited to the current workspace, so a workspace cannot read another's data even if a programming error happens in the application. A brand workspace's ask enters the workspace of each creator asked only to write the request there, and only its state comes back. The directory's cards are readable outside their workspace, and of personal data they hold only what the open, listed page already shows.
- The connection to the site is always encrypted (HTTPS), and email is handed to the sending provider over an encrypted connection.
- Passwords are kept encrypted with encryption that cannot be reversed, and sign-in stops for a while after five failed attempts.
- After it is issued, a document is frozen and its digital fingerprint (SHA-256) is computed, so any change to it shows. A document's event record is only ever added to, never edited.
- Document links are digitally signed, so they cannot be guessed, and they stop working when the workspace is suspended.
- Wakeel's team has read-only access to workspaces' data, with two-step verification, and every administrative action is recorded in a log that cannot be edited.
No service is completely secure. If a leak of personal data happens that could harm the people it concerns, we inform the Saudi Data and Artificial Intelligence Authority within 72 hours of learning of it, and inform those affected without delay, as the law requires.
8. Your rights and how to exercise them
The Personal Data Protection Law gives you the right to:
- Be informed: to be told the reasons and purposes for which your data is collected, which is what this policy does.
- Access: to know what we keep about you.
- Obtain a copy of your data in a clear and readable format.
- Correction: to correct, complete or update your data. The workspace's, creators' and contacts' data is edited directly from inside the account, while the account holder's name and email are, for now, changed by writing to us.
- Destruction: to ask for your data to be deleted when it is no longer needed.
- Withdraw consent at any time, wherever consent is the basis, without affecting what was done before the withdrawal.
To exercise any right: an email to hello@usewakeel.com from the email address linked to the data, stating the request. We may ask for proof that the request comes from the person the data is about. We answer within 30 days, and if the request needs longer we tell you the reason before that time runs out. We charge nothing for this.
If your data was entered by a workspace (as a contact at a brand, a creator, or a document's recipient):
- The workspace is the controller of this data, and the quickest way is to address it directly. You can also write to us, and we will pass the request on to the workspace and help it carry it out.
- A creator whose page is listed in the directory can ask the workspace to take it out, which is immediate, or, if a manager workspace represents them, withdraw the mandate from its link, which takes the page out at once. Writing to us works too, and we can remove the page from the directory ourselves.
- Issued documents, signatures and their records are a reference for both parties in a business dealing, and keeping them may remain justified as long as they are needed as proof. In that case we explain the reason in our answer.
9. Cookies
We use only the cookies the service needs to work, so no consent window appears:
- sessionid: keeps your account signed in. It is created when you sign in, and ends after two weeks or when you sign out.
- csrftoken: protects forms against forged requests. It is created when you open the site's pages, including document pages, and carries no personal data. It lasts a year.
- django_language: keeps the language you chose (Arabic or English), so that the pages before you sign in (sign-in, sign-up, email confirmation, password reset, and error pages while you are not signed in) appear in it. It is created when you choose a language, when you sign in, and when you open the sign-in or sign-up page from an English page, carries no personal data, and ends when you close the browser.
We use no cookies for analytics, advertising or tracking. The browser on your device also keeps one display preference (showing or hiding closed deals), which is not sent to us.
10. Children and anyone under 18
Wakeel is a business service meant for people aged 18 or over, and we do not accept accounts from anyone younger. If a workspace enters the details of a creator under 18, obtaining their guardian's consent is the workspace's responsibility. If we learn of an account created by someone under 18, we delete it.
11. Changes to this policy
We may update this policy as the service develops, and the effective date always appears at the top of the page. For any material change, such as adding a new service provider or a new purpose of processing, we notify account holders by email at least 14 days before it takes effect.
12. Contact and complaints
For any question, request or complaint about your data: hello@usewakeel.com
We ask you to give us the chance to deal with the complaint first. In any case, you may file a complaint with the Saudi Data and Artificial Intelligence Authority (SDAIA), as the competent authority, through the National Data Governance Platform, within 90 days of the breach happening or of your learning of it.