Privacy Policy

1. Who we are

EnterGenni ("we", "us", "our") is a product by intrologics (INTROLOGICS (SMC-PRIVATE) LIMITED). EnterGenni makes enterprise systems AI-ready: it generates the AI layer (APIs, connected data models, sync and queries) from the entity models and schema metadata submitted by its users.

For privacy inquiries, contact us at our contact page.

2. What data we collect

2.1 Sandbox users (no account required)

When you use the sandbox at /sandbox.html, no personal data is collected. The sandbox runs a fixed, pre-generated sample model that lives entirely in server memory. You download a ZIP — we receive a standard HTTP request with your IP address (retained for up to 24 hours in server access logs for security purposes, then discarded).

2.2 API users (synchronous endpoints)

When you call POST /api/generate/graph or /api/generate/graph/from-excel, your entity model is processed entirely in memory. The generated ZIP is streamed back in the response. No model data, no generated code, and no user-identifying information is written to disk or any database. The only log entry is a standard access log line (timestamp, HTTP method, path, response code, byte count).

2.3 API users (async job endpoints)

When you call POST /api/jobs/graph, your model and the resulting generated ZIP are stored in an in-memory queue until you download the result or the job expires (1 hour). After expiry the job record and all associated data are permanently deleted from memory. No disk persistence occurs.

2.4 Account holders (Pro & Enterprise)

To operate a paid account we collect:

• Your email address (account identifier, billing receipts)
• Payment information — processed entirely by our payment provider (Stripe). We never see or store your card number; we store only the Stripe customer ID and subscription status.
• Account usage metadata — generation count, last active date, plan tier. No model content.

2.4a Review and multi-system sessions (signed-in users)

When you use Name Review, Enterprise Linking or Type Rules, we store in your account the schema metadata you upload (entity, field and relationship names, types, lengths), the link proposals, your saved type-rule sets, and the append-only log of your decisions (what changed, from what, to what, when, and by whom). We never receive or store row data. These records are kept so you can return, revert and regenerate, and are scoped to your account.

AI suggestions. If your plan or trial includes AI suggestions, the names, types and lengths of the entities and fields in the session (and system names, when linking) are sent to Google's Gemini API to produce suggestions. No row data, credentials or connection strings are sent. Suggestions are validated and are applied only when you accept them, or, in a project where you switch on auto-apply for AI names, automatically at or above the confidence you choose; those changes are marked in your log and can be reverted. If you do not want your metadata processed this way, do not request AI suggestions; the rule-based suggestions run without it.

Questions in plain English. When you ask a question on the Ask page, the question and the schema of the chosen model (labels, property names and types, relationship types) are sent to Google's Gemini API to draft a query. No row data is sent, and the query is not run by us. We do not store the question.

Running queries on your database. If you connect a database on the Ask page, the connection URL, user and password are kept in that browser tab and sent with each query you run; the query runs read-only and the rows are returned to your browser. We do not store or log the credentials, the queries or the results.

Provision on Aura. The Aura API key, the access token and the database password you use on the Provision on Aura page pass through our server only for the request that needs them. We do not store or log them. The database is created in your own Neo4j Aura account under Neo4j's terms.

2.5 Contact form submissions

If you submit a message via /contact.html, we collect your name, email address, and the message you send. This is used solely to respond to your enquiry.

3. How we use it

• To operate the service — process generation requests, manage accounts, send billing receipts.
• To communicate with you — reply to support and sales enquiries, send account-related transactional emails (no marketing without explicit consent).
• To maintain security — detect and block abusive or malicious requests using access log analysis.
• To improve the service — anonymized aggregate statistics (total generations per day, average entity count) with no personally identifying information.

We do not use your entity model or generated code for AI training, product analytics, or any secondary purpose.

4. Data retention

We keep data for the shortest time necessary to operate the service.

To request early deletion of any data we hold about you, contact us. We will action the request within 30 days.

5. Sharing and disclosure

We do not sell, rent, or share your personal data or entity models with any third party, except:

• Payment processing: Stripe processes payment data. Their privacy policy governs that data.
• AI suggestions: Google (Gemini API) processes the schema metadata described in section 2.4a when you request AI suggestions. We do not send row data.
• Legal obligations: If required by law, court order, or regulatory authority, we may disclose data to the extent required. We will notify you where legally permitted.
• Business transfer: In the event of a merger or acquisition, data may be transferred to the new entity subject to equivalent privacy commitments.

Other than the AI processing you request in section 2.4a, we never share your schema, model, or generated code with any third party for any commercial purpose.

6. Security

All traffic is encrypted in transit using TLS 1.2+. The generation engine runs in an isolated container with no network egress. Generated ZIP files are held in-memory with a 1-hour TTL; no customer model data is written to persistent storage on our servers. Access to production systems is restricted to authorised personnel only.

Enterprise customers can additionally negotiate private cloud deployment, where the generator runs entirely within their infrastructure and no data ever leaves their network.

7. Your rights

If you are in the European Economic Area, UK, or another jurisdiction with data protection laws, you have the right to:

• Access — request a copy of personal data we hold about you.
• Rectification — correct inaccurate personal data.
• Erasure — request deletion of your personal data ("right to be forgotten").
• Restriction — ask us to stop processing your data in certain circumstances.
• Portability — receive your data in a structured, machine-readable format.
• Objection — object to processing based on our legitimate interests.
• Withdraw consent — where processing is based on consent, withdraw it at any time.

To exercise any of these rights, contact us. We will respond within 30 days.

8. Cookies and local storage

8.1 What we use

EnterGenni uses a minimal set of browser storage mechanisms. We do not use advertising cookies, cross-site tracking, or third-party analytics scripts.

8.2 Managing your preferences

To reset your cookie preference and see the consent banner again, open your browser's developer tools and run:

localStorage.removeItem('gf_cookie_pref');

Then refresh the page. You can also clear all site data from your browser's privacy / site settings.

8.3 Essential vs. preference cookies

Essential cookies (session, antiforgery) are required for the service to function correctly. Selecting "Essential only" in the cookie banner still allows these. Preference cookies (gf_cookie_pref) are stored in localStorage, not sent to the server, and do not track you.

We do not use third-party tracking cookies (Google Analytics, Facebook Pixel, etc.). If we add analytics in the future, it will appear in this section and in the consent banner before being activated.

9. Changes to this policy

We may update this policy to reflect changes in how we operate the service or to comply with applicable law. Material changes will be communicated to account holders by email at least 14 days before they take effect. The "Last updated" date at the top of this page always reflects the most recent revision. Continued use of the service after the effective date constitutes acceptance of the revised policy.

10. Contact

For privacy enquiries, data subject requests, or questions about this policy:

• Use the contact form — select "Privacy / legal" as the subject.
• We aim to respond to all privacy requests within 5 business days and to complete them within 30 days.