Ting Guides · For the CEO

What should an employee AI use policy say?

The short answer

It should name the AI tools and accounts staff may use, say which kinds of data may go into them, and say who approves anything in between. Classify data as public, internal, confidential or personal, and treat anything unclassified as confidential. Add how to report a mistake, and review the vendor's data terms before approving a tool.

From this guide's worked example
See it worked through

What it depends on

  1. Which tools, and which accounts

    The same tool can treat your data differently depending on the account. OpenAI's Help Center says that for its services for individuals (Free, Plus, Pro) "we may use your content to train our models" unless the user opts out, while by default it does not use inputs or outputs from ChatGPT Business, ChatGPT Enterprise, ChatGPT Edu or its API to improve its models. A policy that only says "ChatGPT is allowed" says too little.[4]

  2. How your data is classified

    If the company has no data classification yet, write a short one for the policy: public, internal, confidential, personal. Anything without a class is treated as confidential until someone classifies it.

  3. Who answers the in-between cases

    Staff will meet cases the table doesn't cover. Name the person or channel that decides, and say how quickly they answer, or people will decide alone.

  4. Whether a ban would hold

    Blocking AI tools on company devices doesn't stop staff using them on a personal phone with a personal account, where the company has no control at all. A clear "yes, with these tools, this way" is easier to follow than a "no".

The policy text for staff

Policy text, adapt to your company

We use approved AI tools only, and only through company accounts: tool name and account type.

Before you upload a file or paste text, check its data class in the table below. If the data has no class, or contains customer data or anything sensitive, ask person or channel before you upload anything.

Never paste passwords, API keys or any other access credentials into an AI tool.

Check any AI output before you send it to a customer or base a decision on it.

If something is uploaded by mistake, report it to person or channel straight away, with the tool, the account, the type of file and the time. Do not share the data again.

Policy owner: · Data owner: · Version: · Approved by: · Next review:

A template to adapt, not an approved policy and not legal advice.

Which data may go into which AI tool?

Fill the blank cells with your own tools and approvers. A blank cell is not permission: until it is filled, treat that data as confidential.

ClassExampleAllowed inNeeds approval
PublicText already published on the company websiteApproved company toolNo
InternalAn internal marketing plan, meeting minutesCompany tool, company account only 
ConfidentialA customer contract, special pricing, the company's source code Yes: the data owner approves before it goes into any tool
PersonalNames, mobile numbers and ID numbers of customers or staff  

What should you check about the tool's provider?

Answer each line from the provider's own terms, with the link and the date you read it.

CheckWhat to confirmWhere to find it
Who and whatThe provider, the service, the plan, and who in the company owns the account.The order form or the admin console
TrainingWhether your inputs and outputs are used to train models by default, and where that is written.The provider's data-use terms or privacy policy
RetentionHow long inputs, outputs, logs and backups are kept, and what the exceptions are.The data retention section of the terms
LocationWhere the data is stored and processed, and whether the provider commits to a location in writing.The data processing agreement or the data-location page
Access at the providerWho at the provider can see the data, including subprocessors and technical support.The subprocessor list and the support access policy
Contract and transferThe contract, the data processing agreement, and whether personal data leaves the Kingdom, which Article 29 of the Personal Data Protection Law addresses; note who assessed the legal requirements.[2]The contract and the data processing agreement, read with your legal adviser
LeavingHow you delete the data, and how you remove access when an employee leaves the company.The admin console and the account-deletion terms

How do you test the policy before you approve it?

  1. Write three fictional cases from your own work

    For example: summarizing a customer contract, drafting a post from published product pages, and analysing a spreadsheet with customer names.

  2. Give them to three people from different departments

    Ask each one: is it allowed, does it need approval, and with which tool and which account?

  3. Fix every line they disagree on

    Where their answers differ, the line in the table isn't clear yet. Rewrite it until they would answer the same way.

  4. Review the final version, then approve it

    Go through it with the data owner and your legal adviser before the policy owner signs it.

What changes for companies in Saudi Arabia

General information, not legal advice. Each regulatory point summarises the official source cited beside it, as checked on the date shown under Sources; confirm how it applies to your company with your legal adviser.

  • SDAIA's guidelines ask for this policy

    SDAIA's Generative Artificial Intelligence Guidelines for the Public (version 1, May 2025), section 5.4 on classified data breaches, say that organizations "should implement policies for GenAI use that prohibits users from entering classified information into third-party tools", and "must emphasize to their workforce that existing and upcoming legal requirements remain binding when using GenAI tools."[1]

  • Personal data leaving the Kingdom

    If an approved tool processes personal data outside the Kingdom, Article 29 of the Personal Data Protection Law (Royal Decree M/19 of 9/2/1443H, amended by Royal Decree M/148 of 5/9/1444H) applies to that transfer. Its conditions include an adequate level of protection for personal data outside the Kingdom and limiting the transfer to the minimum personal data needed; the Transfer Regulation sets the exemptions from those two conditions and the safeguards they require, such as standard contractual clauses (Article 4). Settle this with your legal adviser before you approve a tool for personal data.[2][3]

Three test cases, answered with the table

ExhibitWorked example

Ting

The thirty-minute test, run on the draft group policy of the fictional Rasikh Holding. Each case is checked against the data-class table.

Data class

Public

Yes

Case

Marketing drafts a post from product pages already on the website

Tool and account

The approved company tool

Data class

Confidential

After the data owner approves

Case

A sales lead wants a summary of a customer contract

Tool and account

The approved company tool, company account

Data class

Personal

Unclear: the row is blank

Case

Finance wants to analyse a spreadsheet of customer names and mobile numbers

Tool and account

Decided by the data owner

CaseData classTool and accountAllowed?
A sales lead wants a summary of a customer contractConfidentialThe approved company tool, company accountAfter the data owner approves
Marketing drafts a post from product pages already on the websitePublicThe approved company toolYes
Finance wants to analyse a spreadsheet of customer names and mobile numbersPersonalDecided by the data ownerUnclear: the row is blank

The decisionFill the "Personal" row before approving the policy. In this run, two of the three people answered the third case differently, because that row was still blank.

Source: Illustrative example. Rasikh Holding and its companies are fictional: not a Ting client and not client data.

Questions people ask

Should we simply ban generative AI tools at work?
A ban on company devices doesn't reach personal phones and personal accounts, where you have no controls at all. Approving specific tools and accounts, with clear data rules, gives the company more control than a ban does.
Does this policy make us compliant with the Personal Data Protection Law?
No. It lowers the chance that staff put data where it shouldn't go. Your obligations under the law reach well beyond staff use of AI tools, so review them with your legal adviser.
Who should own the policy?
Name one owner, usually whoever owns data protection or information security, and write a review date in the policy. Department heads answer the in-between questions for their teams, or pass them to the owner.

What Ting does and doesn't do here

What we do

  • In Executive AI Workshops & Enablement we help your leadership team decide which AI tools to approve, for which data, and who owns the policy.
  • We run the thirty-minute test with real cases from your departments, so the unclear lines show up before the policy is signed.

Where Ting helps: Executive AI Workshops & Enablement

What we don't do

  • We don't give legal advice, and we don't certify a policy as compliant with any law or framework.
  • The workshops are decision sessions for leaders, not coding courses.

Sources

Primary sources only, each read in full on the date shown.

  1. Generative Artificial Intelligence for Public Guidelines, version 1 (May 2025), §5.4 Classified data breachesSDAIA · checked
  2. Personal Data Protection Law (Royal Decree M/19 of 9/2/1443H, amended by Royal Decree M/148 of 5/9/1444H)SDAIA · checked
  3. Regulation on Personal Data Transfer outside the Kingdom, version 2.0 (August 2024)SDAIA · checked
  4. How your data is used to improve model performanceOpenAI Help Center · checked

Ready to try this
on your own workflow?

Contact us