At Rekhic, we believe in building trust through engineering transparency. This Privacy Policy explains exactly how we handle your technical architectures, code manifests, imported files, and account information when you use our visual workspace.

1. Local-First Processing & Architecture Analysis

Rekhic is engineered with strict local-first architecture principles:

Code to Diagram: Source code files, directories, and package manifests (such as package.json, pom.xml, requirements.txt, and docker-compose.yml) uploaded or pasted for architecture detection are processed and analyzed strictly locally within your browser runtime. Rekhic does not upload, transmit, or persist your source code contents to any Rekhic backend servers.
README to Diagram: Pasted README text and uploaded Markdown documentation are parsed entirely client-side. No documentation contents are transmitted to external servers.
Public GitHub to Diagram: When you provide a public GitHub repository URL, your browser fetches public repository tree data directly from GitHub's public REST API. The files are parsed locally on your machine. Rekhic operates no intermediate server proxy that clones or stores your repositories.
Markdown Documentation Export: Exported markdown specifications (ADRs and architecture docs) are synthesized directly in client memory and downloaded to your computer without remote transmission.

2. Public GitHub Integration

Rekhic's GitHub import feature operates under the following constraints:

Public Repositories Only: Rekhic exclusively supports public GitHub repositories. Private repositories are not currently accessible.
No Credentials or OAuth Tokens: Rekhic does not request, store, or require GitHub personal access tokens, SSH private keys, or OAuth account authorization.
Direct Browser API Calls: API calls to GitHub originate directly from your client browser and are subject to GitHub's standard unauthenticated rate limits (60 requests per hour per IP address).
Third-Party Terms: Your interaction with GitHub's public API remains subject to GitHub's own Privacy Statement and Terms of Service.

3. Handling of Uploaded Files

When you drag and drop files into the Rekhic workspace for code or documentation analysis:

Files remain only in temporary browser memory (RAM) and transient client state.
Uploaded source files are not written to long-term storage or uploaded to cloud buckets.
Once you navigate away or refresh the generator view, unpersisted raw source files are garbage-collected by your browser.

4. Workspace and Diagram Data

How your diagram metadata (nodes, labels, coordinates, and connectors) is saved depends on your authentication state:

Guest and Anonymous Usage: When you use Rekhic without signing in, you are assigned an anonymous guest identifier. Your diagram content (nodes, edges, titles) is stored strictly in your browser's local IndexedDB database. Your guest diagrams are never transmitted to our cloud servers. Clearing browser data will delete local guest diagrams.
Registered Accounts: When signed into a permanent account, your diagram topology (node coordinates, labels, tech icons, and edges) is synchronized to our secure cloud database (Google Firebase Firestore) under your user ID to allow cross-device editing.

5. Product Analytics

We use Google Analytics (via Firebase) to track generalized application usage metrics to help us monitor performance and improve usability.

What We Never Send to Analytics: We verify in our implementation that source code, repository code, README text, diagram component labels, repository URLs containing credentials, personal access tokens, and passwords are never transmitted to Google Analytics or third-party tracking services.

Analytics events are restricted to anonymous interface interactions (such as page_view, import_started, and theme_toggle).

6. Cookies and Local Storage

We use browser localStorage, IndexedDB, and essential authentication cookies:

Cookies: Essential session cookies managed by Firebase Authentication to maintain your authenticated login state.
IndexedDB: High-performance local storage used to persist your diagrams on your machine.
localStorage: Used to store user interface preferences such as active theme (Light/Dark mode) and layout view settings (Grid/List mode).

7. Data Security and Infrastructure

Registered account data is secured using Google Cloud / Firebase infrastructure. Firestore Security Rules enforce strict access controls: diagrams are private to their authenticated owner. We do not sell your personal data or your proprietary system architectures, and we do not use your architectures to train external AI models.

8. Account and Data Deletion

Self-service account deletion is permanently available in the Account Settings menu. Initiating account deletion immediately deletes your Firebase Authentication profile and deletes all user-owned cloud diagrams from our Firestore database.

9. Children's Privacy

Rekhic is intended for professional software developers, systems architects, and engineering teams. We do not knowingly collect personal information from individuals under the age of 13.

10. Contact Information

If you have questions about this Privacy Policy or wish to exercise data privacy rights, please contact us at: support@rekhic.in.