Privacy Policy

FeedLab is operated by Lync Systems ("FeedLab", "we", "our", or "us"). This Privacy Policy explains how we handle information when you use our website, web dashboard, mobile apps, embedded feedback widget, public feedback forms, test management tools, API, and MCP server (together, the "Service").

It should be read together with our Terms of Service.

For account and billing information (for example, your name, email address, and payment records), FeedLab decides how that information is used and acts as the data controller.

For content our customers collect or create in FeedLab (feedback submitted through a customer's widget or public form, screenshots, comments, and test cases and results), FeedLab processes that information on the customer's behalf and acts as a data processor. The customer who owns the workspace decides what is collected and how it is used.

If you sent feedback to a company that uses FeedLab and want to access or delete it, please contact that company first. We will help them respond to your request.

We use information to:

• Provide, operate, and maintain the Service
• Deliver feedback, test results, and notifications to the right workspace and people
• Send service emails, such as invitations, notifications, and account messages
• Process payments and manage credits and subscriptions
• Keep the Service secure, prevent spam and abuse, and enforce our Terms
• Understand usage and improve the Service
• Send product updates to people who subscribed, who can unsubscribe at any time
• Comply with legal obligations

FeedLab does not sell personal data, and we do not use customer content to train AI models.

You can connect Claude Code or another MCP client to FeedLab with a personal API token. That tool then acts as you: it can read the projects and test cases you have access to, and create or update test cases.

Information your AI tool reads from FeedLab, and code it reads on your computer, is processed by that tool and its provider under their own terms and privacy policy, not ours. FeedLab does not send your content to AI providers. Review what your tool does before connecting it, and revoke tokens you no longer use from Settings → API Tokens.

We share information only as described here:

• Within your workspace: feedback, comments, and test data are visible to members of the workspace that owns them.
• Service providers that help us run FeedLab, under confidentiality and data protection obligations: Supabase (database, authentication, and file storage), Vercel (hosting), Resend (email), Google Firebase Cloud Messaging (push notifications), Google Analytics (analytics), and PayChangu (payments).
• Services you connect: GitHub, your webhook endpoints, and AI tools you authorise with an API token receive the data needed for the connection to work.
• App stores: Apple and Google handle app downloads under their own policies.
• Legal reasons: when required by law, or to protect the rights, safety, and security of our users, FeedLab, or others.
• Business transfers: if FeedLab is involved in a merger, acquisition, or sale of assets, information may be transferred as part of that transaction, subject to this Policy.

Screenshots attached to feedback are stored at shareable file addresses. Anyone who obtains a screenshot's address may be able to view it. Please review screenshots before submitting them and leave out passwords, payment details, and other sensitive information.

A project's public feedback form can be used by anyone who has its link. Workspace owners decide where to share it.

Our service providers may store and process information in countries other than your own, including the United States and the European Union. Where required, we rely on appropriate safeguards for these transfers.

• Account information is kept while your account is active.
• Feedback, screenshots, comments, and test data are kept until the workspace deletes them or the account is closed. How long feedback is kept may also depend on the workspace's plan.
• Revoked API tokens stop working immediately. A record that the token existed may be kept for security.
• Payment records are kept as long as tax and accounting law requires.
• Deleted data may remain in backups for a limited period before it is overwritten.

We use reasonable technical and organisational safeguards, including encrypted connections (HTTPS), database access rules that limit data to the workspace it belongs to, and hashed passwords and API tokens. No system is completely secure, so we cannot guarantee absolute security. If we become aware of a breach that affects your personal information, we will notify you and the relevant authorities as required by law.

Depending on where you live, you may have the right to:

• Access the personal information we hold about you and get a copy
• Correct inaccurate information
• Delete your information
• Object to or restrict certain processing
• Withdraw consent where we rely on it, for example for the newsletter

You can update most account details in Settings. For other requests, email developers@lyncsystems.tech. We may need to confirm your identity before acting on a request. You can also complain to your local data protection authority.

You can ask us to permanently delete your account and associated personal data at any time. Email developers@lyncsystems.tech with the subject line "Account Deletion Request". We will verify and process your request promptly and as required by applicable law. Content that belongs to a workspace you are a member of, but do not own, remains with that workspace.

The Service is not directed to children under 16, and we do not knowingly collect their personal information. If you believe a child has given us personal information, contact us and we will delete it.

We may update this Privacy Policy from time to time. We will post changes on this page with a new "Last Updated" date. For significant changes, we will give additional notice, such as by email or in the dashboard.