Link-a-LinkTrust Centre
Everything you need to know about how Link-a-Link handles your data, secures our infrastructure, and governs your use of the plugin — in one place.
Link-a-Link was architected from the ground up to avoid personal data entirely. We do not log user account IDs, names, email addresses, or search queries.
What's in the Trust Centre
Privacy & Data — Our complete Privacy Policy and GDPR Compliance Statement. What we process, what we don't, where it lives, how long it's kept, and how to delete it.
Security — Our responses to Atlassian's Partner Security Questionnaire. Covers infrastructure security, development practices, workstation hardening, vulnerability management, and incident response.
End User Agreement — The legal terms that govern your installation and use of the Link-a-Link plugin.
Key facts at a glance
| Topic | Summary |
|---|---|
| Personal data collected | None — no names, emails, account IDs, or search queries |
| Hosting platform | Atlassian Forge (serverless, Atlassian-managed) |
| Mapping data location | AWS S3 in eu-west-1 (Ireland, European Union) |
| Encryption | AES-256 at rest, TLS 1.2+ in transit |
| Tenant isolation | Application-layer + Forge platform-layer + S3 IAM |
| Admin-initiated deletion | Permanent, immediate, audit-logged |
| Governing law | England and Wales |
| Privacy enquiries | [email protected] |
Version 1.0 · Effective date: 08 April 2026 · Governed by UK GDPR / EU GDPR
About This Policy
Our Privacy Policy and GDPR Compliance Statement in one document.
This Privacy Policy describes how Agilva Solutions ("we", "us", "our") processes information in connection with the Link-a-Link plugin for Confluence Cloud ("the Plugin", "the App"). It also constitutes our GDPR Compliance Statement, demonstrating how Link-a-Link is designed to meet the requirements of the UK General Data Protection Regulation (UK GDPR) and the EU General Data Protection Regulation (EU GDPR 2016/679).
Link-a-Link is built on the Atlassian Forge platform and distributed through the Atlassian Marketplace. Its core architecture is intentionally privacy-preserving: the Plugin does not collect, store, or transmit any personal data about individual users. This policy explains precisely what data is handled and why.
Link-a-Link was architected from the ground up to avoid personal data entirely. We do not log user account IDs, names, email addresses, or search queries. Our Support Report feature is specifically engineered to contain zero personal data.
Data Controller
Who we are and how to contact us regarding data protection matters.
The data controller for any data processed in connection with Link-a-Link is:
| Entity | Agilva Solutions |
| Product | Link-a-Link (Confluence Cloud Plugin) |
| Marketplace | Atlassian Marketplace |
| [email protected] | |
| Website | https://www.agilva.com |
| App ID | ari:cloud:ecosystem::app/2648f02d-fd21-4ca2-aaec-a893d28bf3c9 |
Scope & Application
Which features and which users this policy covers.
This policy applies to all users and administrators of the Link-a-Link plugin installed within a Confluence Cloud workspace. It covers both features of the Plugin:
- Confluence Mapping — the feature that allows administrators to upload migration CSV files and enables users to search for old Data Centre page URLs or PageIDs and retrieve the corresponding Confluence Cloud equivalents.
- IntellinQ — the feature that allows administrators to configure document-numbering prefix systems, and enables editors to insert IntellinQ macros on Confluence pages that resolve document numbers into full URLs.
This policy applies in all countries where Confluence Cloud is used with Link-a-Link installed, including all EU/EEA member states and the United Kingdom.
Data We Do Not Collect
Categories of personal data that Link-a-Link never touches.
Link-a-Link is deliberately designed to avoid collecting personal data. The following categories of data are never collected, stored, or transmitted by the Plugin:
| Category | Examples | Collected? |
|---|---|---|
| User identifiers | Account IDs, names, usernames | Never |
| Contact information | Email addresses, phone numbers | Never |
| Search query content | What users typed in the search box | Never |
| Page content | Titles, body text, attachments | Never |
| Authentication data | Passwords, tokens, session IDs | Never |
| Device information | Browser type, IP address, OS | Never |
| Behavioural analytics | Clicks, scroll depth, time on page | Never |
| Location data | GPS, IP-derived location | Never |
| Communication data | Confluence comments, messages | Never |
Data We Process
A detailed breakdown of every data type the Plugin handles.
Link-a-Link processes a minimal set of non-personal, technical and operational data. The following table sets out each data type, where it is stored, and its purpose.
| Data type | What it contains | Stored where |
|---|---|---|
| URL mapping index | Old DC URLs or PageIDs mapped to new Cloud URLs — no page content, no personal identifiers | AWS S3 (eu-west-1) + Forge Storage |
| IntellinQ system configuration | System name, URL prefix, base URL. No user data of any kind | Atlassian Forge Storage |
| Macro document number | The document number saved per macro instance (e.g. PDL-423). No author or viewer info | Atlassian Forge Storage |
| Admin settings | Plugin preferences such as redirect timer duration. No personal data | Atlassian Forge Storage |
| Aggregate search counters | Total searches performed, total found, total not-found — as integers only. No query strings | Atlassian Forge Storage |
| Audit log (uploads) | Upload timestamps, file row count, processing status. No filenames, no user IDs | Atlassian Forge Storage |
| Error event log | Technical error type, message, component name. Maximum 30 entries, FIFO rotation | Atlassian Forge Storage |
| S3 presigned upload metadata | Tenant-scoped S3 object key and expiry timestamp. No personal data | AWS S3 (eu-west-1) |
Forge Platform
Link-a-Link runs entirely on Atlassian's hosted serverless infrastructure.
Link-a-Link is built exclusively on the Atlassian Forge platform. Forge is Atlassian's hosted serverless runtime for Confluence and Jira apps. This has important privacy implications:
- Forge manages all infrastructure. Agilva Solutions does not operate any servers, virtual machines, or databases for the core Plugin functionality. All Forge Storage data (IntellinQ systems, settings, counters, logs) is stored and managed entirely within Atlassian's infrastructure.
- Agilva Solutions has no direct access to Forge Storage data. We cannot query, export, or read individual tenants' Forge Storage data outside of the Plugin's own resolver functions. There is no administrative backdoor or database console.
- Atlassian acts as a Data Processor for data stored in Forge Storage, subject to Atlassian's Privacy Policy and their Data Processing Addendum. Agilva Solutions acts as the Data Controller for determining what data is stored.
- Forge enforces tenant isolation. The Forge platform prevents one tenant's storage data from being accessible by another tenant's app instance at the platform level, in addition to our own application-level isolation.
Because IntellinQ configurations and all plugin settings are stored in Forge Storage, this data is subject to Atlassian's data residency and security controls. For enterprise data residency requirements, refer to Atlassian's Data Residency documentation at atlassian.com/trust/data-residency.
AWS Infrastructure
The Confluence Mapping feature stores URL index data in AWS S3 within the European Union.
| Component | Detail |
|---|---|
| AWS Region | eu-west-1 (Ireland, European Union) |
| S3 Bucket | link-a-link-storage-eu (private, no public access) |
| Lambda Function | link-a-link-processor (eu-west-1) |
| Data stored in S3 | Sharded index files containing old→new URL pairs only. No personal data |
| Upload mechanism | Pre-signed S3 PUT URL valid for 15 minutes. File is processed then retained as index |
| Encryption | S3 server-side encryption (SSE-S3) at rest. TLS in transit |
| Sub-processor | Amazon Web Services EMEA SARL (AWS) — subject to AWS Data Processing Addendum |
Tenant Isolation
How Link-a-Link guarantees that one workspace's data never touches another's.
Link-a-Link is a multi-tenant application. Every workspace that installs the Plugin receives a completely isolated data environment. Data belonging to one Confluence workspace can never be accessed by, mixed with, or exposed to any other workspace.
This isolation is implemented at three independent layers:
- Application layer — Every Forge Storage key used by the Plugin is namespaced with the workspace's unique
tenantId(e.g.searchStats-{tenantId},smartLinks-{tenantId}). No query or operation can read across tenant boundaries at the application level. - Platform layer — The Atlassian Forge platform enforces tenant isolation at the runtime level. A Forge app instance running for Tenant A is physically separated from the instance running for Tenant B — they cannot share storage, memory, or context.
- S3 layer — CSV upload keys and index shard files are prefixed with the
tenantIdin S3, and IAM policies ensure only the Lambda function with the correct context can access them.
Tenant isolation has been validated through the Atlassian Forge Context Token (FCT) mechanism, which ensures that each resolver invocation is authenticated to the correct workspace before any storage read or write operation takes place.
Your Right to Delete
Admin-initiated deletion is a core, prominent feature — not a support-ticket process.
Workspace administrators have the ability to permanently delete the entire Confluence Mapping dataset directly from the Plugin's admin settings panel. When an admin initiates a deletion:
- The admin clicks the "Delete all mapping data" button in the Link-a-Link settings panel.
- A confirmation prompt is displayed to prevent accidental deletion.
- Upon confirmation, the Plugin sends a deletion request to the Forge resolver.
- The resolver deletes all sharded index files from the AWS S3 bucket for that tenant.
- All associated Forge Storage keys for the mapping dataset are purged.
- The operation is recorded in the audit log (timestamp and action type only — no user ID).
- The mapping data cannot be recovered after deletion is confirmed.
When mapping data is deleted via the admin panel, it is removed from both AWS S3 and all Forge Storage index keys simultaneously. There is no backup, soft-delete, or archival copy retained by Agilva Solutions. The deletion is permanent and irreversible.
IntellinQ system deletion
To delete IntellinQ system configurations, admins use the per-system delete function in the IntellinQ admin tab. Individual systems can be removed at any time, or the entire list can be cleared. Deleted IntellinQ configurations are removed from Forge Storage immediately and permanently.
GDPR Lawful Basis
Lawful basis under UK GDPR Article 6 for each processing activity.
Under UK GDPR Article 6, processing of personal data must have a lawful basis. Because Link-a-Link does not process personal data as defined by GDPR, a formal lawful basis analysis is not strictly required. However, to the extent that any information processed by the Plugin could theoretically be characterised as personal data in any jurisdiction, we rely on the following:
| Processing activity | Lawful basis | Notes |
|---|---|---|
| Storage of URL mapping index | Art. 6(1)(b) — Performance of a contract | Necessary to deliver the core contracted service |
| IntellinQ system configuration | Art. 6(1)(b) — Performance of a contract | Required to provide the IntellinQ macro functionality |
| Aggregate search counters | Art. 6(1)(f) — Legitimate interests | Service quality monitoring. No individual data |
| Technical error logs | Art. 6(1)(f) — Legitimate interests | Security and system stability. No personal data |
| Audit log | Art. 6(1)(b) — Performance of a contract | Necessary for admin transparency. No user identifiers |
Data Subject Rights
How UK GDPR and EU GDPR rights apply in the context of Link-a-Link.
Under UK GDPR and EU GDPR, individuals have the following rights regarding their personal data. Given that Link-a-Link does not collect personal data, most of these rights are not engaged. We set out how each right applies in the context of this Plugin:
Right of access (Art. 15)
Link-a-Link holds no data attributable to individual users. There is nothing to access. Workspace-level data (URL mappings) can be inspected by admins directly in the Plugin interface.
Right to rectification (Art. 16)
URL mapping data can be corrected by the admin uploading a revised CSV. IntellinQ systems can be edited at any time in the admin panel.
Right to erasure (Art. 17)
Admins can permanently delete all mapping data via the admin settings panel (see "Your Right to Delete"). Individual IntellinQ systems can be deleted at any time. These actions take immediate effect.
Right to restrict processing (Art. 18)
The Plugin can be uninstalled at any time by a Confluence workspace admin, which terminates all processing immediately.
Right to data portability (Art. 20)
URL mapping data can be exported as CSV from the admin panel at any time. IntellinQ system configurations can be exported per-folder or in full.
Right to object (Art. 21)
Not engaged — processing is based on contractual necessity and legitimate interests. No profiling or automated decision-making takes place.
Rights related to automated decisions (Art. 22)
Link-a-Link performs no automated decision-making or profiling with legal or similarly significant effects on individuals.
International Data Transfers
Where your data lives — and what contractual safeguards apply.
The URL mapping index is stored in AWS S3 in the eu-west-1 region (Ireland, European Union). No data is transferred outside the EU/EEA in connection with the Confluence Mapping feature.
Forge Storage data is managed by Atlassian. Atlassian's data residency for Forge apps is governed by Atlassian's own policies. For customers with enterprise data residency requirements, Atlassian offers data residency controls at atlassian.com/trust/data-residency. Agilva Solutions does not make independent decisions about Forge Storage data location.
To the extent any transfers of data occur to third countries (outside the EU/EEA and UK), they are covered by the European Commission's Standard Contractual Clauses (SCCs) under AWS's Data Processing Addendum and Atlassian's Data Processing Addendum respectively.
Data Retention
How long each data type is kept, and when it's deleted.
| Data type | Retention period | Deletion trigger |
|---|---|---|
| URL mapping index (S3) | Until admin deletes it | Admin-initiated deletion (immediate) |
| URL mapping index (Forge) | Until admin deletes it | Admin-initiated deletion (immediate) |
| IntellinQ system configs | Until admin deletes them | Per-system delete or full clear |
| Macro document numbers | Until macro is deleted from page | Confluence page or macro deletion |
| Aggregate search counters | Indefinite (anonymous integers) | App uninstall |
| Audit log entries | Indefinite, max 30 per tenant | FIFO rotation or app uninstall |
| Error event log | Max 30 entries (FIFO rotation) | Auto-rotated on each new entry |
| Admin settings | Until admin changes or uninstalls | App uninstall |
| App uninstall | All Forge Storage data purged by Atlassian within 30 days. AWS S3 mapping data purged within 60 days. | |
Contact
How to reach us regarding privacy, security, or licensing matters.
| Organisation | Agilva Solutions |
| Plugin | Link-a-Link for Confluence Cloud |
| Privacy enquiries | [email protected] |
| Security enquiries | [email protected] |
| Legal / licensing | [email protected] |
| Product support | Customer Support Portal |
| Website | https://www.agilva.com |
| Marketplace | marketplace.atlassian.com (search: Link-a-Link) |
Privacy Policy version 1.0 · End User Agreement version 1.0 · Effective date: 08 April 2026 · Last updated: 08 April 2026 · © 2026 Agilva Solutions. All rights reserved.