← Back to home
LiveAPISec

Privacy Policy

Effective Date: 08 Aug 2026 · Version: 2026-08-08

This Privacy Policy explains how Loquen Lab LLC (“LiveAPISec”, “we”, “us”, “our”) collects, uses, retains, protects, and discloses information relating to users (“you”) of the LiveAPISec Platform (“Platform”). By accessing or using the Platform you consent to this Policy. If you disagree, discontinue use.

1. Data Controller / Contact

Loquen Lab LLC is the data controller for processing described herein.

Privacy inquiries: [email protected]

Legal / compliance: [email protected]

2. Categories of Data Collected

We may process the following categories (depending on your interactions):

CategoryExamplesRequired?
Account IdentifiersInternal user ID, username, auth provider IDYes (core usage)
ContactEmail (if provided by identity provider)Conditional
Technical / UsageIP address, timestamps, user agent, logs, feature flags, error tracesYes (security & diagnostics)
BillingSubscription plan, payment status, transaction metadata (no full payment card PAN stored)Conditional (if using paid plan)
API / Scan DataOpenAPI specs, base URLs, credentials metadata, scan results, security findings, Trust Page dataConditional (if using scanning features)
CredentialsAPI keys, tokens, and secrets used to authenticate scans — encrypted at rest (AES-256), never logged in plaintextConditional
AI Prompt / OutputText submitted to AI-assisted triage/interpretation + generated analysis (may undergo transient logging)Conditional
Booking / DemoName, email, chosen time slot and timezone when you book a demoConditional
Support / FeedbackTickets, emails, form submissions, session notesConditional

Sensitive categories (e.g., government IDs, health data) are neither required nor intentionally collected. Do not submit them.

3. Sources of Data

  1. Direct input (account setup, profile edits, OpenAPI specs, Target API configuration).
  2. Authentication provider (OIDC / OAuth claims via Clerk).
  3. Automatic collection (logs, metrics, security tooling).
  4. Target APIs (responses collected during authorized scans).
  5. Voluntary user messages or feedback.
  6. Payment / billing processors (transaction tokens, status from Stripe).
  7. AI feature interactions (prompts, completions) processed via integrated model providers (OpenRouter).

4. Purposes of Processing

PurposeLegal Basis
Provide core Platform featuresContract necessity
Account & session securityLegitimate interest / Contract
Billing & subscriptionsContract necessity
Abuse, fraud & moderation controlsLegitimate interest
Analytics & performance tuning (aggregate)Legitimate interest (minimal / pseudonymized)
Legal compliance & enforcementLegal obligation / Legitimate interest
AI analysis & recommendationsContract necessity / Legitimate interest
User communications & supportContract necessity / Legitimate interest
Marketing (if opted-in)Consent

5. Legal Bases (Summary — EEA / Similar Regimes)

Where required by data protection laws we rely on: performance of contract, legitimate interest (balanced test maintained), legal obligation, or consent (for optional communications). We avoid relying on consent when another lawful basis is more appropriate.

6. Data Minimization & Retention

We keep personal data only for as long as needed:

Data TypeRetentionNotes
Account & profileLife of account + short grace (≤90 days)Basic identifiers
Logs (standard)30–180 daysSecurity, diagnostics, aggregated thereafter
Scan results & findingsLife of account + ≤90 daysNeeded for Trust Page history
CredentialsUntil deleted by user or account terminationEncrypted at rest (AES-256)
Billing records7–10 years (jurisdictional accounting)Required for audit
AI prompts/output logs≤30 days (service improvement / abuse)May be aggregated earlier
Booking / demo dataUntil deleted by user or retention policyBooking confirmation + reminders
BackupsRolling cycles (e.g., 30–60 days)Encrypted at rest

Upon expiry we delete or irreversibly anonymize.

7. Security Measures

Controls include: transport encryption (TLS), role-based access, least privilege, audit logging, anomaly detection, secret management (AES-256 encryption for credentials), routine patching, segregated environments, encryption at rest for key data stores, and sandboxed scanning with strict pacing and request caps. No system is perfectly secure; report suspected issues to [email protected].

Credentials you provide for scans are encrypted at rest and never logged in plaintext. You are responsible for only providing credentials you are authorized to use and for keeping them accurate. We are not liable for unauthorized access to your Target APIs caused by your credentials, their exposure, or misconfiguration on your side.

8. Data Sharing & Disclosures

We do NOT sell personal data. We may share with:

  • Infrastructure & hosting providers (cloud, CDN).
  • Payment processors (Stripe — processing subscription payments).
  • AI model providers (OpenRouter — processing AI prompts and generating responses).
  • Analytics / monitoring (aggregated telemetry).
  • Authentication provider (Clerk — identity verification).
  • Moderation / security tooling (threat detection).
  • Professional advisors (legal, accounting).
  • Authorities when legally required or to protect rights, safety, or comply with law.

Public Trust Page: if you enable the public certificate for an organisation, the organisation name, overall status, and aggregate scan data (open/fixed counts, last scan, statement) become publicly visible at the certificate URL and via our embed widgets. Do not enable it if you do not want this information public. You are responsible for how you present and share the certificate.

Third parties are bound by contractual obligations (data processing agreements) where required.

9. International Transfers

Where data moves outside your jurisdiction we implement appropriate safeguards (e.g., Standard Contractual Clauses, transfer risk assessments). Additional measures (encryption / pseudonymization) may be applied.

10. AI & Automated Processing

AI features may analyze scan findings and produce triage, severity suggestions, and interpretations. We do not use your private scan data to publicly train models without consent. Limited human review may occur for abuse detection or quality evaluation under confidentiality obligations. No solely automated decision produces legal or similarly significant effects without recourse. The deterministic core scanner remains the source of truth.

11. Cookies & Similar Technologies

We primarily rely on essential session tokens and minimal local storage for preference or anti-abuse markers. Non-essential marketing / tracking cookies are not currently deployed. If adopted, a separate consent banner will describe categories and preferences.

12. Your Rights (Subject to Jurisdiction)

Rights may include: access, rectification, erasure, restriction, objection, portability, withdrawal of consent (prospective), complaint to supervisory authority, opt-out of certain processing.

Exercise via [email protected] (we may need to verify identity). Responses typically within 30 days.

13. Children

The Platform is not directed to children under 16 (or lower age defined locally). We do not knowingly collect such data. If you believe a child provided information, contact us for removal.

14. Third-Party Links / Integrations

External links or plugins operate under their own policies; review them separately. We disclaim responsibility for third-party practices.

15. Data Breach Procedure

We maintain incident response playbooks. In the event of a breach impacting personal data, we will notify affected users and/or authorities in accordance with applicable law (content: nature, categories, mitigation steps, contact).

16. Aggregated & Anonymized Data

We may aggregate or anonymize data for statistical insights (performance metrics, adoption trends). Such information no longer constitutes personal data.

17. Automated Communications

Transactional or security emails (e.g., password reset, booking confirmation, policy acceptance, moderation) are mandatory. Optional marketing requires prior consent and includes an opt-out mechanism.

18. California / Regional Addenda

If required (e.g., CCPA / CPRA), additional disclosures (categories sold/shared = none, right to limit use of sensitive information = not applicable presently) may be published as an Addendum.

19. Changes to this Policy

Revisions will carry a new “Effective Date”. Material changes may trigger re-acceptance. Maintain awareness by checking periodically.

20. Contact

Loquen Lab LLC

418 Broadway STE N, Albany

Albany County, New York 12207 USA

Privacy & data rights: [email protected]

Security: [email protected]

Legal notices: [email protected]

By continuing to use the Platform you acknowledge you have read and understood this Privacy Policy.