Skip to the policy
Home

Legal

  • Terms
  • Privacy
    • Who we are
    • Your editor and local files
    • Accounts, security and email
    • Hosted media, transcription and chat
    • Payments, support and website use
    • Why we use information and who can receive it
    • How long information stays
    • Your choices and account deletion
    • Age, security and changes
    • Service providers
  • Acceptable Use
  • Refunds

Temno Privacy Policy

Last updated: October 5, 2026.

On this page
  • Who we are
  • Your editor and local files
  • Accounts, security and email
  • Hosted media, transcription and chat
  • Payments, support and website use
  • Why we use information and who can receive it
  • How long information stays
  • Your choices and account deletion
  • Age, security and changes
  • Service providers

Who we are

Temno is operated by Wright Solutions Development, LLC ("Temno," "we," "us"). This policy covers the Temno website, Windows editor and optional hosted features. Contact us at support@temno.io or 2261 Market Street STE 18630, San Francisco, CA 94114 about privacy or account deletion.

Your editor and local files

The editor stores projects, imported media, previews, waveforms, search indexes, transcripts, conversation history and exports on your device or in locations you choose. Opening a local project alone does not upload its media to Temno. Hosted generation, transcription and chat send the content needed for those features as described below. Local MCP gives clients you connect access to the tools and project information they request; those clients may send information to their own providers. Their processing is governed by your arrangements with them.

Local preferences can contain your own API keys. The operating system protects saved Temno account sessions using its data-protection service; other local files and keys may use different storage. Local crash reports may include file paths, exception details and memory dumps. Temno does not currently provide an automatic cloud crash-report sender. Operating-system diagnostic settings apply separately. Update checks and downloads contact the configured update host, which receives your request and IP address. If you separately obtain a model from an external model-download site, that site's privacy policy governs your visit; local search does not upload your media to that site.

Accounts, security and email

We process your email address, authentication information, account and session identifiers and profile details to sign you in, secure your account and deliver service messages. When you choose third-party sign-in, the identity provider and our authentication provider exchange authentication information; your profile may include your name, email and profile image. To display an identity-provider profile image, the desktop may download it from the identity provider's image service, which receives the request and your IP address. Where password sign-in or account recovery is available, it uses our authentication provider.

Our accounts service processes verification and recovery information and temporarily stores encrypted session information. Our email delivery provider delivers account emails and receives the recipient address and message content, including any relevant link. Your mailbox provider also processes delivered messages. Browser login and recovery use necessary security cookies. Blocking them can prevent these flows.

Hosted media, transcription and chat

For generation or enhancement we process your prompt, settings and selected images, video or audio; file hashes and media properties; job status and provider identifiers; generated outputs; and usage and credit records. Our Gateway processes these requests and stores job information and temporary files using our database host. The model-hosting provider receives the generation request and can fetch the selected files to run your chosen model. Its serving partners and delivery networks may also process this content.

Transcription sends audio chunks, language and any supplied vocabulary hints through our model router to the provider serving the transcription model listed in Service providers. That serving provider can vary; transcription does not use the same provider-pinning and data-collection restrictions as hosted chat. Our Gateway also processes audio and text to produce word timings and speaker labels. These labels distinguish speakers within your transcript; they are not verified identities.

Hosted chat sends conversation messages and the project context used by the assistant, including tool arguments and results. This can contain media names, paths, transcripts or other information returned by editing tools. Our model router routes the request to the selected model provider. We store temporary conversation and execution content to resume the interaction, together with usage and credit information.

The media catalog includes the model families listed in Service providers. Availability changes. A model's creator is not necessarily its hosting provider: the model-hosting provider may host the model itself or route the request to a partner. The selected route determines which companies process the request. You can ask support about the route and recipients for a particular hosted job without sending us passwords or API keys.

Provider retention, security and data-use terms differ. Our chat routing requests restrictions on provider data collection. Restrictions on training and input/output logging are separate from provider retention; we do not promise that every model or audio endpoint has zero retention. The lifetime requested for a generated media file does not control every copy of its request payload or provider logs. Deleting Temno data does not by itself delete independently retained provider records. Relevant information is in the terms and data policies listed in Service providers and the selected provider's terms.

If you use your own API key, chat goes to the endpoint you configure (the default endpoint provider is listed in Service providers). Custom generation connections send requests and uploads to that configured service; the legacy HTTP connection can use a legacy editor service endpoint listed in Service providers. Your provider account and its terms govern that processing. Temno's hosted credit rules do not replace your direct provider charges. An assistant or connected MCP client can also request an import from an HTTPS media URL. Your device downloads that file, and its hosting site receives the request and your IP address; the imported copy may then be saved in your local project.

Payments, support and website use

When paid hosted features are available, our payment processor collects payment information through its checkout and customer portal. We exchange your email, customer/subscription identifiers, selected plan and transaction information with our payment processor, and keep subscription, invoice, credit and usage records. Our application credit tables do not store full card numbers or security codes. Our payment processor's privacy policy, listed in Service providers, describes its processing. Purchases are sold through Link, Stripe's merchant-of-record service: Link collects the billing address and tax details it needs for the sale and keeps its own order records under its privacy policy. If you ask Link to delete them, Link also cancels subscriptions sold through it.

We use our support mailbox to receive and manage support messages and attachments, including privacy or deletion requests. If we arrange a copy of your information, we verify the recipient and use a restricted delivery method. Our account and hosted-generation services run on infrastructure provided by our service host. Website and service hosts process IP addresses, timestamps, requested resources, errors and security information to deliver and secure services. Our website edge provider also measures visits to the Temno website with a script on its pages: the page viewed, the referring site, browser, operating system and device type, approximate country and page-load performance. It uses no cookies or other stored identifiers and does not keep your IP address for this measurement.

If you sign up for Temno news and launch updates, your subscription starts only after you confirm by email. The launch announcement is the first update we send. We store your address, signup status, where you signed up, the version of the consent wording you saw, and related times in Temno's database, hosted by our database provider. The website and apps cannot read the list. Our accounts service uses it to send mail, and authorized support staff use it only to handle your requests. We also keep hashes of confirmation tokens and send counts to manage confirmations and limit abuse. Our email delivery provider delivers confirmation and update emails from a separate Temno updates address and receives the recipient address and message content, including any relevant link. Your mailbox provider also processes delivered messages. Every update email includes a one-click unsubscribe option. Contact support@temno.io to unsubscribe, or to request access to or deletion of your email signup information. Access requests include your signup information and any recorded reason for stopping mail. After unsubscribing, you can sign up again, but rejoining requires a new email confirmation. If mail to an address is stopped because of a bounce, spam complaint or support block, a signup sends nothing until support lifts the block; you must then sign up and confirm again. Unsubscribing from optional updates does not stop necessary account or security messages.

Why we use information and who can receive it

We use information to provide the functions you request, authenticate you, run and meter hosted jobs, process purchases, answer support requests, prevent abuse and meet applicable legal obligations. Necessary service cookies support authentication. We do not sell your personal information or share it for cross-context behavioral advertising, and we do not use advertising trackers on the Temno website. We use sensitive account information for the requested service, security and legal obligations, rather than to infer personal characteristics for advertising.

Service providers described above process information for these functions. Payment and identity providers may also act for their own legal, security or account purposes. Information may be disclosed when legally required, to investigate abuse or protect rights, or as part of a business transfer subject to applicable law and notice requirements. Access by our operators is limited to support, security, administration and other necessary service purposes.

Where data-protection law requires a lawful basis, we rely on performing our agreement for requested features, legal obligations for required records, legitimate interests in security and reliable operation where permitted, and consent where required. You may withdraw consent without affecting the lawfulness of prior processing. Temno operates from the United States; our providers may process information in the United States and other countries outside your country. Where applicable law requires transfer safeguards, we use the required safeguards for that transfer. Contact support for information about the arrangements relevant to your request.

How long information stays

We keep information for the relevant service purpose and permitted exceptions described below. Different categories have different lifecycles; expiration of a download does not erase every associated record.

InformationRetention period or criteria
Local projects, downloads and chat filesRemain in storage you control until you remove them. Your own backups and connected clients are separate.
Account and profile informationKept while the account is in use and until a verified deletion request is completed, subject to applicable legal or security exceptions.
Email update signupsUnconfirmed signups are deleted 30 days after the most recent signup attempt recorded by the service. Confirmed addresses are kept while you are subscribed. Unsubscribing, a bounce, a spam complaint, a support block or a verified deletion request removes your signup record. After an unsubscribe, bounce, spam complaint or support block, we keep a separate record containing only a keyed hash of your address, the reason and the time. This record contains no email address and remains after a deletion request to prevent unwanted mail. This record has no fixed expiry. It is removed if you confirm a new signup after unsubscribing, or when support lifts a block.
Temporary hosted image/media filesUploads and downloadable outputs are normally scheduled to expire after 24 hours. They are temporary delivery storage, not a permanent project backup.
Temporary transcription and hosted-chat contentUnused transcription uploads are normally scheduled to expire after one hour. Transcription results and hosted-chat content have a 24-hour content window; completion timing affects its start.
Image/media prompts and detailed settingsScheduled for cleanup 24 hours after job completion. Cleanup preserves job identifiers, metering and other limited metadata needed for operation and records.
Other job history, legacy prompts and provider/output metadataKept with the account's hosted-job records until no longer needed to provide that history, investigate a job or resolve a charge, or until a verified deletion request applies. These records do not have the same automatic 24-hour content cleanup.
Usage, payment and credit recordsKept to operate balances, settle payments, handle refunds/disputes and meet tax, accounting or other legal obligations. Any exception to account deletion is limited to the records and period needed for that purpose.
Security and operational logsKept for troubleshooting, protection against abuse and incident investigation under the relevant service's log lifecycle. A specific investigation or legal obligation may justify keeping limited records longer.
Support and privacy-request correspondenceKept to handle the request, necessary follow-up and a proportionate record of the outcome; unnecessary attachments and export staging copies are removed when their purpose ends.
Login/recovery materialShort-lived authorizations expire; encrypted session material may remain temporarily to finish revocation and cleanup. Expiration does not extend the authorization's validity.
Backups and provider-held copiesBackups age out under the relevant backup cycle and may temporarily retain data removed from active systems. We reapply completed deletion instructions if restoring our account data. Providers and recipient mailboxes have their own retention requirements.

Cleanup is scheduled work. Delays, failures, active-job settlement and retries can mean physical deletion occurs after a content deadline. Retention decisions consider the data's purpose, sensitivity, an open support or security matter, mandatory recordkeeping and deletion requests. We remove or de-identify information when its purpose and any justified exception have ended. For information about a particular record or exception, contact support.

Your choices and account deletion

You can use local editing without hosted features, choose which content to submit, manage local files, and contact support@temno.io or the mailing address above to request access, correction, a copy of your information or account deletion. For deletion, send "Delete my Temno account" from the account email when possible. Do not send passwords, API keys or payment-card details. We verify requests proportionately and explain any permitted exceptions.

Depending on applicable law, you may also have rights to object, restrict processing, withdraw consent, opt out of covered sale/sharing or targeted advertising, limit covered uses of sensitive information, appeal a decision or complain to a data-protection authority. We do not penalize you for exercising applicable privacy rights. To request review of a privacy decision, contact support with the case reference and the reason for your appeal. An authorized agent may contact us; we may verify their authority and your identity or ask you to confirm the request directly where permitted. We respond within the time required by the law applicable to your request.

When we process a verified account-deletion request, we remove hosted access and delete the account's hosted jobs and files. We also address the customer profile and saved payment methods held for Temno by our payment processor; any retained billing records are identified separately. We retain only records justified by an applicable exception, such as legally required accounting evidence, for the corresponding period. We describe those exceptions in the response. Deletion does not erase files on your device, messages in your mailbox or copies independently retained by third parties.

Age, security and changes

Hosted accounts are intended for adults aged 18 or older. Contact us if you believe a child has provided information. We use access controls and encrypted connections, but no system can promise perfect security. We update this policy as practices change, revise its date and provide additional notice where required before a material new use of information.

Service providers

The names below identify the roles described in the policy, including optional user-selected services and model creators that are not necessarily the companies hosting a model.

ProviderWhat it does for TemnoWhat it receivesTerms or data policy
SupabaseOur authentication provider and database host; Supabase Auth handles password sign-in and recovery where available. Hosts the email updates list and hosted job information/temporary files.Authentication information exchanged for sign-in; hosted job information and temporary files; the email signup, consent, confirmation, send-count and suppression information described above.Data-processing addendum
GoogleThe optional Google sign-in identity provider and profile-image service. Sign-in can supply profile details that may include name, email and image. Also a model provider when its hosted chat route is selected.Authentication information exchanged with Supabase. Its image service receives the image request and IP address. Its selected chat provider receives conversation messages, project context, tool arguments and results.Privacy policy
ResendOur email delivery provider for account messages and email-update confirmations and updates; email-update confirmations and updates use a separate Temno sender.Recipient address and message content, including relevant links.Privacy policy
falThe model-hosting provider that runs the selected generation or enhancement model, either itself or through a partner.Generation requests and selected files it can fetch to run the chosen model; its serving partners and delivery networks may also process this content.API terms; Data-processing terms
OpenRouterOur model router: routes hosted chat to the selected Anthropic, Google or Meta model provider, and transcription to a provider serving Meta's Muse Voice Transcribe.Chat messages, project context, tool arguments and results; transcription audio chunks, language and supplied vocabulary hints. Transcription does not use the same provider-pinning and data-collection restrictions as hosted chat.Provider data policy
AnthropicA hosted chat model provider when selected; the default endpoint provider for chat using your own API key.Chat requests sent on the selected hosted route or directly to the configured own-key endpoint. Your provider account and its terms govern the direct processing.Privacy policy
MetaA hosted chat model provider when selected; creator of the Muse Voice Transcribe model, whose serving provider can vary.Conversation messages, project context, tool arguments and results on its selected hosted chat route. The transcription input goes to the actual serving provider; the model creator is not necessarily its host.—
The provider serving Meta's Muse Voice Transcribe (varies)Runs the transcription model reached through OpenRouter.Audio chunks, language and any supplied vocabulary hints. The serving provider can vary; transcription does not use the same provider-pinning and data-collection restrictions as hosted chat.—
Stripe, including LinkOur payment processor for checkout and the customer portal, and, as Link, the merchant of record that sells purchases and handles their sales tax, VAT or GST; holds the Temno customer profile and saved payment methods addressed during verified account deletion.Payment information and billing address; email, customer/subscription identifiers, selected plan, tax and transaction information. Any retained billing records are identified separately.Privacy policy; Link privacy policy
Google WorkspaceOur support mailbox service for receiving and managing support messages and attachments, including privacy/deletion requests.Support correspondence and attachments, including information supplied for privacy and deletion requests.Data-processing addendum
CloudflareOur DNS and website edge provider; delivers the website, stores and serves its videos, measures website visits without cookies, and forwards the website's email-update signup, confirmation and unsubscribe requests to Temno's accounts service.DNS lookups; website request metadata such as IP address, timestamps and requested resources; the website visit measurements described above; email address in a signup request and signed confirmation/unsubscribe links in transit. The Temno Worker does not store or log request content; Cloudflare may process operational and security records under its policies.Privacy policy
CybranceeOur service host for the accounts and hosted-generation services.The information processed by those services; service hosts process IP addresses, timestamps, requested resources, errors and security information to deliver and secure services.Terms of service
Microsoft (Windows and DPAPI)The operating-system platform: Windows protects saved Temno account sessions using DPAPI. Windows diagnostic settings apply separately.Account session information is protected locally; operating-system diagnostics are separate and depend on Windows settings. This does not add an automatic Temno cloud crash-report sender.Privacy statement
Hugging Face (optional model downloads)An example of an external site from which you may separately obtain a model; its privacy policy governs that visit.Information from your separate visit or download under that site's policy. Local search does not upload your media to it.Privacy policy
Palmier/Convex (legacy connection)A possible endpoint for the legacy HTTP custom-generation connection.Requests and uploads sent to that configured service; your provider account and its terms govern that processing. This is a conditional connection, not a statement that it is active.Convex privacy policy
Generation catalog model creators and familiesThe media catalog includes model families such as GPT Image (OpenAI), Nano Banana, Grok Imagine, MAI Image (Microsoft), Muse Image, Krea, Ideogram, Seedream, Reve, Recraft, FLUX, MiniMax, Seedance, Wan, Happy Horse, Veo, Gemini Omni, Kling, LTX, VEED, Luma, ElevenLabs, Seed, Lyria, Sonilo, Mirelo, Gemini, Topaz, Bytedance and SeedVR.The selected route determines the actual recipients of the generation request and selected files. A model family or creator name does not by itself establish that the creator receives the content.—
Generation serving partners and delivery networks (vary by route)May serve the selected generation model or deliver its content alongside the model-hosting provider.May process the generation request and selected content, as described above.—
Your mailbox providerProcesses delivered account and update messages.Delivered messages, including their content and links; recipient mailboxes have their own retention requirements.—
Other configured endpoints, connected MCP clients and their providers, update/download hosts and HTTPS media hostsThe user-selected or configured services described above; these roles do not name a single fixed provider.Connected clients receive requested tools/project information and may send it to their providers. Custom connections receive their requests/uploads. Update/download and HTTPS media hosts receive requests and IP addresses. Your arrangements and the selected provider's terms govern their processing.—

Providers can change, and we update this table when they do. The role descriptions and the policy's points about model creators versus hosts, selected routes and independently retained provider copies continue to apply.

© 2026 Temno. The source code will be published at launch under GPL-3.0.

FAQLaunch updatesTermsPrivacyAcceptable UseRefunds