
Rules and ethics
Part of Business productivity software rules and ethics in the UK
Business productivity software data protection by purpose
Business productivity software data protection by purpose: map lawful bases, controller roles, risk checks, contracts and UK GDPR duties for each use.
Business productivity software data protection starts with a precise account of the processing. A privacy notice cannot compensate for an unknown event log, an undeclared support copy or an activity score whose purpose keeps changing. Map the information and decisions before configuring the service.
This guide concerns UK data protection for an organisation operating in England. The main framework is the UK GDPR and Data Protection Act 2018. Relevant UK GDPR anchors include Articles 6 (lawful basis), 13 and 14 (privacy information), 26 (joint controllers), 28 (processor terms), 30 (records of processing), 33 (breach notification) and 35 (DPIAs). Whether a duty applies depends on the organisation, processing and facts; seek advice where needed.
What to take away
- List each distinct purpose before configuring a productivity service, and choose an Article 6 lawful basis for each.
- Identify controller, processor or joint-controller roles for each purpose, based on who determines why and how data is used.
- Check privacy information, records of processing, international transfers and any need for a DPIA.
- Match the processor contract to Article 28 and the service actually provided.
- Test rights requests, deletion and breach procedures before release.
Draw the information route
Follow each category from collection to deletion. Include account details, imported records, task content, audit logs, support tickets, analytics, backups and exports. For every copy, record:
- the person or role it concerns;
- the purpose and lawful basis under review;
- who can view, change and extract it;
- suppliers and countries involved;
- retention and deletion behaviour;
- the evidence used to verify the map.
The ICO says data protection by design and by default should shape processing from the outset and throughout its lifecycle. Translate that principle into acceptance tests. A disabled account should lose access when expected; a restricted role should not see another team's records; an approved deletion should have a documented result.
Match common purposes to an Article 6 basis
Article 6 of the UK GDPR names six lawful bases: consent, contract, legal obligation, vital interests, public task and legitimate interests. Select and document a basis for each distinct purpose; the answer depends on the data, the people concerned and the organisation's role. A supplier's basis for its own processing may differ from its customer's.
- For providing a contracted service to an individual, consider contract only where the processing is necessary to perform that contract. If it is not necessary, assess whether another basis fits.
- For invoices and required records, use legal obligation only where a legal requirement applies; contract may be relevant to necessary payment administration.
- For account security and audit logs, assess legitimate interests and document the necessity and balancing exercise. Use legal obligation only where a specific legal requirement applies.
- For product analytics, assess legitimate interests and its balancing test, or use consent where it is genuinely freely given, specific and withdrawable.
- For worker monitoring or productivity scoring, assess necessity, less intrusive options and the impact on staff before relying on legitimate interests. Do not assume employee consent is freely given.
- Vital interests applies only where processing is necessary to protect someone's life. Public task applies where the processing is necessary for a task carried out in the public interest or under official authority.
These are decision prompts, not automatic assignments. Record why the selected basis fits each purpose and give people the required privacy information under Articles 13 or 14.
Assign roles purpose by purpose
Do not label the software company a processor for everything. A customer may decide why staff task data is used, while the supplier decides how its own billing or prospect records are processed. Some arrangements can involve joint or separate controllers.
The ICO explains when a controller and processor need a binding processing arrangement; Article 28 sets out the processor-contract requirements. Where two or more controllers jointly determine purposes and means, document their arrangement under Article 26. Ask a qualified reviewer to classify each purpose from the facts, then make the roles consistent across product documentation, privacy information and contracts.
Screen change before release
New integrations, worker scoring, automated recommendations and broader analytics can alter risk even when the basic account model stays the same. Use a screening record for each change. Under Article 35 of the UK GDPR, carry out a DPIA before processing likely to result in high risk. The assessment considers possible effects on people's rights and freedoms as well as technical security.
Worker data needs close attention. The ICO's guidance, “Employment practices and data protection: monitoring workers”, addresses productivity tools and asks employers to define a purpose, assess necessity, consider less intrusive methods, minimise collection and provide clear information. A vendor's default settings should allow the customer to implement that decision rather than quietly widening surveillance.
Make the contract operational
Article 28 of the UK GDPR sets out required processor-contract content, including that the processor acts only on documented instructions from the controller. The ICO's list includes instructions, confidentiality, security, sub-processors, support for rights, end-of-contract handling and audit information. Check each term against the actual service.
Test a subject-access search, correction, export and deletion in a non-production environment. Record which party performs the step and what remains in backups. If support staff can create a diagnostic copy, define its access and retention rather than treating it as invisible maintenance.
Keep a release record
Before deployment, the product owner should attach the information map, role analysis, lawful-basis advice, DPIA decision, privacy wording, supplier list, contract and technical test results. Record unresolved items and stop conditions. Repeat the review when a purpose, data category, recipient, country, monitoring setting or retention rule changes.
Before you act
- List each processing purpose and record its Article 6 lawful basis and the reason it fits.
- Check that privacy information under Article 13 or 14 covers each purpose, and keep an Article 30 record where required.
- Document controller, processor or joint-controller roles and check any Article 26 or 28 arrangement.
- Screen for a DPIA under Article 35 and verify the route for any international transfer.
- Test rights requests, deletion and the breach-reporting route before deployment.
Common questions
What should be included in the information map?
The map should cover account details, imported records, task content, audit logs, support tickets, analytics, backups and exports. For each copy, record the people concerned, purpose and lawful basis, who can view or change it, suppliers and countries, retention and deletion, and verification evidence.
When is a data protection impact assessment required?
The ICO requires a DPIA before processing that is likely to result in high risk. New integrations, worker scoring, automated recommendations and broader analytics can alter risk even if the basic account model stays the same. The assessment considers effects on people's rights and freedoms as well as technical security.
What does the processor contract need to cover?
The ICO's required content includes instructions, confidentiality, security, sub-processors, support for rights, end-of-contract handling and audit information. Check each term against the actual service. Test a subject-access search, correction, export and deletion in a non-production environment, and record what remains in backups.



