Privacy policy

Pever answers questions about an organization from its own documents, meetings, tickets and code, with citations. This policy explains what Pever collects, how it is used and protected, and how to have it deleted. It covers the app at app.pever.si, this website, and Pever's connections to other services such as Google Drive and Linear.

Pever is built and operated by an independent developer. Questions about this policy go to hello@pever.si.

What we collect

How we use it

We do not sell your data, do not use it for advertising, and do not use your organization's content to train AI models.

Who can see your content

Each organization's data is kept separate from every other organization's. Inside an organization, a person can only search and read documents in the projects they have been given access to, and this is enforced in the database for every search. Administrators of your organization decide who belongs to it and which projects each person can see.

The developer operating Pever does not read your organization's content, except when you ask for help with a specific problem, when needed for security or abuse investigations, or when required by law.

Google user data

When an administrator connects Google Drive, Pever asks for read-only access to Google Drive (drive.readonly). Pever uses it only to read the folders the administrator chooses on Pever's settings page, and the files in them, so that members of their organization can search them and get cited answers. Pever never changes, creates, shares or deletes anything in Google Drive.

Pever's use and transfer of information received from Google APIs to any other app will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements.

An administrator can disconnect Google Drive at any time on Pever's settings page, which revokes Pever's access and can also remove every imported file. Access can also be removed from your Google Account at myaccount.google.com/permissions.

Service providers

Pever relies on these providers to run the service. They process data only on Pever's behalf:

To answer a question, the passages relevant to it are sent to the AI provider together with the question. Requests go through Cloudflare's AI gateway with request and response logging turned off. Pever uses these providers' paid API services, not their consumer apps.

Retention and deletion

Security

All traffic is encrypted in transit. Sign-in codes are stored hashed and expire after five minutes; sessions can be ended at once by removing a person. Tokens for connected services are encrypted at rest. Access rules are checked in the database for every search, not left to the AI model.

Changes

If this policy changes, the new version will be posted here with a new date. Significant changes will be announced to organization administrators.