DOCUMENT RETENTION POLICY V8
DOCUMENT RETENTION POLICY
VERSION 8.0 | MARCH 2026
GROOVY COMPANY, INC. DBA OTCM PROTOCOL
Wyoming Corporation | CIK: 1499275 | OTC: GROO | 12 Daniel Rd East, Fairfield, NJ 07004
SEC Category 1 Model B | Release No. 33-11412 | BOARD APPROVED | CONFIDENTIAL
|
|
|---|---|
|
Field |
Value |
|
Document ID |
OTCM-POL-DRP-001 |
|
Version |
|
|
Effective Date |
|
|
|
|
Approved By |
Board of Directors |
|
Legal Entity |
Groovy Company, Inc. dba OTCM Protocol |
|
Governing Law |
Federal Securities Law, Wyoming Business Corporation Act, and New Jersey State Law |
π TABLE OF CONTENTS
- Article I: Purpose and Scope
Article II: DefinitionsArticle III: Document Retention ScheduleArticle IV: Blockchain and Digital Asset RecordsArticle V: Electronic Records ManagementArticle VI: Litigation Hold ProceduresArticle VII: Document DestructionArticle VIII: ResponsibilitiesArticle IX: Compliance and EnforcementArticle X: Administration
π― ARTICLE I: PURPOSE AND SCOPE
Section 1.1 β Purpose
This Document Retention Policy (the "Policy"βPolicyβ) establishes standards and procedures for the retention, preservation, and destruction of Company records. The Policy is designed to:
|
|
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
Section 1.2 β Regulatory Framework
|
Section 1.3 β ScopeThis Policy applies to all records created, received, or maintained by the Company,
|
|
|
|
|
| |
|---|---|---|---|---|
Retention |
Notes |
|||
|
Articles of Incorporation |
Permanent |
Including all amendments |
||
|
Bylaws |
|
|
| Including all amendments |
|
Board / Committee Minutes |
|
|
| All board and committee meetings |
|
||||
|
Shareholder Meeting Minutes |
Permanent |
Annual and special meetings | ||
|
||||
|
Stock Ledger |
Permanent |
All ownership records |
||
|
Board/Committee Resolutions |
|
All formal resolutions including Common B authorizations |
||
|
|
|
| ||
|
OTCM Protocol assumed name certificates |
|||
|
|
|
| ||
Annual Reports to State |
Permanent |
All jurisdictions | ||
|
Board/Committee Resolutions
Permanent
All formal resolutions
π
Shareholder Consents
Permanent
Written consents in lieu of meeting
Section 3.2 β Financial Records
|
|
|
|
| |
|---|---|---|---|---|
Retention |
Notes |
|||
|
Annual Financial Statements |
Permanent |
Audited statements | ||
|
||||
|
Quarterly Financial Statements |
7 years |
Internal and external | ||
|
||||
|
General Ledger |
Permanent |
All entries |
||
|
AP/AR Records |
| 7 years |
Invoices, |
|
|
Bank Statements / Reconciliations |
| 7 years |
| |
|
||||
|
|
Permanent / 7 years |
| ||
| workpapers 7 years |
| ||
|
Expense Reports
7 years
Employee reimbursements
π
Budgets
5 years
Annual budgets
π
Audit Reports
Permanent
Internal and external
π
Audit Workpapers
7 years
Per SOX requirements
Section 3.3 β Tax Records
|
|
|
|
| |
|---|---|---|---|---|
Retention |
Notes |
|||
|
Income Tax Returns |
Permanent |
Federal and state | ||
|
||||
|
Tax Workpapers |
7 years |
Supporting documentation | ||
|
||||
|
Payroll Tax Returns / W-2s |
7 years |
All filings | ||
|
||||
|
|
|
| ||
1099 Forms Issued |
7 years |
Information returns | ||
|
||||
|
|
|
| ||
Property Tax |
|
| ||
|
|
|
|
Section 3.4 β Employment Records
|
|
|
|
| |
|---|---|---|---|---|
|
Notes |
|||
|
Personnel Files |
7 years after termination |
General employment records | ||
|
||||
|
I-9 Forms |
3 years after hire or 1 year after termination (longer) |
Immigration verification | ||
|
||||
|
Payroll Records |
7 years |
Wages, deductions, hours | ||
|
||||
|
Benefits Records |
7 years after plan termination |
ERISA requirement |
||
|
Background Checks |
| 5 years |
| |
|
|
||||
|
|
|
| ||
| 5 years |
| ||
|
|
| ||
|
|
| ||
|
| Injury/illness logs |
Section 3.5 β Contracts and Legal
|
|
|
|
| |
|---|---|---|---|---|
Retention |
Notes |
|||
|
Executed Contracts |
10 years after expiration |
All material contracts | ||
|
||||
|
Real Estate Documents |
Permanent |
Deeds, leases, mortgages | ||
|
||||
|
Intellectual Property |
Permanent |
Patents, trademarks, | ||
|
||||
|
Litigation Files |
10 years after |
All legal matters |
||
|
NDAs / Confidentiality |
|
|
| |
| 10 years after expiration |
| ||
|
||||
|
Insurance Policies / Claims |
|
| ||
|
| permanent; claims 10 years after settlement |
| |
|
||||
|
|
|
| ||
Legal Opinions |
Permanent |
|
Section 3.6 β Securities and Regulatory Records
|
|
|
|
| |
|---|---|---|---|---|
Retention |
Notes |
|||
|
SEC Filings (10-K, 10-Q, 8-K) |
Permanent |
All forms filed | ||
|
||||
|
Form D Filings |
Permanent |
Reg D exemption notices | ||
|
||||
|
Private Placement Memoranda |
|
| ||
|
PPM V8 and all prior versions |
|||
|
Subscription Agreements |
Permanent |
| ||
|
||||
|
Accredited Investor Verification |
7 years |
| ||
|
||||
|
Cap Table Records |
Permanent |
All ownership records | ||
|
||||
|
|
|
| ||
Insider Trading Records |
7 years |
Pre-clearance, | ||
|
||||
|
Related Party Transaction Records |
7 years |
Approvals, | ||
|
||||
|
Section 16 Filings |
Permanent |
Forms 3, 4, 5 |
||
|
SEC Crypto Task Force Correspondence |
Permanent |
All regulatory engagement materials |
||
|
No-Action Letter Materials |
Permanent |
Consolidated no-action letter and all drafts |
π ARTICLEArticle IV: BLOCKCHAINBlockchain ANDand DIGITALDigital ASSETAsset RECORDSRecords
Section 4.1 β Immutable Blockchain Records
β οΈIMPORTANT:Blockchain records are inherently immutable and cannot be deleted. This Policy addressestheretention of related off-chain records and metadata.
Section 4.1 β Immutable Blockchain Records
|
|
|
|
| |
|---|---|---|---|---|
Retention |
Notes |
|||
|
Smart Contract Source Code |
Permanent |
All deployed Transfer Hook and CEDEX contracts | ||
|
||||
|
Smart Contract Audits |
Permanent |
| ||
|
||||
|
Deployment Records |
Permanent |
Transaction | ||
|
||||
|
Contract Upgrade History |
Permanent |
All Transfer Hook and CEDEX modifications |
Section 4.2 β ST22 SecurityDigital TokenSecurities Records
|
|
|
|
| |
|---|---|---|---|---|
Retention |
Notes |
|||
|
Custody Agreements |
Permanent |
Empire Stock Transfer tripartite agreements | ||
|
||||
|
Common B / Series |
|
| ||
|
Certificates of Designation, board resolutions, CUSIP assignments |
|||
|
Token Minting Records |
Permanent |
Issuance | ||
|
||||
|
Transfer Hook Configurations |
Permanent |
| ||
|
||||
|
|
7 years |
| ||
|
||||
|
Token Holder Registry |
Permanent |
Off-chain holder information | ||
|
||||
|
Transaction Logs |
7 years |
Off-chain transaction records and analytics |
Section 4.3 β OTCM Utility Token Records
|
|
|
Notes | |||
|
| |||||
|
|
|
|
| ||
|
|||||
|
|
Permanent |
| |||
|
|||||
|
Token Distribution Records |
Permanent |
All distributions | |||
|
|||||
|
Vesting Schedules |
7 years after full vesting |
Locked token records | |||
|
|||||
|
Staking Records |
7 years |
Staking activity and reward logs |
Section 4.4 β Wallet and Key Management
|
|
|
|
| |
|---|---|---|---|---|
Retention |
Notes |
|||
|
Company Wallet Addresses |
Permanent |
| ||
|
||||
|
Key Generation / Ceremony Records |
Permanent |
| ||
|
||||
|
Multi-Sig Configurations |
Permanent |
| ||
|
||||
|
Wallet Access Logs |
7 years |
Access and transaction logs | ||
|
||||
|
Key Rotation Records |
7 years |
Key changes and |
Section 4.5 β Platform Operations
|
|
|
|
| |
|---|---|---|---|---|
Retention |
Notes |
|||
|
Issuer Onboarding Records |
Permanent |
All issuer | ||
|
||||
|
CEDEX Trading Volume Data |
7 years |
Historical platform data | ||
|
||||
|
Global Unified CEDEX Liquidity Pool Records |
7 years |
Pool configurations, |
||
|
CPMM Parameters |
|
Historical bonding curve and AMM configurations |
||
|
|
|
| ||
Platform Incident Reports |
7 years |
Security incidents, | ||
|
API Access Logs
3 years
Third-party integrations
Section 4.6 β Transfer Agent Records (Empire Stock Transfer)
Per SEC Rules 17Ad-6 and 17Ad-7:
|
|
|
|
| |
|---|---|---|---|---|
Retention |
Notes |
|||
|
Master Securityholder File |
Permanent |
DLT-based records | ||
|
||||
|
Transfer Journals |
6 years |
All transfers | ||
|
||||
|
|
|
| ||
Stop Transfer Orders |
6 years |
Stop orders and releases |
||
|
Holder Correspondence |
| 6 years |
| |
|
||||
|
Reconciliation Records |
6 years |
Daily on-chain vs. off-chain reconciliations |
Section 4.7 β Compliance Records
|
Record Type |
Retention |
Notes |
|
KYC/KYB/KYW Records |
5 years after account closure |
Bank Secrecy Act β Empire Stock Transfer onboarding |
|
AML Transaction Monitoring |
5 years |
Chainalysis KYT + TRM Labs screening logs |
|
SAR/CTR Filings |
5 years from filing |
BSA requirement β confidential |
|
OFAC Screening Records |
5 years |
Three-layer screening results and match resolution |
|
Accreditation Verification |
7 years |
Reg D / Reg S verification documentation via Empire |
π» ARTICLEArticle V: ELECTRONICElectronic RECORDSRecords MANAGEMENTManagement
Section 5.1 β Email Retention
|
|
|
|
|---|---|---|---|
Category |
Retention |
Notes |
|
|
Business Critical |
Per subject matter schedule |
Contracts, legal, |
|
|
Operational |
| 3 years |
Day-to-day business communications |
|
Transitory |
| 1 year |
Scheduling, routine inquiries |
|
|||
|
Litigation Hold |
Until hold released |
|
π§ Email Best Practices:
|
|
|---|---|
|
|
|
Categorization
Use consistent subject lines and categories
π
Attachments
Save important attachments separately
π«
Personal
Do not use company email for personal matters
Section 5.2 β Instant Messaging and Collaboration Tools
|
|
|
|
|---|---|---|---|
Platform |
Retention |
Notes |
|
|
Slack/Teams (Business) |
3 years |
Business channels | |
|
|||
|
Project Channels |
Life of project + 3 years |
Project-specific | |
|
|||
|
Confidential Channels |
7 years |
Legal, HR, |
|
|
Business SMS/Text |
| 3 years |
Business-related |
Section 5.3 β Cloud StorageDatabase and SaaSBackup Records
|
|
Retention |
|
||
|
User Account Data |
| |||
|
|
|
| ||
| 7 years after |
| ||
|
|
| ||
|
|
| ||
|
|
|
Section 5.4 β Database Records
|
|
|
|---|---|---|
|
| Platform user records |
|
||
|
Transaction History |
7 years |
All CEDEX platform transactions |
|
||
|
|
|
|
Security/Audit Logs |
7 years |
|
|
Daily Backups | ||
|
|
Rolling daily |
|
|
|
24 months rolling |
Rolling monthly |
|
Annual Backups |
7 years |
|
Section 5.5 β Backup and Disaster Recovery
|
|
|
|---|---|---|
|
|
|
|
|
|
|
|
|
|
| Year-end snapshots |
|
||
|
Blockchain Node Data |
Permanent |
Full Solana node archives |
βοΈ ARTICLEArticle VI: LITIGATIONLitigation HOLDHold PROCEDURESProcedures
Section 6.1 β Triggering Events
A Litigation Hold must be implemented whenupon: anylawsuit offiled the(immediate), followingdemand occurs:
|
|
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
Section 6.2 β Litigation Hold Process
|
|
|
|---|---|---|
|
|
β’ Step 2: Legal |
|
|
β’ Step 3: Legal |
|
|
β’ Step 4: Legal |
|
|
|
|
|
|
|
|
|
|
|
β’ Step 8: Legal |
|
|
β’ Step 9: Legal |
|
|
|
Section 6.3 β Litigation Hold Notice Requirements
All Litigation Hold notices must include:
|
|
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Section 6.4 β Blockchain Records and Litigation Holds
|
|
|---|---|
|
|
| action. Standard hold procedures apply |
|
|
|
|
| Export and preserve relevant CEDEX data as needed. |
Section 6.5 β Consequences of Non-Compliance
|
|
|---|---|
|
|
|
|
|
|
|
|
|
|
ποΈ ARTICLEArticle VII: DOCUMENTDocument DESTRUCTIONDestruction
Section 7.1 β Conditions for Destruction Authorization
Records may only be destroyed when:
|
|
|---|---|
|
|
|
|
|
|
|
|
|
|
Section 7.2 β Destruction Methods
|
|
|
||
|
Confidential Paper | |||
|
| Cross-cut shredding or incineration |
||
|
Non-Confidential Paper |
| Recycling acceptable | |
|
|||
|
Electronic Media |
Secure wiping (DoD 5220.22-M or NIST 800-88 equivalent) |
||
|
Hard Drives / SSDs |
| Degaussing and physical destruction | |
|
|||
|
Cloud Data |
Certified deletion with written confirmation | ||
|
|||
|
Blockchain Data |
|
Section 7.3 β DestructionDocumentation Documentationand Annual Cycle
All destruction must be documented with:
|
|
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Section 7.4 βdestruction. Annual Destructioncycle: Cycle
January
|
|
|---|---|
|
|
February |
|
|
|
|
|
destruction), May |
|
Section
7.5
litigation.
π«NEVER destroyrecords:
Subjectrecords subject to a LitigationHoldRequestedHold, requested by regulators orauditorsBeforeauditors, before retention period hasexpiredWithoutexpired, without properauthorizationThatauthorization, or that may be relevant to anticipatedlitigation
π₯ ARTICLEArticle VIII: RESPONSIBILITIESResponsibilities
Section
|
Role |
Key Responsibilities |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Board of Directors
|
|
|
|---|---|
|
|
|
|
|
|
Section
8.3
β Chief Legal OfficerCounsel
/
General
Counsel
π Responsibility
Description
βοΈ
Litigation Holds
Implement and manage litigation holds
πholds;
Legal Guidance
Adviseadvise on retentionretention; requirements
π
Compliance
Monitor compliance withmonitor legal requirementscompliance; recommend updates
CTO
π
Updates
Recommend Policy updates
Section 8.4 β Chief Financial Officer
π Responsibility
Description
π°
Financial Records
Ensure retention of financial records
π
Audit Support
Support audit record requirements
π
Tax Records
Ensure retention of tax records
Section 8.5 β Chief Technology Officer
π Responsibility
Description
π
Blockchain Records
Oversee blockchain record retention
πΎretention;
Systems
Implementimplement technical retentioncontrols; controls
πmanage
Security
Ensurebackups; ensure secure storage and destruction
πΎ
Backups
Manage backup retention schedules
Section 8.6 β Compliance Officer
π
Responsibility
Description
π
Administration
Day-to-day Policyadministration; administration
πconduct training; monitor compliance; prepare reports
Training
Conduct retention training
π
Monitoring
Monitor compliance
π
Reporting
Prepare compliance reports
Section 8.7 β Department Heads
(Record
Custodians)
π Responsibility
Description
π
Department Records
Ensure proper retention ofwithin departmentdepartments; records
π₯train staff; authorize destruction; implement holds
Staff Training
Train staff on retention requirements
ποΈ
Destruction
Authorize department record destruction
βοΈ
Litigation Holds
Implement holds within department
Section 8.8 β All Employees
π
Responsibility
Description
π
Compliance
Comply with thisPolicy; Policy
πcomplete
Training
Completetraining; required training
βοΈ
Holds
Complycomply with litigation holds
π¨holds;
Reporting
Reportreport potential violations
β οΈ ARTICLEArticle IX: COMPLIANCECompliance ANDand ENFORCEMENTEnforcement
Section 9.1 β Training
π
Training
Type Frequency
Audience
π
Type
Frequency
Audience
Initial Training
Upon hire
All employees
π
Annual Refresher
Annually
All employees
Blockchain-Specific
π
Blockchain-Specific
Upon assignment
Technical staff
βοΈstaff, CTO team
Litigation Hold
As needed
Affected custodians
π
Management Training
Annually
Department heads
Legal OfficerCounsel
|
| |
|---|---|---|
| Implement and manage litigation | |
|
| |
|
|
|
|
CTO |
|
|
Section 8.4 β Chief Financial Officer
|
|
|---|---|
|
|
|
|
|
|
Section 8.5 β Chief Technology Officer
|
|
|---|---|
| Oversee blockchain record |
|
|
|
|
|
|
|
|
|
Section 8.6 β Compliance Officer
|
|
|---|---|
|
| Day-to-day |
|
|
|
|
|
|
|
|
|
Section 8.7 β Department Heads
(Record
|
|
|---|---|
| Ensure proper retention |
|
|
|
|
|
|
|
|
|
Section 8.8 β All Employees
|
|
|---|---|
|
| Comply with |
|
|
|
|
|
|
β οΈ ARTICLEArticle IX: COMPLIANCECompliance ANDand ENFORCEMENTEnforcement
Section 9.1 β Training
|
|
|
|
|---|---|---|---|
Type |
Frequency |
Audience |
|
|
Initial Training |
Upon hire |
All employees | |
|
|||
|
Annual Refresher |
Annually |
All employees |
|
|
Blockchain-Specific |
| Upon assignment |
Technical |
|
|||
|
Litigation Hold |
As needed |
Affected custodians | |
|
Management Training
Annually
Department heads
Section 9.2 β Auditing
|
|
|
| |
|---|---|---|---|
Frequency |
Scope |
||
|
Compliance Audit |
Annually |
Policy compliance | |
|
|||
|
Systems Audit |
Annually |
Technical | |
|
|||
|
Blockchain Audit |
Quarterly |
On- | |
|
|||
|
Destruction Audit |
Annually |
Destruction practices and documentation |
Section 9.3 β Violations
Violations of this Policy may result in:
|
|
|---|---|
|
|
|
|
|
|
|
|
|
|
Section 9.4 β Reporting Violations
|
|
|---|---|
violations to: Compliance Officer |
|
(compliance@otcm.io), Ethics Hotline |
|
|
|
Legal |
|
π‘οΈNo Retaliation:(frank@otcm.io). The Company prohibits retaliation against anyone who reports a good faithconcern about Policy compliance.concern.
ποΈ ARTICLEArticle X: ADMINISTRATIONAdministration
Section 10.1 β Policy Owner
The Chief Legal OfficerCounsel is the owner of this PolicyPolicy. Annual review by Legal Counsel covers legal changes, technology changes, business changes, audit findings, and isindustry responsiblebest for:
|
|
|---|---|
|
|
|
|
|
|
|
|
Section 10.2 β Annual Review
This Policy shallmay be reviewed annuallyapproved by the Legal DepartmentCounsel; andretention updatedschedule aschanges necessaryrequire to reflect:
|
|
|---|---|
|
|
|
|
|
|
|
|
|
|
Section 10.3 β Amendment Procedures
|
|
|---|---|
|
|
| CEO + |
|
|
|
Section 10.4 β Questions
π§Contact:compliance@otcmprotocol.com
Questions regarding this Policycompliance@otcm.io or specific retention requirements should be directed to the Compliance Officer or Legal Department.frank@otcm.io.
βοΈAcknowledgment ACKNOWLEDGMENTand AND CERTIFICATIONCertification
I acknowledge that I have received and read the Groovy Company, Inc. dba OTCM Protocol, Inc.Protocol Document Retention Policy. I understand its contents and agree to comply with all of its terms and conditions.
I understand that I am responsible for retaining records in accordance with this Policy and the applicable retention schedules.
I agree to comply with any Litigation Hold notices I receive and understand that failure to preserve records subject to a hold may result in serious consequences for the Company and for me personally.
I understand
|
Field |
|
|
Signature |
_________________________________ |
|
Date |
_________________________________ |
|
Printed Name |
_________________________________ |
|
Title / Position |
_________________________________ |
|
Department |
_________________________________ |
Document Information
|
Field |
Value |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Document ID |
OTCM-POL-DRP-001 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Version |
8.0 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Effective Date |
March 2026 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Legal Entity |
Groovy Company, Inc. dba OTCM Protocol |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Entity Type |
Wyoming Corporation |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Governing Law |
Federal Securities Law, Wyoming Business Corporation Act, and New Jersey State Law |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Approved By |
Board of |
|
|
|---|---|
|
|
|
|
|
|
|
|
|
|
π APPENDIX A: QUICK REFERENCE RETENTION SCHEDULE
π’ Corporate
|
|
|---|---|
|
|
|
|
|
|
|
|
π° Financial
|
|
|---|---|
|
|
|
|
|
|
|
|
π Tax
|
|
|---|---|
|
|
|
|
π€ Employment
|
|
|---|---|
|
|
|
|
|
|
βοΈ Legal
|
|
|---|---|
|
|
|
|
|
|
π Blockchain
|
|
|---|---|
|
|
|
|
|
|
|
|
OTCM Protocol, Inc. A Wyoming Digital Asset Corporation
πΒ© 2026 Groovy Company, Inc. dba OTCM Protocol SEC| Category 1All Issuer-SponsoredRights TokenizedReserved Securities Infrastructure| CONFIDENTIAL
Document ID: OTCM-POL-DRP-001 | Version 1.0 | Effective: January 30, 2026