REFCARDS
Trust
Private work stays private until release is intentional.
Refcards is being shaped around clear identity, contributor boundaries, project custody, and controlled public presentation.
Public-safe promise
This page describes the trust model without exposing private profile, project, Hub, or export data.
Identity first
Profiles, roles, and account sessions keep the source of each workspace action clear.
Data ownership
Export approvals, timers, and scope presets make data release deliberate instead of accidental.
Project custody
Project activity, export rows, import records, and restored package history keep handoffs visible.
Public control
Public pages only expose founder-approved public records, files, and project presentation.
Release boundary
Public pages are an output, not the workspace.
Internal drafts, private team projects, Hub imports, and export controls remain behind account access. Public project pages should reflect only approved information.
Log in
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