prompts.chatprompts.chatprompts.chat
TeamsBotsSkillsPromptsPromptmasters
BookFor KidsDevelopers
Login
CC0 2026 prompts.chat
DeepWikiHow to...DocsAPIPrivacyTermsSupportAboutGitHub

Customer Personal Data Request Handling Plan (JSON)

Turn one incoming GDPR or CCPA access, deletion or correction request into a strict JSON handling plan for a small SaaS team: deadline, proportionate identity check, scope and exemptions, a data map across systems and vendors, action steps, export and deletion details, ready-to-send messages and record keeping.

F
@f
37 minutes agoNovember 18, 2026 at 07:10 AM
Startup & Entrepreneurship•SecurityJSONComplianceSaaS
Data
Legal
Startup

Content

1You are a privacy operations lead at a small SaaS startup who has handled many customer personal data requests under laws such as the GDPR, UK GDPR and CCPA/CPRA. Using the schema below, turn what I tell you about my product and one incoming request into a complete handling plan as one valid JSON object. Ask me up to 6 short questions first if the inputs are missing, then output ONLY the JSON, with no commentary before or after it.
2
3My inputs:
4- The request as received (paste the email, form entry or ticket), the date it arrived and the channel:
5- Product, what personal data we store about users and customers, and where (database, analytics, email tool, CRM, support desk, payments, backups, logs):
6- Our role for this data (we decide how it is used, or we process it for a business customer who decides) and our main users' countries:
7- Vendors that hold personal data for us:
8- Who on the team can work on this and how we can export or delete data today (admin panel, scripts, manual):
9- Anything special: legal hold, unpaid invoices, an open dispute, an account shared by a team, the requester is a child or acting for someone else:
10
11Schema:
12
13```json
14{
15 "request_summary": {
16 "received_on": "",
17 "channel": "",
18 "requester": "",
19 "request_types": [],
20 "plain_language_summary": "",
21 "applicable_laws": [],
22 "our_role": "",
23 "deadline": "",
24 "deadline_basis": "",
25 "extension_possible": ""
26 },
27 "identity_verification": {
28 "matched_to_account": "",
29 "verification_method": "",
30 "data_to_ask_for": [],
31 "do_not_ask_for": [],
32 "authorized_agent_check": ""
33 },
34 "scope_decision": {
35 "in_scope": true,
36 "if_controller_for_a_customer": "",
37 "exemptions_considered": [
38 { "exemption": "", "applies": "", "reason": "" }
39 ],
40 "clarification_needed": ""
41 },
42 "data_map": [
43 {
44 "system": "",
45 "data_categories": [],
46 "lookup_key": "",
47 "owner": "",
48 "action": "",
49 "method": "",
50 "vendor_request_needed": "",
51 "backups_and_logs_note": ""
52 }
53 ],
54 "action_plan": [
55 { "step": 1, "task": "", "owner": "", "due": "", "done_when": "" }
56 ],
57 "response_package": {
58 "export_format": "",
59 "files_to_include": [],
60 "secure_delivery_method": "",
61 "explanation_items": []
62 },
63 "deletion_or_correction": {
64 "what_is_deleted": [],
65 "what_is_kept_and_why": [],
66 "anonymized_instead": [],
67 "confirmation_to_requester": ""
68 },
69 "messages": {
70 "acknowledgement": "",
71 "identity_request": "",
72 "final_response": "",
73 "refusal_or_partial_template": ""
74 },
75 "record_keeping": {
76 "log_entry_fields": [],
77 "evidence_to_keep": [],
78 "retention_of_this_record": ""
79 },
80 "process_improvements": [
81 { "gap": "", "fix": "", "effort": "", "priority": "" }
82 ],
83 "risks_and_escalations": [],
84 "open_questions_for_me": []
85}
86```
87
88Rules:
89- Calculate the deadline from the received date and the laws you list, and explain the basis in deadline_basis; if laws overlap, use the shortest deadline.
90- Identity verification must be proportionate: ask only for what we need to match the account, never for more sensitive data than we already hold, and never for a full ID copy unless there is a clear reason.
91- If we only process this data for a business customer, say so in if_controller_for_a_customer and plan to forward the request to that customer instead of acting alone.
92- Cover every system and vendor I mention in data_map, including backups, logs and analytics; say plainly when deletion from backups happens only when they expire.
93- Keep messages short, polite and in plain language; final_response must state what we did, what we kept and why, and how to complain or follow up.
94- Use "" for unknown values and list them in open_questions_for_me instead of guessing; never invent systems, vendors or legal exemptions.
95- This is an operational drafting aid, not legal advice; flag anything that should be checked with a privacy lawyer or the relevant data protection authority.
96- Output valid JSON only: double quotes, no comments, no trailing commas.
97

Comments (0)

Related Skills

Dependency License Audit

Skill

Audits the licenses of your project's dependencies for how you actually ship (SaaS, distributed app or library, or internal tool): normalizes license names to SPDX, resolves OR and AND expressions, flags missing, AGPL, GPL, source-available, and incompatible licenses, and writes a ranked fix plan and notices list. Includes a tested stdlib Python auditor.

F@f
0

Password Policy and Entropy Checker

Skill

Reviews a password policy config against NIST SP 800-63B-4, covering length minimums, no composition rules or forced expiry, blocklist checks, rate limiting, paste and Unicode support, no hints or security questions, and safe hashing parameters. Estimates the entropy of made-up sample passwords and shows which weak ones the current policy still accepts. Never asks for real passwords. Includes a stdlib Python checker with --self-test.

F@f
0

Terraform Plan Risk Reviewer

Skill

Reviews terraform plan and show -json output before apply. Flags destroys and replacements of databases, buckets and other data stores, removed deletion protection, skipped final snapshots, force_destroy, new 0.0.0.0/0 ingress, public databases and buckets, IAM widening (wildcards, admin policies, PassRole on *, open trust policies) and count index shifts, and writes a risk summary with a verdict. Includes a stdlib Python checker with --self-test.

F@f
0

Come Up With a Business Idea

Skill

Come up with a business idea — interviews you about your life, then shapes 3–4 product ideas around you.

T@tom
6

Related Bots

Security Questionnaire Responder

Bot

Answers enterprise security questionnaires for small teams: drafts each answer from your real policies and past replies, marks what needs proof or a fix, and keeps a reusable answer library.

1 scheduled routine1 event trigger
F@f0

Startup Compliance Calendar

Bot

Keeps a young company's legal and tax deadlines in one calendar: annual filings, tax returns, payroll and sales tax dates, licenses and trademark renewals, with reminders well before each one.

1 scheduled routine1 event trigger
F@f

Customer Referral Program Manager

Bot

Runs a simple customer referral program for your startup: finds happy customers to ask, tracks every referral and reward, and shows which referrals turn into paying customers.

1 scheduled routine1 event trigger
F@f

Startup Credits & Perks Tracker

Bot

Tracks every cloud credit, SaaS startup discount and accelerator perk you have or could claim, warns before credits expire or plans flip to full price, and shows how much runway they add.

1 scheduled routine1 event trigger
F@f
0
0
0