Privacy
Aprex.no has two places where you can send information: the contact form and the AI conversation in Studio. This page explains exactly what each of them sends, where it ends up, who processes it on behalf of Aprex, and what you can demand.
Last updated: September 21, 2026
The form sends your email address and message, both required, plus name and company if you fill them in. Three technical details from the request travel with it: the address the form was submitted from, your IP address, and your browser user agent. All of it is sent as a single email to post@aprex.no with your address as the reply-to. Nothing else on the site stores it.
What you write is sent to the Vercel AI Gateway, which forwards it to the language model Aprex uses. The messages are not stored in any Aprex database. The per-turn server log holds only counters and categories - which topic the conversation locked onto, which phase it is in, how many turns and signals were recorded - not what you actually wrote.
If you choose to hand the case over from Studio, your email address, any company name, the summarised case and the last twelve messages are sent as email to post@aprex.no. You receive a copy at your own address at the same time. This only happens when you press it yourself - the conversation is never forwarded automatically.
The site runs on Vercel, which also provides the AI gateway the conversation passes through, the bot protection on the API routes, and a cookieless visitor measurement. The language model is provided by Anthropic through that gateway. Email to and from post@aprex.no is handled by the provider running Aprex’s domain mail. Aprex uses no ad networks, tracking pixels or third-party analytics on the site.
Enquiries are processed to answer you and, where relevant, to prepare an agreement, under GDPR Article 6(1)(b). Technical information such as IP address and user agent, along with rate limiting and bot protection on the API routes, rests on the legitimate interest in keeping the service available and preventing abuse, under Article 6(1)(f).
Enquiries stay in the Aprex mailbox for as long as they are needed to follow up the conversation or the customer relationship, and are deleted once they are not. You can ask for deletion at any time by writing to post@aprex.no. The rate-limiting counter lives only in server memory and resets continuously; it is not stored.
You can request access to the information Aprex holds about you, have it corrected or erased, ask for processing to be restricted, object to the processing, and receive the information you provided in a portable form. Send the request to post@aprex.no. If you believe the processing breaches the rules, you can complain to the Norwegian Data Protection Authority.
Describe the workflow, the systems and the problem, but do not send passwords, health data, national identity numbers or confidential information about customers and employees through the form or the AI conversation. If Aprex is to process such data in a project, that is agreed separately with a data processing agreement.
Security, AI use and terms are all connected to how information is handled.
No. The conversation is sent to the AI gateway to generate a response, but is not stored in any Aprex database. The server log holds only categories and counters, not message content.
It travels with the email from the contact form, and is used in memory for rate limiting the API routes. It is not stored in any database.
Aprex sets no tracking cookies. The visitor measurement on the site is cookieless, and no ad networks or third-party analytics are used.
Send an email to post@aprex.no describing what you want. Aprex responds within the deadlines set by the GDPR.
Write to post@aprex.no and Aprex will answer specifically for your case.
Contact Aprex