This Privacy Policy explains how Temple (“we”, “us” or “our”) collects, uses and shares personal information when you use Temple: the video editor at www.temple.so, review links and review pages, AI generation and other paid skills, and the hosted agent connector (the “Service”). We are the controller of the personal information described here, except where we say otherwise.
In short: without an account, your projects and source media stay in your browser. With an account, they are also saved to your workspace on our servers, so you can open them on another computer and share them with the people you invite. We also receive what you publish, what you send to AI generation or transcription, and the files you share through the agent connector, along with your account and billing details. We don’t sell your personal information and don’t use it for targeted advertising.
1. Information we collect
Your account
- Your email address. If you sign in with Google, we also receive your name and profile picture from your Google account.
- Account and session records: your account identifier, when you signed in, and the IP address and browser details of each session.
- The agents you connect to Temple, such as the name of the app, when you connected it and when it was last used.
- Messages you send us, such as feedback in the editor and emails to support.
Billing and credits
Payments are handled by Stripe. We receive your Stripe customer identifier, plan and subscription status, invoices and payment status, and the email address used for billing. We don’t receive or store your full card number. We keep a record of your credits: what was granted, reserved, spent and refunded, and for which runs.
Workspaces
Every account has a workspace of its own, and you can start others or be invited to them. We store what is saved to a workspace: your projects (their timelines, text and settings), the media files they use, the files you add to the workspace, its name, picture, memory page and pipelines, who its members are and the invitations sent from it. Projects you make while signed in are saved to the workspace you have chosen without your asking, and projects that were only in your browser when you signed up are saved to your own workspace. Everyone in a workspace can open what is saved to it; only you are in your own workspace until you invite someone.
Review links you publish
When you publish a review link, we store the rendered copy of your video, its title, its length, frame rate and file size, its versions, and the link’s settings and status. We also count views of each link.
AI generation and transcription
When you or an agent run a generation or another paid skill, we receive your prompt, settings and input files (such as reference images, video or audio, or the recordings you transcribe), and the outputs. We keep a record of each run: the model, its price, its status and when it ran.
The agent connector
When an agent works on your project through the hosted connector, its requests and the results, which can include parts of your project, frames and media files you ask it to work with, pass through our servers to reach your browser and the agent. Files sent in either direction are stored only briefly, until they are delivered or their download link expires.
People who watch or comment on review links
- The name and email you enter, your comment, the point in the video it refers to and when you posted it. Your email is not shown publicly.
- When you turn on voice review, your microphone audio and the frame you are watching go to Google Gemini to understand your feedback and playback commands. The resulting comments are saved with the review.
- Random identifiers stored in cookies on your browser, to let you delete your own comments and to count distinct views (see “Cookies” below).
- Your IP address, used to limit how often requests can be made. For this, we store it only in a keyed, hashed form.
Reports
If you use “Report this video” or send us a copyright notice, we collect what you submit: the reason, the link, your explanation, your name and email address, and for copyright notices, the work you say is infringed and other details the law requires.
Analytics
On www.temple.so, we use PostHog to understand how the website and editor are used and to find errors. It records a limited set of events, such as the editor opening, an edit being made or undone, an export or skill finishing, or signing in. Events carry only fixed details like the type of media or the skill used. If you are signed in, events are linked to your Temple account identifier and your email address is stored on your analytics profile; guests have a profile with a random browser identifier. Guest activity can be linked to your account when you sign in. Before anything is sent, we remove project titles, prompts, media names and contents, addresses that include project identifiers, typed text, error messages and sign-in codes. We record masked session replays to understand navigation and interactions. Text and input values are masked, and media, the video canvas and embedded content are blocked from replays. We don’t capture console logs, network bodies or headers in replays. We don’t use IP addresses for location, and we honor your browser’s Do Not Track setting. Local and test versions of Temple send no analytics.
Crash reports
If Temple for Mac crashes, it sends us a crash report: a snapshot of the part of the app that stopped, taken at that moment, which can include fragments of what it held in memory, such as parts of an open project. It comes with the versions of the app and the editor, how many tabs and graphics were open, the identifier of the open project and, unless your browser setting asks not to be tracked, your analytics identifier. We keep it for 30 days to find and fix what went wrong. PostHog gets only where the crash happened and these details, without the snapshot or the project identifier, on your analytics profile.
Server logs
Like most websites, our servers and Cloudflare record technical information about requests, such as IP address, browser type, the page or address requested and the time. We use these logs to run, debug and secure the Service.
2. What we don’t collect
Temple is built to work in your browser. Without an account, your projects, timelines, source media and exported files are stored on your device and aren’t sent to us, unless you or an agent you connect send media to AI generation or transcription, or share a file through the agent connector. With an account, your projects and their media are saved to your workspace as described above; files you export stay on your device unless you publish them. We don’t ask for and don’t want sensitive information such as government identifiers or health information.
3. How we use information
- To provide the Service: sign you in, run generations and skills, host and stream review links, show comments, and deliver files to your agent.
- To process payments, grant and track credits, and apply plan limits, including view counts and link expiry.
- To keep the Service and its users safe: prevent abuse, fraud and extreme usage, enforce our Terms of Service, and handle reports and copyright notices.
- To communicate with you: sign-in codes, receipts, service and account notices, and replies to your messages.
- To understand and improve the Service: usage analytics, error and crash reports, and measuring which review links lead people to sign up.
- To comply with the law and respond to lawful requests.
If you are in the European Economic Area or the United Kingdom, we rely on these legal bases: performing our contract with you (providing the Service and billing), our legitimate interests (security, abuse prevention, analytics and attributing sign-ups, balanced against your rights), your consent where we ask for it, and compliance with legal obligations.
4. Service providers
We use the following companies to run the Service. They process personal information on our behalf, under contracts, and only to provide their services.
| Provider | What they do for us |
|---|---|
| Cloudflare | Hosting and network for the Service, video hosting and streaming for review links (Cloudflare Stream), file storage (R2), and sending email such as sign-in codes. |
| Neon | Our PostgreSQL database for accounts, workspaces, billing records, credits, review links and comments. |
| Stripe | Payments, subscriptions, invoices and the customer portal. |
| Sign in with Google, if you choose it, and understanding spoken feedback through Gemini when you turn on voice review. | |
| PostHog | Product analytics, masked session replays and error reports on www.temple.so, and crash reports from Temple for Mac. |
| Anthropic | Running the Claude model behind Temple’s own agent, if you use it: what you write to the agent and what it reads of your project to answer, such as the Timeline, transcripts and frames. It also runs the agent’s web searches. |
| fal and MachGen | Running AI models for generation and transcription. Some models, such as ElevenLabs voice, sound and speech-to-text models, are made by other companies and offered through fal, and those companies may process the inputs too. |
5. How we share information
- With service providers, as described above.
- With the agents you connect. When you connect an agent such as Claude, ChatGPT or Codex, we share with it the project information and files it requests on your behalf. Its provider’s privacy policy applies to what it receives.
- With people who have your review link. Anyone with the link can see the video, its title, its comments and the names commenters entered.
- In copyright and content reports. When we act on a copyright notice, we send the notice, including the sender’s name and contact details, to the person who published the video. If that person sends a counter-notice, we send it, including their name and contact details, to the person who sent the notice.
- For legal reasons: to comply with the law or a valid legal request, to report child sexual abuse material to the National Center for Missing & Exploited Children (NCMEC) as required by law, or to protect the rights, property and safety of our users, the public or Temple.
- In a business transfer, such as a merger, acquisition or sale of assets, subject to this policy.
- With your consent or at your direction.
We don’t sell personal information, and we don’t share it for cross-context behavioral or targeted advertising.
6. How long we keep information
- Account information: while your account exists. When it is deleted, we delete or anonymize it, except for records we must keep for legal, tax, accounting or fraud-prevention reasons, such as billing records.
- Workspace projects and files are kept until you remove them or the workspace is deleted. When your account is deleted, a workspace that only you are in is deleted with it; one you share stays with the people in it.
- Review videos follow the link rules in our Terms of Service. On a Free account, a link’s video is kept for 30 days after the link expires and then deleted. On Pro and Max, videos are kept while your subscription is active, and for 6 months after it ends, and then deleted. Videos are deleted when you delete your account.
- Link records and comments are kept with the link, including after its video is deleted, until you delete your account. Comments a guest deletes are hidden from the page and kept in our records with the link.
- Generation inputs uploaded for a run are deleted automatically, usually within a day. Outputs and run records are kept so you can retrieve them while your account exists.
- Files sent through the agent connector are deleted once delivered, or within a few hours if they are never collected.
- Reports and takedown records are kept as long as needed to handle them, apply our repeat-infringer policy and meet legal obligations. Material reported as child sexual abuse is preserved as the law requires.
- Crash reports from Temple for Mac are deleted after 30 days.
- Analytics and logs are kept only as long as they are useful for the purposes above. Rate-limit records expire within about a day.
7. Security
We protect information with measures such as encrypted connections, signed and short-lived access to review videos, HttpOnly session cookies, hashed sign-in codes, and limited access to our systems. Payment details are handled by Stripe. No system is perfectly secure, so please also keep your email and sign-in methods safe.
8. Your choices and rights
You can ask us to access, correct, delete or export the personal information we hold about you, and object to or restrict some uses of it. Email support@temple.so from the address you sign in with, so we can verify your request. Account deletion is handled by email for now. We will respond within the time the law requires and won’t treat you differently for using your rights.
- You can turn off a review link, delete your own comments, disconnect agents, and cancel your subscription at any time.
- You can clear cookies and browser storage. Clearing browser storage also removes your local projects.
- Analytics respect your browser’s Do Not Track setting.
California and other US states
If you live in California or another US state with a privacy law, you have the right to know what personal information we collect, use and disclose, to access, correct and delete it, and not to be discriminated against for using these rights. In the past 12 months we have collected identifiers (such as email address, account identifiers and IP address), commercial information (plans, purchases and credits), internet activity (analytics, logs and crash reports), and audio and visual information (videos you publish and media you send to generation), from you, your device and the services described above, for the purposes in section 3. We disclose them to the service providers in section 4. We don’t sell or share personal information as those laws define it, and we don’t use sensitive personal information to infer characteristics about you. You may use an authorized agent; we may ask for proof of the agent’s authority and verify your identity.
European Economic Area and United Kingdom
If you are in the EEA or the UK, you have rights under the GDPR and UK GDPR: access, rectification, erasure, restriction, portability, and objection to processing based on legitimate interests. Where we rely on your consent, you may withdraw it at any time. You may also complain to your local data protection authority.
9. International transfers
Temple is based in the United States, and we process information in the United States and in other countries where our service providers operate, including through Cloudflare’s global network. When we transfer personal information from the EEA or the UK, we rely on appropriate safeguards, such as the European Commission’s Standard Contractual Clauses and the UK addendum, or our providers’ certification under the EU-U.S. Data Privacy Framework, where applicable.
10. Children
Temple is not directed to children under 13, and we don’t knowingly collect personal information from them. If you believe a child under 13 has given us personal information, contact us at support@temple.so and we will delete it.
11. Cookies and similar technologies
We use a small number of cookies and browser storage entries. We don’t use advertising cookies. Google and Stripe may set their own cookies on their sites when you sign in with Google or pay.
| Name | Purpose |
|---|---|
| Sign-in session | Keeps you signed in. Set when you sign in, HttpOnly, and lasts up to 30 days or until you sign out. |
| temple-reviewer | Set on review pages when you comment. A random identifier, HttpOnly, that lets you delete your own comments. Lasts 30 days. |
| Review viewer | Set on review pages when you play a video. A random identifier, HttpOnly, used to count distinct views of a link and apply view limits. |
| temple-review-ref | Remembers the first review link that brought you to Temple, by the link’s public identifier, so we can tell which links lead to sign-ups. |
| Analytics (PostHog) | On www.temple.so only. A first-party cookie and local storage entry holding a random analytics identifier, as described in “Analytics” above. |
| Browser storage | Your projects, media and editor preferences, stored in your browser (IndexedDB, origin private file system and local storage) so the editor works on your device. Without an account this stays on your device and isn’t sent to us. With an account, your projects and their media are also saved to your workspace, as described in “Workspaces” above. |
12. Changes to this policy
We may update this policy. If a change is material, we will tell you in advance, for example by email or in Temple. The effective date at the top of this page shows when it last changed.
13. Contact
Questions or requests about privacy? Email support@temple.so.