What you can export today#
- Blueprint package (JSON) — all nine system calculations in one portable file. Rebuildable from birth data, but useful for backup / sharing with a practitioner.
- KAXANTA conversation history (Markdown or JSON) — every message across every session, with timestamps.
The JSON format is stable — the schema is documented at /api/v1/users/me/export, and the field names match the Mongoose model shapes. No breaking changes without a version bump.
How to trigger an export#
- Settings → Privacy → Data export.
- Pick the package you want (Blueprint or KAXANTA).
- Pick the format (JSON, or Markdown for KAXANTA).
- The browser downloads the file directly — no email, no waiting.
GDPR right-to-portability#
The blueprint JSON export satisfies the GDPR right-to-portability (Article 20) requirement — it is the full set of personal data we hold about you, in an interoperable format. If you need any additional data for regulatory purposes (IP logs, webhook records, admin notes), email privacy@kaxanta.com and we will pull it within 30 days.
If you are comparing us to another cosmic-chart tool, re-computing your blueprint elsewhere should produce the same Human Design type, same Life Path, same Day Master, etc. — differences usually mean different ephemeris sources, not real disagreement.
What we do NOT export#
- Server-side analytics events (counts, not individual records — pseudonymised at rest).
- Aggregated performance telemetry (latency p95s, error rates — zero personal content).
- Support-team internal notes (opt into our internal ticket SLA by signing the support DPA — rarely needed).
Was this helpful?
← Back to Help index