Privacy Policy
Last updated: 10 August 2026
This page is a plain-language summary provided for transparency. It is not legal advice and does not create a contract. If you operate Teamly as a service for others, review it with your own legal counsel before relying on it.
Teamly is open-source, self-hostable software. There are two different contexts to be clear about: the hosted marketing website at askteamly.ai, and the Teamly application that you run yourself. This policy explains both, and what data — if any — reaches the Teamly maintainers.
The short version
- When you self-host Teamly, the maintainers receive none of your data — no prompts, no results, no provider keys. Everything lives in the database you control.
- Your AI provider keys are stored encrypted at rest and are never sold, shared, or used to train models.
- The marketing website collects only what is needed to operate it, does not run advertising trackers, and does not sell your data.
The marketing website (askteamly.ai)
When you visit the marketing site, our hosting provider processes standard technical information (such as IP address and browser type) in server logs for security and reliability. If you email us or book a call, we receive the contact details and message you send so we can reply. We do not use this information for advertising and we do not sell it.
The Teamly application
The application processes the data you put into it: your brands, the prompts you track, competitors, tags, the responses returned by AI models, and the metrics derived from them. It also stores the AI provider API keys you connect.
Because Teamly is bring-your-own-keys, running a scan sends your prompts to the AI providers you configure (OpenAI, Anthropic, Google, xAI, Perplexity). Those requests are governed by each provider's own terms and privacy policy. Teamly does not add itself as an intermediary that retains your prompts or answers beyond your own database.
When you self-host, you are the operator of that instance. The Teamly maintainers have no access to your instance, its database, or its traffic.
Provider keys
Provider keys are encrypted with AES-256-GCM before they are written to the database, decrypted only in memory for the moment a scan needs them, and never written to logs or returned to the browser in plain text — the app only ever shows a masked form (for example, sk-…a1b2). See the Security page for more detail.
Third-party services
A Teamly deployment relies on Supabase (authentication and Postgres database), a Redis instance (background jobs), and the AI providers you connect. When you self-host, these are your own accounts and are covered by your agreements with those providers.
Your choices
You can remove a provider key at any time from Settings, and you can delete brands, prompts, and other data you have added. If you self-host, deleting the data from your database removes it entirely. For questions about data handled by the marketing site, contact us at hello[at]factorial.software.
Changes to this policy
As Teamly evolves we may update this page; material changes will be reflected in the “last updated” date above.