✓ GDPR Compliant

Privacy Policy

Rivoryn Limited, trading as AICVS · Last updated: 1 March 2026 · Effective: 1 March 2026

Plain English summary: We scan your code to check compliance, but we never store your source code. Only the scan result and a cryptographic hash are saved. You are always in control of your data. We are GDPR-compliant and process all data within the EU.

Contents

  1. Who we are
  2. What data we collect
  3. How we use your data
  4. Legal basis for processing
  5. Your source code — special handling
  6. Who we share data with
  7. How long we keep data
  8. Your GDPR rights
  9. Cookies
  10. Security measures
  11. International transfers
  12. Children's privacy
  13. Changes to this policy
  14. Contact us

1. Who we are

Rivoryn Limited (trading as AICVS) is the data controller responsible for your personal data. We are incorporated in Ireland and process all data within the European Union.

2. What data we collect

Account data

Usage data

Payment data

Payments are processed by Stripe. We store only your Stripe customer ID — we never see or store your full card details. Stripe's Privacy Policy applies to payment processing.

What we do NOT collect

3. How we use your data

PurposeData usedLegal basis
Providing the AICVS serviceAccount data, scan resultsContract performance
Authentication and securityEmail, IP, event logsLegitimate interest
Billing and subscription managementEmail, Stripe customer IDContract performance
Service improvement (aggregated, anonymous)Scan statisticsLegitimate interest
Legal compliance and auditEvent logs, audit trailLegal obligation
Customer supportEmail, account dataContract performance

We process your personal data only where a lawful basis under GDPR Article 6 applies. We rely on the following lawful bases:

5. Your source code — special handling

Critical commitment: Your source code is never stored on our servers. When you upload a file, it is read into memory, analysed, then the raw code is immediately discarded. We store only the scan result (score, findings, a SHA-256 hash of the file). This means we cannot reconstruct your source code from our records — and we never could.

The SHA-256 hash stored serves as proof that a specific file was scanned at a specific time, without revealing the code's content. This is a core architectural choice — not just a policy.

6. Who we share data with

RecipientPurposeLocationSafeguard
SupabaseDatabase hostingEU (Frankfurt)DPA in place
StripePayment processingUSA (EU SCCs)Standard Contractual Clauses
Render.comAPI hostingEU (Frankfurt)DPA in place
VercelFrontend hostingEU CDN edgeDPA in place

We do not sell, rent, or trade your personal data. We do not share data with advertisers.

7. How long we keep data

Data typeRetention periodBasis
Account dataDuration of account + 30 days after deletionContract
Scan results24 months (or until you delete them)Service provision
Compliance bundles24 monthsService provision
Security audit logs90 daysSecurity / legal
Financial records7 yearsIrish tax law
Source code files0 days — discarded immediatelyPrivacy by design

8. Your GDPR rights

Under GDPR, you have the following rights. To exercise any of them, email privacy@aicvs.io. We will respond within 30 days.

9. Cookies

We use only essential, functional cookies. No advertising, tracking, or analytics cookies are used.

CookiePurposeDuration
aicvs_sessionMaintains your login session (JWT refresh)30 days
aicvs_prefsUI preferences (theme, settings)1 year

We do not use Google Analytics, Facebook Pixel, or any third-party tracking scripts.

10. Security measures

11. International transfers

We primarily process data within the EU. Stripe processes payment data in the USA — this transfer is governed by Standard Contractual Clauses (SCCs) approved by the European Commission under GDPR Article 46(2)(c).

12. Children's privacy

AICVS is a professional developer tool. We do not knowingly collect data from individuals under 16. If you believe we have inadvertently collected data from a minor, please contact us immediately at privacy@aicvs.io.

13. Changes to this policy

We will notify registered users by email at least 14 days before any material changes 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 updated policy.

14. Contact us

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

We aim to respond to all privacy requests within 72 hours and resolve them within 30 days as required by GDPR Article 12.