Privacy Policy

1. Who we are

Revue (“we”, “us”) is a feedback capture product that turns reviewer notes, screenshots, and recordings into developer-ready issues. This policy describes what we collect while the product is in beta.

2. Information we collect

• Account data. Email, name, and authentication details when you create an account.
• Project data. Project names, target URLs, descriptions, and integration settings you connect (such as Jira, Asana, or GitHub), including GitHub account tokens and the repositories and branches you select for code analysis.
• Review content. Media reviewers capture or upload (screenshots, video, audio), captions, transcripts, device and page context, and the structured tickets generated from that feedback.
• Code analysis data. When a project owner runs code analysis, we temporarily download a snapshot of a selected GitHub repository (or pull request), inspect source files related to the ticket, and store the resulting findings, file paths, line references, and an investigation trace of the tools the agent used.
• Usage data. Basic technical logs needed to operate the service, such as timestamps and error reports.

3. How we use information

We use this information to provide Revue: authenticate users, collect and organize feedback, generate issue summaries, investigate related source code when you ask us to, sync to tools you connect, and keep the product secure. We do not sell personal information, and we do not use your repositories to train Revue’s own models.

4. Processors and integrations

We use infrastructure and AI providers to run Revue, including database/storage hosting and models that transcribe feedback, structure tickets, and inspect source during code analysis. If you connect Jira, Asana, or GitHub, we exchange the data needed to authenticate, sync issues you choose to send, and — for GitHub — download a repository snapshot when you run analysis. Source the agent reads is sent to our AI provider so it can search and cite code. Those services have their own privacy policies.

5. Code analysis

Code analysis is optional and started by a project owner from a ticket. When you run it, Revue:

• Uses your connected GitHub token to look up a matching pull request when a tracker key is present, otherwise the branch you selected.
• Downloads a size-capped snapshot of that ref to a temporary workspace on our servers. We skip common vendor, build, media, and lockfile paths. We do not keep a permanent clone of your repository.
• Lets an AI agent list, search, and read files in that workspace. File contents the agent actually reads are included in prompts to our AI provider. Secrets or personal data committed to those files may be included if the agent opens them.
• Stores a summary, findings (including paths and line numbers), and a short investigation trace (tool names, queries, and result summaries — not the full repository). The temporary workspace is deleted when the run finishes.

Disconnect GitHub in project settings to revoke this access. Avoid selecting repositories that contain secrets or data you do not want processed by an AI provider.

6. Sharing

Review links are for signed-in reviewers you invite. Project owners can see submitted reviews. We may disclose information if required by law, or to protect Revue, our users, or the public from abuse or security threats.

7. Retention

We keep account, project, and review data until you delete it or close your account, unless we must retain it longer for security or legal reasons. Temporary repository checkouts used for code analysis are deleted after the run. Stored analysis findings and traces remain with the ticket until you delete that ticket or project. You can delete individual tickets and projects from the dashboard.

8. Your choices

You can update project settings, disconnect integrations (including GitHub), choose which repositories are analyzed, and delete projects or tickets you own. Reviewers should avoid sharing sensitive personal data in captures. To request deletion of an account, email admin@laminindigital.org.

9. Security

We use authentication, access controls, and encrypted transport to protect data. Revue is a beta product; no method of transmission or storage is completely secure.

10. Children

Revue is not directed at children under 13, and we do not knowingly collect their personal information.

11. Changes

We may update this policy as the beta evolves. The “Last updated” date will change when we do. Continued use after an update means you accept the revised policy.

12. Contact

Questions about privacy can be sent to admin@laminindigital.org. See also our Terms of Use.