Intellectual Property Ownership Framework
Ownership boundaries for client engagements
Summary
This framework sets the intellectual property ownership boundaries for the Sasha platform built by Context Is Everything. It applies to all Context Is Everything client engagements and internal projects.
Principle: Clients own their data and their customizations. Context Is Everything owns its frameworks and tools.
About Context is Everything
Context Is Everything is the trading name of Bernard Moves Ltd, a company registered in England and Wales. It builds Sasha, a private AI platform deployed inside a customer's own infrastructure, and creates and maintains its own frameworks, tools and methodologies, including the Contour Methodology.
Customer & client rights
What you own & control
Client ownership rights
Your Data and Business Intelligence
- All customer data: Contact lists, campaign content, analytics, business metrics
- Derived insights: Analysis, reports and business intelligence from your data
- Market research: Industry-specific findings and competitive intelligence
- Final deliverables: All documentation, reports and project outputs created for you
Your Custom Solutions
- Domain-specific prompts: AI instructions written for your customer data processing
- Business workflows: Logic and processes unique to your operations
- Custom templates: Industry-specific content and designs created for your use
- Tech integrations: Custom connections built for your stack
Your Data Rights
- Ownership of all data you provide to Context Is Everything
- Export rights: Download all your data in standard formats at any time
- Deletion rights: Request removal of your data from our systems
- Audit rights: Review our data handling and security practices
Context is Everything intellectual property
What Context is Everything owns
Core framework
The 26-Phase Methodology
- Autonomous development framework: Our methodology for building products
- Research and validation processes: Investigation and evidence-gathering frameworks
- System architecture patterns: Technical infrastructure designs
- Documentation automation: Workflows for generating project documentation
Proprietary Development Tools
@knowcode/doc-builder: Our npm package for automated documentation generation- Development accelerators: Scripts and utilities used in project delivery
- AI automation tools: Proprietary algorithms and processing methodologies
- Internal software: All platforms and applications developed by Context Is Everything
Reusable assets
Framework Components
- General processing prompts: AI instructions and templates that are not client-specific
- Development methodologies: Coding standards, AI frameworks and quality assurance processes
- Design systems: Visual patterns, UI components and reusable design elements
- Process documentation: Process frameworks and operational guidelines
Business Operations IP
- Client delivery processes: All tooling and methodologies for project execution
- Project management frameworks: Quality assurance and delivery systems
- Training and documentation: Internal knowledge systems and operational procedures
- Improvement processes: Processes for changing how we deliver services
Third-party intellectual property
Technology partners
AI & development platforms
Anthropic Inc.
- Claude Code platform: The foundation of our autonomous development system
- Claude AI models: Language models and related technologies
- Intellectual property: All Claude-related trademarks, copyrights and patents
Core Technology Stack
- n8n: Workflow automation platform
- Postmark: Email delivery service
- Cloud providers: AWS, Google Cloud and other infrastructure services
- Open source ecosystem: npm packages, development tools and monitoring solutions
graph TD
A[Your Project] --> B[Context Is Everything Tools]
B --> C[Third-Party Services]
subgraph "Third-Party IP"
C --> D[Anthropic Claude]
C --> E[n8n Automation]
C --> F[Postmark Email]
C --> G[Cloud Services]
end
style A fill:#f0fdf4,color:#000
style B fill:#fefce8,color:#000
style C fill:#f0f9ff,color:#000
Third-party terms
- Governed by their own licences: Each service operates under its own terms and conditions
- Integration services only: Context Is Everything provides configuration and integration expertise
- Data processing terms: Your data processed through third-party services follows their privacy policies
- No liability for changes: Context Is Everything is not responsible for third-party service modifications or availability
Tool usage rights & licensing
What you can use and what stays protected
Your rights during engagement
Access and Usage
- Tool access: Use all Context Is Everything proprietary tools during your project
- Output ownership: All generated content, documentation and code belongs to you
- Deliverable rights: Full rights to use all project deliverables
- Data and insights: Ownership of all analysis and business intelligence
Usage restrictions
Protected Assets
- No redistribution: You may not share or resell Context Is Everything tools
- No modification: You may not reverse-engineer or modify our proprietary tools
- No sublicensing: You may not provide Context Is Everything tools to third parties
- Time-limited: Tool access ends when the project completes, unless agreed otherwise
Framework licensing model
graph LR
A[General Methodology] --> B[Applied to Your Project]
B --> C[Client-Specific Customizations]
C --> D[You Own Customizations]
A --> E[Reused for Future Clients]
subgraph "Your IP"
D
end
subgraph "Context Is Everything IP"
A
E
end
style D fill:#f0fdf4,color:#000
style A fill:#fefce8,color:#000
style E fill:#fefce8,color:#000
How It Works
- General frameworks: Context Is Everything reuses its core methodology across projects
- Your customizations: All client-specific adaptations remain your property
- Framework changes: Context Is Everything updates the framework from learnings across all projects
Data security & compliance
How we protect your information
Data processing standards
Purpose-Limited Processing
- Project-only usage: We use your data only for the agreed deliverables
- Retention terms: Defined in every engagement
- Regular audits: Compliance monitoring and validation
Storage & retention
Infrastructure
- Access controls: Permissions and authentication on all systems
- Defined periods: Retention timelines set by the engagement terms
- Deletion: Data removal when the project completes
- Backups: Integrity protection and disaster recovery
Compliance
- GDPR: Protection for European client data and privacy rights
- Industry-specific: Healthcare HIPAA, finance PCI-DSS and other sector requirements
- Security testing: Regular vulnerability assessments and penetration testing
- Documentation: Audit trails of data processing activities
Cross-project intelligence
What we share between projects
Aria product development
How Client Work Affects Internal Products
- General learnings: Methodology improvements from client engagements go into our internal products
- Process refinement: Process improvements found during client work go into Aria development
- Data separation: Your data and customizations stay separate and protected
- Explicit consent: We do not use client data in internal products without your written permission
What gets shared
- General methodologies and process improvements
- Technical patterns: Reusable architecture and development approaches
- Process optimization: Workflow improvements
- Technology insights: General technological advances and capabilities
What stays private
- Business strategies: Client-specific implementations and approaches
- Competitive intelligence: Market insights and competitive analysis
- Custom solutions: Unique workflows and business logic
- Client relationships: All engagement details and communications
Conflict prevention
- No competitive sharing: We do not share competitive intelligence between competing clients
- Confidentiality: Client-specific strategies and insights remain confidential
- Industry knowledge: We apply general industry knowledge for all clients
- Conflict policies: Procedures prevent inappropriate information sharing
Legal framework & enforcement
Legal basis
Governing law
- This framework operates under [Jurisdiction TBD] law
- Disputes go to arbitration
- Regular compliance reviews
- Works together with service agreements
IP protection
- Copyright protection for materials
- Trademark protection for branding
- Trade secret protection for methodologies
- Patent considerations for innovations
Violations & remedies
- Reporting process for violations
- Remediation for inadvertent issues
- Legal remedies for infringement
- Negotiated dispute resolution
Implementation guide
Project lifecycle
Project initiation
- IP terms agreed before work starts
- Ownership boundaries documented
- Security requirements set
- Review points scheduled
During engagement
- IP boundary checks
- Decisions documented
- Client approval processes
- Compliance monitoring
Engagement completion
- IP documentation finalized
- Data exported to the client
- Tool access ended
- Post-engagement protection in place
Review & updates
How this framework changes
Review schedule
- Annual framework review: Evaluation of all terms and conditions
- Legal compliance updates: Changes when laws and regulations change
- Client feedback: Changes based on client input
- Technology changes: Updates for new tools and methodologies
Version control & communication
- Version history: All changes documented with explanations
- Client notifications: Material changes communicated to all affected parties
- Grandfathering: Existing engagements keep their terms during transitions
- Effective dates: Stated for every framework change
Contact & support
Questions about this framework
Get in touch
Context Is Everything
Email: hello@context-is-everything.com
Legal Department: hello@context-is-everything.com
Emergency IP Issues
Contact: hello@context-is-everything.com