SERVICE PRIVACY AND SECURITY REVIEW Yenra | Reviewed October 3, 2026 Guide: https://yenra.com/safenet-2000/ Purpose: make an evidence-backed decision about a specific app/service task. Save a private copy. Use harmless sample data for tests. Do not include passwords, recovery codes, tokens or real customer information here. Record unknowns as unknowns. A completed worksheet is not a certification or a determination of legal compliance. SCOPE Service / feature / account type / exact plan: Reviewer / date / decision owner: Task and intended benefit: Information involved (categories, not actual sensitive records): People whose information is involved: Applicable organizational, contractual or jurisdictional requirements: What must be true before real data can be used: INFORMATION ROUTE Device/source -> service account -> people/integrations -> copies -> exit: Required collection and optional permissions: Purposes (feature delivery, analytics, advertising, AI training, other): Workspace admin / vendor / support / subprocessor access: Retention of originals / logs / recordings / transcripts / derived outputs: Export format / deletion process and timing / stated exceptions: CONTROL CHECKS Authentication method and recovery plan (secure references only): Sessions/devices reviewed: Connected-app scopes and whether each is necessary: Sharing defaults and permitted recipients: Recipient test account and observed access boundary: Export test: did attachments, labels and important relationships survive? Revocation test and separate deletion actions: Backend deletion evidence (provider statement, not just disappearance): Independent backup/recovery copy if needed: AI FEATURE CHECKS (when applicable) Inputs, retrieved data, outputs and connected sources: Training/improvement use terms and settings: Retention terms and settings (consider separately from training use): Human review / vendor access / administrator controls: Actions it can take and human approval points: Differences between this plan and other plans: EVIDENCE RECORD (duplicate per consequential claim) Question/requirement: Source URL / document or setting / exact plan / date checked: What the evidence actually establishes: Harmless test performed and observed result: What remains unknown: Required change or question for the provider: Owner / due date: DECISION Choose: APPROVE FOR DEFINED TASK / LIMITED PILOT / DEFER / REJECT Permitted information and activities: Required controls and unresolved restrictions: Evidence supporting the decision: Who approves expanding the scope: Next review date: Triggers: new feature, plan or terms change, new integration or people, incident, failed export, or changed information sensitivity. IF A PROBLEM OCCURS Official recovery/support address already verified: Responsible administrator or incident contact: Information and access potentially affected: Containment actions / time / evidence location: Follow the provider and organization's response process. Link revocation does not retrieve previously downloaded copies. Determine any required notifications using the facts and applicable rules. Source framework: https://www.nist.gov/privacy-framework/getting-started-0 Authentication guidance: https://pages.nist.gov/800-63-4/sp800-63b.html