Data Classification and Handling Policy template (free, plain-language starter)

Free data classification and handling policy template for small companies: full text, the controls it supports and the decisions to make. Not legal advice or a certificat

Template · Updated · by the Controlkeep team

In short

Four sensitivity levels and what each means for storage, sharing, transfer and disposal. This free starter covers 4 controls and leaves 2 decisions for you; it is original text, not a standard’s wording, and adopting it is not a certification.

Four sensitivity levels and what each means for storage, sharing, transfer and disposal. Customers and auditors ask for it in teams deciding where data may be stored or shared; write it when you start handling customer data in several tools.

Starter policies are original templates written by Controlkeep. They are a starting point, not legal advice, and adopting them is not a certification or an audit opinion. Adapt every rule to how your company really works, and have a qualified adviser review policies with legal effect (privacy, employment, contracts).

Controls it supports

RefControlStarter framework
IS-ORG-03Asset inventoryISO 27001-style Annex A starter
IS-ORG-04Information classificationISO 27001-style Annex A starter
TC-CON-01Data is encryptedSOC 2-style common criteria starter
IS-TEC-08CryptographyISO 27001-style Annex A starter

Decisions to make before approving

  • [password manager, production database]
  • [6 months]

The policy text

Purpose

Not all information needs the same protection. This policy gives [Company] four simple levels so that everyone knows how to handle what they work with.

Scope

All information created, received or held by [Company], in any format: documents, databases, email, chat, paper and recordings.

Classification levels

LevelMeaningExamples
PublicApproved for anyone to see.Website content, published blog posts, marketing material.
InternalFor staff and trusted contractors. Limited harm if leaked.Internal procedures, meeting notes, most email.
ConfidentialCould harm the company, customers or staff if leaked.Customer data, contracts, financial records, source code, unreleased plans.
RestrictedSerious harm if leaked; only named people.Passwords and keys, payment card data, health or other special category personal data, security vulnerabilities, HR investigations.

If you are unsure, treat information as Confidential and ask [Policy Owner].

Handling rules

InternalConfidentialRestricted
Where to storeApproved company toolsApproved tools with access limited to those who need itOnly systems approved for Restricted data, e.g. [password manager, production database]
Sharing insideStaffNeed to knowNamed people only, with owner approval
Sharing outsideWith careOnly under contract or NDA, using approved sharing toolsOnly with owner and [Policy Owner] approval
In transitEncrypted connections (HTTPS)Encrypted; never as plain email attachments to personal addressesEncrypted end to end; never by chat or email
On devicesEncrypted diskEncrypted disk; no local copies unless neededNo local copies
PrintingAllowedAvoid; collect immediatelyNot allowed without approval

Labelling

Confidential and Restricted documents are labelled in the title or header where the tool allows it. Systems holding mainly one level (for example the production database) are classified as a whole in the asset inventory.

Asset inventory

[Policy Owner] keeps an inventory of systems that hold Confidential or Restricted data, with their owner and classification, and reviews it at least every [6 months].

Encryption

Confidential and Restricted data is encrypted in transit over public networks and at rest. Encryption keys are managed by the platform or a key management service and access to them is limited.

Disposal

Information is disposed of according to the Data Retention and Deletion Policy. Paper with Confidential or Restricted information is shredded; devices are wiped before reuse or disposal.

Exceptions

Exceptions to this policy must be requested in writing, approved by [Policy Owner], recorded with a reason and an end date, and reviewed when they expire.

Enforcement

Breaking this policy may lead to loss of access and to disciplinary action in line with employment contracts and local law. Contractors may have their engagement ended.

Review

[Policy Owner] owns this policy and reviews it at least every [Review Period], and after any major incident or change in how [Company] works. Questions go to [Security Contact].

Adopt it

  1. Copy the policy below, or create it from the starter library in Controlkeep, where [Company], [Policy Owner], [Security Contact] and [Review Period] are filled from a form.
  2. Decide the 2 remaining bracketed items so the rules match how you actually work.
  3. Approve it, ask staff to acknowledge it, and link it to the controls it supports so auditors can follow the trail.

Related: collecting audit evidence, policies help, Data Retention and Deletion Policy, Privacy and Data Protection Policy.

Questions and answers

How many classification levels do we need?

Three or four. More levels are rarely applied consistently.

Does adopting this data classification and handling policy make us SOC 2 or ISO 27001 compliant?

No. Policies are one part of a programme; an auditor tests whether you follow them over time. Controlkeep helps you keep the evidence, but it is not a certification or an audit opinion.

Try Controlkeep free

A working control register: owners, evidence, policies and reviews in one place, with exports your auditor can read. The Free plan needs no card; you can export or delete your data any time.