Appearance
Cookies, Privacy & Terms
Relewise ApS is committed to protecting your privacy. This documentation website is primarily a static site, but it also includes an Ask AI chat where visitors can submit questions. The data we collect are:
- Essential technical logs kept by our web server (e.g., IP address and user-agent for security and troubleshooting).
- Ask AI service data including a first-party User ID used for abuse prevention and rate limiting, and temporary conversation snapshots when visitors use the Ask AI sharing feature.
- Google Analytics usage statistics only if you consent to analytics cookies.
We do not use advertising cookies, fingerprinting, or any other third-party trackers, and we never sell or rent personal information.
Note: Privacy terms for the Relewise SaaS platform (API, dashboard, etc.) are covered separately in our Data Processing Agreement.
Our Use of Cookies
Last updated May 29, 2026
| Cookie type | Purpose | Default status |
|---|---|---|
| Essential | Operate and protect the site (e.g., load-balancer session cookie, security logs, Ask AI abuse-prevention User ID). | Always on |
| Analytics (Google Analytics) | Anonymous usage statistics—page views, referrers, time on page. | Set only after consent |
You will see a cookie banner the first time you visit. You can accept or decline analytics cookies, and you may change your choice at any time by clicking the button below or by clearing cookies in your browser.
Privacy Policy
Last updated May 29, 2026
1. Who We Are
Relewise ApS
Trindsøvej 8, 1st floor,
DK-8000 Aarhus C, Denmark
2. What Data We Process on This Site
| Category | Examples | Legal basis | Retention |
|---|---|---|---|
| Technical & security logs | IP address (may be truncated), browser type, timestamp, requested URL | Legitimate interest (site security & performance) | ≤ 2 years |
| Analytics data (only if cookies accepted) | Aggregated page-view statistics, approximate geo-region (city level), device type | Consent (Art. 6 (1)(a) GDPR) | Up to 26 months (Google Analytics default) |
| Ask AI service identifier | First-party pseudonymous User ID used for abuse prevention and rate limiting of Ask AI requests | Legitimate interest (Art. 6 (1)(f) GDPR) | Up to 13 months |
| Ask AI shared conversation snapshots | Conversation message text and safe rich response content stored only when a visitor creates a share link | Legitimate interest (Art. 6 (1)(f) GDPR) | Until the share link expires |
3. How We Use the Data
- Security & integrity: Detect abuse or technical faults.
- Ask AI abuse prevention: Protect the Ask AI endpoint against misuse and enforce rate limits.
- Ask AI sharing: Store a temporary conversation snapshot when a visitor creates a share link.
- Usage insights: Improve documentation structure and content (analytics, consent-based).
We never use data from this site for advertising or profiling.
4. Sharing and International Transfers
- Google Analytics (USA): Processes analytics data on our behalf under EU Standard Contractual Clauses.
- Hosting provider (EU): Stores server logs in EU data centers.
- Ask AI endpoint: Maintained and operated by Relewise (not a third-party endpoint).
We do not otherwise disclose data unless required by law.
5. Your Rights
Where the GDPR or similar laws apply, you can request: access, erasure, restriction, objection, and data portability for information derived from your use of this site. To exercise rights, email our DPO (see “Contact Us”).
6. Children
This site is not directed to children under 18 and we knowingly collect no data from them.
7. Changes
We may update this notice; the “Last updated” date will change accordingly.
8. Contact Us
Data Protection Officer
Brian Holmgård Kristensen
📧 bhk@relewise.com
Agent Gateway and AI Integrations
Last updated September 16, 2026
This section supplements the Relewise Data Processing Agreement and explains how Agent Gateway handles data when an AI assistant, automation tool, or external application connects to Relewise.
Credentials and Access
Agent Gateway supports OAuth Connected Apps and Personal Access Tokens for REST and MCP connections. OAuth-capable clients manage credentials through Connected Apps. Clients that do not support OAuth, including the Relewise Agent Plugins CLI and its direct REST fallback, use a Personal Access Token stored in the client's secure credential storage or another secure secret store.
Relewise does not place credential values in prompts, tool results, or Agent Gateway Request Logs. Credentials are not stored in the public Relewise Agent Plugins repository. Users must not paste Personal Access Tokens into an AI conversation, command argument, repository file, log, or transcript.
Agent Gateway checks the authenticated user's permissions, the credential's Dataset access, the Dataset's Agent Gateway configuration, the connection method, and the allowed area for every request.
Requests and Returned Data
When a connected client invokes Agent Gateway, it sends the requested operation and its parameters to Relewise. This can include a Dataset ID and identifiers, filters, or other values needed to complete the operation. Agent Gateway may return Dataset or customer data that the authenticated user and the applicable Dataset and area policies allow the client to access.
Data returned to the client is also handled under the AI provider's or other client's own privacy, retention, and model-training policies. Review those policies before connecting the client or requesting sensitive data.
Request Logs and Retention
Relewise records metadata about authenticated Agent Gateway requests for security, auditing, and troubleshooting. The metadata can include the user, credential or Connected App reference, time, outcome, area, action, connection method, HTTP method, path, Dataset ID, and failure reason. Request Logs do not contain credential values, request bodies, response bodies, or the Dataset data returned by an operation.
Agent Gateway Request Logs are automatically deleted after 90 days, unless Relewise must preserve specific records for an active security investigation or to meet a legal obligation.
Disconnect or Revoke Access
Users can disconnect a Connected App in My Relewise. Personal Access Tokens can be revoked permanently or regenerated, which immediately invalidates the previous token value. Changes to user permissions, Dataset access, and Agent Gateway configuration also apply to existing connections.
Read the Agent Gateway documentation, Security and Permissions, Connected Apps, Personal Access Tokens, and Request Logs for configuration and access-control details.
Terms of Use
Last updated February 19, 2026
- Acceptance – By using this site you agree to these Terms.
- Intellectual Property – All content is © Relewise ApS. Non-commercial use is permitted; commercial reproduction requires written permission.
- Permitted Use – No unlawful, malicious, or automated scraping.
- No Warranty – Site provided "as is"; accuracy not guaranteed.
- Limitation of Liability – Relewise is not liable for indirect or consequential damages.
- Governing Law – Danish law; non-exclusive jurisdiction in Aarhus, Denmark.
For questions about these Terms, email hello@relewise.com.