Privacy policy
Last updated 6 October 2026
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
- Account details: your email address and name, the organizations you belong to and your role in them. You sign in with a one-time code sent to your email; Pever stores no passwords.
- Your organization's content: documents uploaded to Pever, and content from services an administrator connects (for example Google Drive files, Linear tickets). Pever keeps a copy of this content, the text read from it, and search indexes built from it.
- Questions and answers: the questions you ask, screenshots you attach to them, the answers given, the sources they cite, and any feedback you leave.
- Usage and technical data: when and how the service is used, model usage and cost, response times, errors, and the IP address of sign-in attempts (to limit abuse).
How we use it
- To provide Pever to your organization: to search your organization's content and answer its members' questions with citations.
- To keep the service secure, working and within your plan's limits, and to fix problems.
- To send the emails the service needs, such as sign-in codes and invitations.
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.
- Files from the chosen folders are copied into Pever, read into text, and indexed, and are kept up to date with changes in Drive. Files removed from Drive, moved out of the chosen folders, or no longer shared with the connected account are removed from Pever.
- Google data is shown only to members of the organization that connected it, within the projects the administrator assigned the folders to.
- Google data is not sold, not used for advertising, not used to train AI models, and not transferred to anyone except the service providers listed below, only to provide Pever's features.
- Access tokens from Google are stored encrypted and are never shown in the app.
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:
- Cloudflare: hosting, file storage, email delivery, and some AI models (text reading, search and ranking).
- Neon: the database, hosted in Singapore (AWS ap-southeast-1).
- OpenAI: writing answers and reading images and scanned pages. Other AI providers (such as Anthropic or Google) are used only when your organization chooses one of their models.
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
- Content is kept while your organization uses Pever. Deleting a document in Pever, or removing it from a connected source, removes it from search; deleting a chat deletes it and its attached screenshots.
- Deleting an organization deletes all of its documents, chats, connections and stored files.
- You can ask us to delete your account, or any data about you, by writing to hello@pever.si.
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.