REFCARDS
Refcards Privacy Policy
Refcards Privacy Policy
Data Use, Storage, and System Transparency
This Privacy Policy explains how Refcards collects, uses, and manages data within the platform.
By using Refcards, you agree to the practices described in this Policy.
1. Platform Context
Refcards is a structured system for building ideas into real projects through collaboration and defined workflows.
Refcards Core acts as the system of record for structured project data, file records, file routes, filing rules, consent, audit, and verification.
It is not a general content or social platform.
Data within Refcards is:
-
structured
-
traceable
-
linked to defined roles and relationships
2. Information We Collect
Refcards may collect and process:
-
Account Information: name, email address, and profile details
-
Project and Collaboration Data: ideas and project records, messages and communication, files and attachments, contributor roles and activity
-
System and Activity Data: timestamps and activity logs, system-generated events, export and audit records
3. How Data Is Used
Data is used to:
-
operate the platform and its structured workflows
-
enable collaboration between users
-
maintain project history and continuity
-
support export, verification, and trust mechanisms
-
improve system performance and usability
4. Data Ownership
Refcards follows a structured ownership model:
Refcards does not assume ownership of user-created content.
-
users retain ownership of their contributions
-
contributors own their files, messages, and inputs
-
projects maintain linked contribution records
-
Hubs provide environments but do not own user data
5. Data Storage and Structure
Data within Refcards is stored as part of a structured system.
This includes:
Data is retained to preserve:
Approved Hub-specific or exported-data storage does not replace the Refcards Core system of record.
-
linked records (ideas, projects, contributors)
-
file references and metadata
-
activity and audit logs
-
file records and file routes
-
consent, export, and verification records where applicable
-
system integrity
-
project continuity
-
collaboration history
6. Export and Data Portability
Refcards allows users to export structured project data.
Exports may include:
Export bundles are:
-
project records
-
contributor relationships
-
messages and activity
-
files (where permitted)
-
portable
-
verifiable
-
controlled by role and consent
7. Archive and Retention Controls
Refcards supports controlled handling of export archives.
Users may:
Users acknowledge:
Archive removal does not delete the underlying system record.
-
download export bundles
-
remove local downloadable archives
-
removing an archive only affects the downloadable package. It does not delete underlying project data, canonical records, file records, file routes, filing rules, consent records, audit history, verification hashes, or system history retained by Refcards Core
-
underlying project data remains within the Refcards Core system
-
audit records, hashes, and verification data may be retained
8. Data Retention
Refcards retains data to support:
Certain data may be retained even after archive removal, including:
-
project continuity
-
collaboration traceability
-
system integrity and auditability
-
activity logs
-
export records
-
verification data
-
consent and ownership records
-
file records and file route metadata where needed for project continuity and auditability
9. Data Sharing
Refcards does not sell user data.
Data may be shared only:
-
within projects and collaboration environments
-
with other participants where required for structured workflows
-
when required by law
10. Security
Refcards implements reasonable measures to:
However, no system is completely secure, and use of the platform is at the user's own risk.
-
protect user data
-
maintain system integrity
-
prevent unauthorised access
11. User Rights
Users may:
Requests for data access or deletion may be made through platform contact channels.
Data access or deletion requests may be subject to retention needed for project continuity, auditability, legal obligations, platform integrity, consent records, and verification history.
-
access their data
-
manage their contributions
-
control export of their data (subject to consent rules)
12. Platform Evolution
Refcards is an evolving system.
Data handling practices may be updated as the platform develops.
Users will be informed of material changes where appropriate.
13. Contact
For questions regarding this Privacy Policy, users may contact:
Email: support@refcards.io
14. Acceptance
By using Refcards, you confirm:
-
You understand how data is used within a structured system
-
You acknowledge export, retention, and audit behaviour
-
You agree to this Privacy Policy
Review Platform Terms
REFCARDS
Private founder workspace, Hub structure, and controlled export/import records.
Subscribe and join waiting list
Public Projects
Public Events
About
Invite
Founder
Founder Note
How It Works
What Is Refcards
Use Cases
Why Invite-Led
Platform Terms
Privacy
support@refcards.io