1. Platform Overview
Refcards is a structured platform designed to support the development of ideas into real projects through collaboration, defined workflows, and ongoing progress.
Refcards Core operates as the system of record for structured project data, canonical records, file records, file routes, filing rules, consent, export, audit, and verification.
Refcards operates as a structured system for building real projects - not a general community platform.
-
a general discussion platform
-
an unstructured collaboration space
2. User Roles
Refcards supports multiple participant roles, including:
Each user interacts with the platform within defined roles and permissions.
-
individual users (members)
-
contributors to ideas and projects
-
Hub founders (subject to separate agreement)
3. Account Responsibilities
Users agree to:
Users are responsible for all activity under their account.
-
provide accurate account information
-
maintain the security of their account
-
use the platform in accordance with these Terms
4. Use of the Platform
Users may use the platform within structured permissions.
-
Users may create and develop ideas
-
Users may collaborate with other users
-
Users may contribute to projects
-
Users may participate in Hubs
-
Users must not misuse platform functionality
-
Users must not interfere with system integrity
-
Users must not attempt to bypass system rules or controls
5. Data Ownership
Refcards follows a structured ownership model:
Refcards does not assume ownership of user-created content.
Hub participation, Hub presentation, or Hub storage does not transfer ownership of contributor data or authority over Refcards Core records.
-
users retain ownership of their contributions
-
contributors own their messages, files, and inputs
-
founders guide project direction
-
Hubs provide environments but do not own data
6. Collaboration and Contributions
By contributing to a project, users acknowledge:
Collaboration is governed by structure, visibility, and defined roles.
-
their contributions become part of a structured project record
-
their contributions may be visible to other participants within the project
-
their contributions are linked to their identity within the system
7. Export and Data Handling
Refcards provides structured export functionality.
Export bundles are portable and verifiable within the approved export scope. They do not replace Refcards Core as the system of record.
-
Users may export project data based on role and consent
-
Users may download structured export bundles
-
Users may verify exported data independently
-
Users must not export data they do not own or have consent to include
-
Users must not misuse exported data outside permitted scope
-
Users must not expand access beyond export scope
-
Users must not reconstruct excluded or restricted data
-
Users must not treat exported or externally stored data as replacing Refcards Core records
8. Archive and Retention Controls
Refcards supports controlled handling of export archives.
Archive removal affects downloadable data, not the underlying system record.
-
Users may remove local downloadable export archives
-
Users may manage access to exported packages
-
Removing an archive does not delete underlying project data, canonical records, file records, file routes, filing rules, audit history, consent records, verification hashes, or system history retained by Refcards Core
-
System records, audit history, and verification data may be retained
-
Data handling follows platform structure and consent rules
9. System Integrity
Refcards operates as a structured system.
All activity is subject to system rules and structured workflows.
-
Users must not attempt to modify system-level data relationships
-
Users must not interfere with identity or traceability mechanisms
-
Users must not bypass verification or audit controls
-
Users must not bypass Core file routes or filing rules
-
Users must not alter file records or canonical records
-
Users must not interfere with consent, ownership, audit, or verification controls
-
Users must not treat Hub storage or exported packages as the system of record
-
Users must not reconstruct or expose restricted data
10. Hubs
Hubs are structured environments built on Refcards.
Hubs are environment and workflow layers. They may shape participation, presentation, and approved integrations.
Hubs do not replace Refcards Core backend systems, Core filing, file routes, canonical records, consent rules, or verification requirements.
Hub founders are subject to additional responsibilities defined in separate agreements.
-
Users participating in Hubs operate within the Hub's defined workflows
-
Users participating in Hubs collaborate under structured conditions
-
Users participating in Hubs retain ownership of their contributions
11. Privacy and Data Use
Refcards processes data in accordance with platform policies.
This includes:
Further details are provided in platform documentation and privacy policies.
-
project data and collaboration records
-
system-generated activity and audit data
12. Platform Availability
Refcards is an evolving system.
The platform may:
No guarantee is made regarding uninterrupted availability.
-
be updated, modified, or improved over time
-
introduce new features or system changes
-
undergo planned or unplanned downtime
13. Limitation of Liability
Refcards provides a structured system for collaboration and project development.
Refcards is not responsible for:
Use of the platform is at the user's own risk.
-
decisions made by users or collaborators
-
external use of exported data
14. Termination
Refcards may suspend or terminate access if:
Users may stop using the platform at any time.
-
these Terms are violated
-
system integrity is compromised
15. Changes to Terms
These Terms may be updated as the platform evolves.
Users will be notified of material changes where appropriate.
Continued use of the platform constitutes acceptance of updated Terms.
16. Acceptance
By using Refcards, you confirm:
-
You understand the platform is a structured system for real project development
-
You agree to operate within defined roles, workflows, and system rules
-
You acknowledge data ownership, export, and responsibility conditions
-
You acknowledge that Hubs provide environments and do not own contributor data or replace Refcards Core authority.