Data and Privacy

Engineering system diagrams frequently contain sensitive technical information—such as internal API routes, microservice topology, and database vendor choices. Rekhic is architected with privacy and local-first principles.

1. Local-First Processing Architecture

All code parsing, README extraction, and architecture generation features run locally in your browser:

• Code to Diagram: When you upload a project folder or manifests, parsing runs client-side via JavaScript AST and regex matching. Source code is never transmitted to a Rekhic server.
• README to Diagram: Markdown files and Mermaid blocks are parsed directly in your browser.
• GitHub to Diagram: Files fetched from public GitHub repositories are transferred directly from GitHub's public API to your browser without server-side proxying or storage.

2. Cloud Storage for Diagrams

For signed-in users:

• Diagram node positions, titles, icons, and connections are stored in Firebase Firestore under your authenticated User ID.
• Access is strictly governed by Firebase Security Rules: only you can view or modify your diagrams.
• We do not sell your personal data or your proprietary system architectures.
• We do not use your architecture diagrams to train third-party AI models.

3. Product Analytics

Rekhic uses Google Analytics strictly to monitor application health and feature usage (e.g. tracking page views, button clicks, and error rates):

• Never Sent: Source code contents, README text, diagram labels, file paths, repository tokens, or passwords are never transmitted to analytics.
• Sent: Generalized UI events (e.g. import_readme_start, theme_toggle_clicked).

Next: Explore solutions to common issues in Troubleshooting.