Encore is a product of Passionate Pursuit. This policy describes the information processed through Encore’s website, studio, client-facing experiences, and connected agent tools. It is written to reflect the product’s current implementation.
1. Who this policy covers
Encore serves studios and the people those studios invite into client projects. When a studio creates an account, configures its workspace, manages billing, or uses Encore for its own operations, Encore determines how the related account and service data is used.
For project information that a studio collects from an end client, the studio decides what to ask, whom to invite, and why the information is needed. As between Encore and the studio, the studio is the controller of that client information and Encore processes it on the studio’s behalf to provide the service. End clients should direct project-specific privacy requests to the studio that sent the Encore link.
2. Information Encore collects
Account and studio information
Encore uses Supabase for account authentication. It stores an account identifier, email address, authentication metadata, account preferences, studio settings, team membership and invitation details, and notification preferences. If you choose Google sign-in, that authentication flow is initiated through Supabase.
Projects and authored content
Encore stores the work a studio creates or uploads: project and client names, project configuration, flows and canvases, questionnaire questions, moodboards, comparisons, pages, briefs, templates, brand settings, uploaded images, and image metadata. Context documents may include the uploaded filename and text extracted from supported PDF, DOCX, Markdown, or text files.
Client participation
Client-facing experiences can collect a participant’s name and email address. They also store session progress and the participant’s questionnaire answers, ratings, reactions, comments, image choices, and comparison decisions. Encore may create individual or team briefs from that evidence. The studio that sends the link controls what the experience asks for and whether the link uses verified-email or guest access.
Images and files
Uploaded and imported project images are stored in Supabase Storage. The current project image bucket is public-read so images can appear in client-facing pages: a person who has an image’s direct file URL may be able to view it. Project context uploads are converted to extracted text for storage and assistant context; the active context-upload route does not retain the original PDF, DOCX, Markdown, or text file as a separate stored object.
Billing information
Polar hosts checkout and the billing portal. Encore sends Polar the account identifier, email address, and selected product, and stores customer and subscription identifiers, product, status, trial timing, and billing-period timing returned by Polar. Payment-card entry and card updates happen on Polar’s hosted surfaces; Encore does not receive the full card number through its application routes.
Website analytics and service telemetry
Marketing pages set a first-touch attribution cookie named encore_attr for up to 90 days. It contains a random visitor identifier, first-touch time, landing path, external referrer, and any UTM or referral parameters. Session storage prevents duplicate pageview beacons for the same path in one tab. Encore records pageviews, CTA clicks, and signup attribution, including host, browser user-agent, signup provider, and email domain.
Encore also records bounded application-error reports for troubleshooting. These reports can include the route, error message, stack trace, and a limited context object. Please do not intentionally place sensitive information in error messages or URLs.
3. How Encore uses information
- Authenticate accounts and verified client participants.
- Store, display, share, and export the studio content and client evidence you request.
- Operate flows, pages, client links, notifications, teams, and billing.
- Analyze images and synthesize briefs or pages when an AI-powered feature is used.
- Attribute site visits and signups, understand use of the service, and troubleshoot errors.
- Protect the service, enforce access boundaries, and maintain operational records.
- Respond to support, privacy, and account requests.
4. Service providers and subprocessors
Encore relies on the following providers to operate the current service:
- Supabase
- Authentication, database services, and file storage.
- Vercel
- Application hosting, request execution, and scheduled application jobs.
- Anthropic
- AI image analysis, content assistance, page composition, logo moderation, and brief synthesis. Depending on the feature, Anthropic can receive selected project content, images, client responses, and participant names needed for the requested synthesis.
- Polar
- Hosted checkout, subscriptions, customer billing records, and the billing portal.
- Resend
- Client verification links, team invitations, studio notifications, sender-domain configuration, and support-email delivery. Resend receives the recipient address and the message content needed to deliver each email.
- Unsplash and Pexels
- Optional stock-image search and import. When used, the provider receives the search query and normal web-request information; image previews may load from its image CDN.
These providers process information under their own service terms and privacy notices. Encore may also disclose information when legally required or when necessary to protect the service and its users.
5. Sharing, links, and connected agents
A studio can share project experiences and completed work through Encore links. Some links require email verification; a studio can also choose guest access. Anyone who has a live guest link may be able to open the linked experience. Studios can manage, expire, or revoke links in the product.
Studio owners can invite team members, who may then access the studio’s projects and client information according to their role. A studio can also connect an MCP-compatible app or agent through Encore’s OAuth consent flow. A connected app receives only the scopes granted at consent, but those scopes can permit it to read and modify studio data on the connecting user’s behalf. The user can disconnect the app from studio settings. The connected app’s own privacy practices also apply to information it receives.
6. Retention, export, and deletion
Encore retains account, studio, project, and client content while the account remains open and as needed to operate the service. The current product does not apply one fixed automatic retention period to every telemetry or operational record. The marketing attribution cookie expires after no more than 90 days unless it is cleared earlier.
A signed-in studio owner can download a JSON account export from Settings. The export includes account details, authored content, projects, client responses, briefs, templates, integration metadata, and agent activity records. Password hashes, service credentials, and provider API keys or tokens are excluded.
A studio owner can permanently delete the account from Settings after password confirmation. The deletion flow removes the sign-in and account-owned database records, cancels an active Polar subscription, and removes identified stored project files. If a storage or billing cleanup step fails, Encore retains a restricted deletion-job record so the remaining cleanup can be audited and retried. Some operational records may also be retained when needed to complete deletion or meet legal obligations.
Studios can delete individual projects, sessions, pieces, links, and other content using the controls available in the service. End clients should ask the inviting studio to access, correct, export, or delete project responses; Encore can assist the studio with a verified request.
7. Your choices and rights
Depending on your location and relationship with Encore, you may have rights to:
- Access, correct, or obtain a copy of personal information.
- Ask for deletion or restriction of certain processing.
- Object to certain uses or withdraw consent where consent is the basis for processing.
- Disconnect a connected agent, revoke a client link, or clear the attribution cookie.
Account owners can use the export and deletion controls in Settings or email hello@encorehq.co. Client participants should normally contact the studio that invited them, because that studio controls the project and can identify the relevant response.
8. Security and confidentiality
Encore uses authenticated sessions, scoped service routes, studio ownership checks, and row-level access controls for application data. OAuth connections use explicit consent and scoped tokens. No internet service is perfectly secure, and client links and public image URLs should be shared only with intended recipients. Do not upload an image that must remain inaccessible to anyone who obtains its direct URL.
9. Changes and contact
Encore may update this policy as the service or its providers change. A revised version will carry a new “Last updated” date. Questions or privacy requests can be sent to hello@encorehq.co.