FAQs
FAQs
The most-asked questions about AIRegistra. Use the headings below as anchors — Cmd-F / Ctrl-F finds anything fast for ~15 entries.
If your question is not here, write to hello@airegistra.com. We update this list as questions land.
Pricing & billing
How does pricing work?
AIRegistra is per seat, per month, paid monthly. Two rates:
- €4.99 / user / month for design partners — the first ~30 customers via the
DESIGN30promo code, locked for 12 months from signup. - €7.99 / user / month standard — for everyone after the design-partner cohort closes.
The product is identical at both rates. There are no per-module licences and no enterprise tier in v1. Add or remove seats anytime via the self-service billing portal — proration runs automatically. Cancel anytime. See the full pricing page for the FAQ-grade detail.
What’s the design-partner discount?
The first ~30 design-partner seats lock at €4.99 per user per month for 12 months from signup, in exchange for honest feedback, willingness to be a reference, and a monthly call (or on-demand). The discount ends at month 13 — you roll to the standard €7.99 rate unless we have re-negotiated. The cohort is fixed at ~30; once closed, the design-partner rate is closed.
What happens at the end of the trial?
The trial is 30 days. Payment method is required at signup but you are not charged until day 31. If you cancel before day 31 you are never charged. If you do nothing, the subscription auto-converts on day 31 at your locked rate. You always have access to the self-service billing portal to cancel, change seats, or update payment.
Can I get a refund?
Payments are processed by a PCI-compliant third-party processor and the subscription is monthly. The simplest path is to cancel from the Customer Portal — you keep access until the end of the current billing period and are not charged again. If you have a specific issue (mistaken charge, account compromise, billing error), email hello@airegistra.com and we will sort it out individually.
Security & data
Where is my data stored?
Application data is stored on EU-region cloud infrastructure: a managed document database for application data, and managed object storage for uploaded files (snapshots, evidence documents). A small number of webhooks (billing, transactional email) transit through US-region serverless functions, but the application data itself stays in the EU. Full detail in the privacy policy.
Who can see my AI inventory?
Only members of your organisation, plus AIRegistra’s operations admins for support purposes. Cross-org access is enforced at the platform-rules layer — users authenticate with Google, and every read or write is gated by membership in the relevant orgs/{slug}/members/{uid} document. We don’t have an “anyone with a link” sharing model in v1.
Is my data used to train AIRegistra’s models?
No. AIRegistra does not train AI models. The product uses LLMs at two specific points (vendor classification during billing-CSV import, and evidence-summary suggestions) and those calls go to commercial LLM providers under their standard data-processing agreements — typically zero-retention or short-retention windows that exclude your data from any training corpus.
What about GDPR?
AIRegistra is a Mindysm OÜ product, incorporated in Tallinn, Estonia. We process personal data as a controller (waitlist, account holders) and as a processor (your team’s data within your org). We have GDPR-required documentation (records of processing activity, processor list, sub-processor list, breach notification process). The privacy policy is the canonical reference. For DPA requests, email hello@airegistra.com.
EU AI Act
Do I need this if I’m not in the EU?
If you have any users, customers, or operations in the EU, the Act likely reaches you — its territorial scope (Article 2) is broader than EU establishment alone. If you have an EU subsidiary, EU customers buying your AI-enabled product, or EU staff using AI tools for company work, the Act applies in some form. Outside that, you may still be reached indirectly by procurement: EU customers asking to see your AI usage policy is becoming common.
If you have zero EU exposure today, the Act is not a direct obligation but the framework AIRegistra implements (inventory + policy + training + evidence) is broadly applicable to other regulatory regimes (Colorado AI Act, NYC AI hiring law, NIS2, sector-specific rules) — it is not EU-only governance.
What if my company is small?
There is no SME carve-out in the Act. A 10-person company using AI tools has the same Article 4 obligation as a 1000-person company. The proportionality clause adjusts the depth of training, not the obligation itself. Practically, smaller companies have less surface area to govern, so getting compliant is faster — not slower — than at enterprise scale.
How do I know if I’m a Provider or a Deployer?
Most mid-market companies are deployers — they use AI tools their team adopted. SaaS companies that ship AI features in their product are usually both providers and deployers. The role declaration article walks through the decision tree with examples and edge cases.
What’s the deadline?
2 August 2026 is the date everyone references. That is when most of the Act’s substantive obligations start applying and when penalties under Article 99 become enforceable. Article 4 (AI literacy) technically already applied from 2 February 2025, but with no penalty teeth. The full timeline is in the key deadlines article.
Product
How do I import my AI tools?
Three ways: CSV from billing (most common billing-platform exports plus a generic CSV format), employee survey link (one-question survey to staff to surface shadow AI), and manual entry. The CSV importer auto-classifies known vendors and asks you to review unknowns. The fastest first import is your last month’s billing CSV.
Can I track AI features in my own product?
Yes. The Tool Register treats AI features your company builds the same as AI tools your company uses. If you call OpenAI / Anthropic / Mistral from your product, register that as a tool with a “we are the provider” tag. The EU AI Act readiness checklist will surface the matching provider obligations once you declare both Provider and Deployer roles.
What integrations do you have?
In v1: CSV imports from common billing platforms, transactional email for invitations and notifications, Google sign-in, self-service billing, and cached ECB rates for multi-currency normalisation. Direct billing-platform connectors (replacing CSV imports), chat-based notifications (Slack first), and enterprise SSO are on the roadmap for v1.x.
Have a question that isn’t covered here? Write to hello@airegistra.com. Every email goes to the team — there is no support tier wall in v1.
8 min read · Last updated