VitaGate — Privacy
In one paragraph
VitaGate runs entirely inside Atlassian. It reads the Jira work items and Confluence pages you can already see, as you, and shows you what they say with a link to each source. It sends nothing to any server outside Atlassian, because it has no permission to: the app declares no external domains, so the platform would refuse the attempt. It stores almost nothing, and none of what it stores is about a person.
Who we are
- Legal name
- VitaMedas, Inc.
- Commercial name
- Graviti Labs
- Registered office
- 2261 Market Street STE 69554, San Francisco, CA 94114, United States
- State of incorporation
- Delaware
- Contact
- [email protected]
Your Atlassian site remains the controller of the content in it. For the limited data described below, we are the controller.
What VitaGate reads
When you open the panel on a work item, or ask the Rovo agent about a change, the app reads:
- that Jira work item, and the web links on it;
- the Confluence pages those links point at, and pages reached by following links out of those pages, to a maximum of three hops and sixteen pages;
- your Atlassian account identifier, used only to address the Teamwork Graph query for the current request. It is never written anywhere.
Every one of these calls is made as you, using your own Atlassian permissions. VitaGate cannot read a document you could not open yourself. If you lose access to a page, the app loses access to it at the same moment.
It reads documents only when a person asks it to. There is no background crawl, no scheduled job and no indexing of your site.
What VitaGate stores
In the Atlassian Forge key-value store, inside your own Atlassian site:
- The Teamwork Graph connection identifier, if an administrator connects the connector. This is an identifier Atlassian issues; it identifies a connection, not a person.
- A record of what the demonstration seeder created — the space key and id, the Jira project key, the three issue keys and a timestamp — so that running it again reuses what is there instead of making duplicates.
That is all. VitaGate does not store the content of your documents, the dossiers it assembles, your questions, or anything identifying a person. There is no database outside your Atlassian site, because there is no server outside your Atlassian site.
What VitaGate writes
Only when you press a button, and never otherwise:
- “Record that this is awaiting determination” writes one object to your site's Teamwork Graph: the change key, its summary, a count of how many cited obligations were assembled from how many documents, and a link back to the work item. It does not write a regulatory determination, because the app does not make one. The app can also update and delete objects it has written, and nothing else.
- The demonstration seeder, on the administration page, creates one Confluence space, seven pages and three Jira work items. It runs as the signed-in administrator, so every object is attributed to that person; it never alters anything that already exists.
Artificial intelligence
The Rovo agent runs on Atlassian's own AI platform under Atlassian's terms. Your content is sent to Atlassian, not to us and not to any third party we have chosen. We do not train any model on your content, and we have no model to train.
Logging
The app writes diagnostic lines to Atlassian's Forge logging, which only you and the app's contributors can read, and only for sites that have log access sharing enabled. These lines record events such as whether a connector change carried an identifier. They never contain the identifier itself, document content or anything about a person.
Sub-processors
None. VitaGate has no external service, no analytics, no error reporting service and no content delivery network of its own. Atlassian processes everything, as the operator of the platform the app runs on and of your site.
International transfers
The app does not move data between regions. Your content stays wherever Atlassian hosts your site, under Atlassian's own data residency arrangements.
Retention
The two stored items above persist until the app is uninstalled, at which point Forge deletes the app's storage. Documents, work items and Teamwork Graph objects belong to your site and are governed by your own retention settings.
Your rights
Because VitaGate holds no personal data of its own, a request about your personal data is properly directed to Atlassian or to your site administrator, who control the content. Write to [email protected] and we will help you identify the right route, and delete the app's stored records on request from a site administrator.
Security
The app holds no credentials of its own and no secrets in its code. It has no network egress permission. Every product call it makes carries the acting user's authority, so the app's reach is bounded by that person's permissions rather than by our own promises.
Changes
Material changes will be published on this page with a new version number and effective date.