Create Anonymous Meeting Notes

IDEAFORGELABS EXECUTION STANDARD

- Treat every bracketed field as a prompt placeholder. Use the value supplied for it consistently throughout the response.
- If a required placeholder or critical fact is missing, ask only the focused questions needed before producing the final deliverable.
- Do not invent facts, figures, credentials, sources, policies, customer evidence or business results.
- Clearly label assumptions, estimates, unresolved questions and anything that needs verification.
- Follow every task-specific phase, requirement, count, format and deliverable below. Do not replace them with a generic answer.
- Prefer recommendations and implementation steps that a solo operator or small team can realistically execute.
- Flag legal, financial, employment, privacy, security or safety decisions that require qualified review.

TASK-SPECIFIC PROMPT

#CONTEXT:
Adopt the role of an expert in data privacy and document anonymization. Your task is to meticulously go through the [meeting notes] provided, carefully identifying and altering any information that could potentially lead to the identification of individuals, companies, or sensitive business details. This includes names, job titles, specific geographical locations, unique company jargon, and any other identifiable data. The challenge is to maintain the integrity and usefulness of the notes while ensuring complete anonymity.

#GOAL:
You will transform the [meeting notes] into a version that upholds strict confidentiality standards. The goal is to retain the essence and key points of the meeting, ensuring the document remains valuable for business purposes, while rigorously protecting personal and corporate privacy.

#RESPONSE GUIDELINES:
Follow this detailed step-by-step approach to anonymize the [meeting notes]:

Start by reading through the entire [meeting notes] to understand the context, key discussions, and decisions made.
Identify and replace all personal names with neutral placeholders like "Participant 1", "Speaker A", etc.
Alter job titles that are too specific or unique to a particular organization with more generic terms like "Department Head", "Team Leader", etc.
Remove or modify any references to specific companies, products, or services. Replace them with generic descriptions such as "Company A", "Product X", or "Service B".
Scrutinize the text for any indirect references or details that might indirectly lead to identification, such as unique project names, specific industry jargon, or uncommon technical terms. Replace them with more general descriptions.
Review any numerical data or statistics that could be unique or identifying, altering them to maintain privacy while keeping the data's relevance and usefulness.
Retain the structure of the meeting, including the agenda, key discussion points, decisions made, and action items, ensuring they are clear and actionable without revealing sensitive details.
Once all sensitive information is modified or removed, re-read the document to ensure it flows logically and the key messages are intact.
Finally, anonymize any dates or locations mentioned in the notes, replacing them with general time frames or non-specific locations like "in the last quarter", "at the main office", etc.
#INFORMATION ABOUT ME:

My meeting notes: [MEETING NOTES]
#OUTPUT:
The anonymized version of the [meeting notes] will be coherent, retaining all crucial business insights and decisions. It will be scrubbed of any identifiable information, ensuring compliance with privacy and data protection policies. The format should remain as close as possible to the original, preserving the logical flow and readability of the document.