Privacy policy.
How information is handled when you use Dayfaro.
Last updated October 14, 20261. Who is responsible for your data
Dayfaro (dayfaro.com) is the data controller for the personal data described in this policy. Contact support@dayfaro.com about this policy or your data.
This policy covers dayfaro.com, the Dayfaro workspace, the CLI and SDK, the MCP server, and Dayfaro in ChatGPT, Claude, and other connected apps. Those apps handle the information they receive under their own policies.
If you build Dayfaro into your own product and send us other people’s personal data, you must have the right to do so and inform them. Contact us if you need a data processing agreement.
2. Information we process
Account: your email address, account identifier, password (stored only as a scrypt hash), verification and password-reset records, sign-in sessions, and the onboarding answers you give: name, role, goal, topics, and preferred cadence.
Google or GitHub sign-in, if you choose it: the verified email address and provider account identifier. We do not keep their access tokens after sign-in.
Your content: source text, script and voice instructions, generated scripts and your edits, audio, transcripts, and the language, length, style, and voices you choose. Content can contain personal data about other people; only submit it if you are allowed to.
Connected apps: which app you approved, its permissions, and when you connected or disconnected it. To issue connection tokens, Supabase keeps a linked sign-in identity containing your email address.
Access keys: the name you give a key, a short prefix, a hash of the key, and when it was created, last used, or revoked. The full key is shown only once. When you sign in to the CLI through the browser, we also keep the device name it reports and the status of the request for one day. The CLI stores its key only on your computer, in a file readable by your user account.
Credits and purchases: your balance and a ledger of purchases, discounts, generation charges, refunds, and adjustments, plus Polar customer and order references and the email used at checkout. We never receive card numbers.
Support: messages and attachments you send to support@dayfaro.com.
Business research: publicly available professional names, roles, company websites, published business contact details and source excerpts relevant to potential use of Dayfaro. We also keep contact permission, outreach history, interview notes and agreed next steps in a private staff workspace. We do not infer private email addresses.
You need to give an email address to create an account or buy credits. Without one we cannot provide the service.
Technical records: IP address, request and error details, job status, model usage, and generation costs. IP addresses are used for rate limiting; we keep those counters for up to one hour.
3. How and why we use it
To provide the service you request: accounts, sign-in, generating, storing, playing, and exporting podcasts, connecting apps and access keys, and charging credits. Legal basis: performance of our contract with you (GDPR article 6(1)(b)).
To process purchases, keep accounting and tax records, and handle content reports and requests from authorities. Legal bases: contract and legal obligation (article 6(1)(b) and (c)).
To keep the service secure and working: rate limiting, preventing fraud and misuse, fixing faults, answering support requests, and establishing or defending legal claims. Legal basis: our legitimate interests (article 6(1)(f)). You can object to this processing at any time.
To understand visits and product journeys and diagnose usability issues.
We send emails needed for your account, such as verification, password reset, and purchase confirmations. We do not send marketing emails without your consent.
We research potential business customers and prepare relevant messages using public professional information. Legal basis: our legitimate interest in understanding business needs and developing Dayfaro (article 6(1)(f)). AI assists research and drafting; a fit score is a provisional business hypothesis. Public contact information does not itself give permission for marketing. You can object to this research or ask us to stop contacting you at support@dayfaro.com.
We do not sell or rent personal data, show advertising, or use your content to train AI models. We do not make decisions that have legal or similarly significant effects on you solely by automated means.
4. AI generation and ChatGPT
To create a podcast we send your source text, instructions, settings, and script to OpenRouter, which routes them to Google’s Gemini models: Gemini Flash writes the script and Gemini text-to-speech produces the voices. Your account email and payment details are not sent. Links are fetched only when you enable the optional Online search feature.
When you enable Online search (off by default), we send your research request to the script model to plan retrieval. The generated search queries, objectives and public URLs are sent to Parallel Web Systems. Retrieved excerpts are sent to the script model to write your episode. We store source links, publication dates where available, coverage notes and script citations with your podcast. The excerpts are processed for generation and are not saved as a separate full-text research archive. Do not include secrets or private URLs in research requests.
OpenRouter and Google process this content under their own terms and may keep it for a limited period, for example to detect abuse. We use their paid developer services rather than consumer AI products.
When you use Dayfaro in ChatGPT, ChatGPT decides what to send to Dayfaro, usually the text and options for your podcast. Dayfaro does not receive your other conversations. Dayfaro returns the information each request needs, such as podcast titles, status, scripts, transcripts, playback links, your email, and your credit balance. That information becomes part of your ChatGPT conversation, which OpenAI handles under its privacy policy.
You can disconnect ChatGPT or any other app in Account settings. Disconnecting stops access immediately. It does not delete information the app already received.
5. Service providers and international transfers
Render, Frankfurt, Germany: runs the Dayfaro servers, including the MCP server, generation workers, and job queue. Traffic passes through Cloudflare, Render’s network provider.
Supabase, Frankfurt, Germany: database, storage for audio and transcripts, and the sign-in service for connected apps.
Vercel: hosts the website and the app interface.
OpenRouter, United States, and Google: script and speech generation, plus analysis of public business information and drafting of business messages.
Parallel Web Systems, United States: optional podcast web search and extraction, and public business research for our private customer-development workspace. Research requests are processed under Parallel’s terms and privacy policy (https://parallel.ai/privacy-policy).
Polar: merchant of record for credit purchases. Polar and its payment processors handle checkout, payment details, taxes, receipts, and refunds as an independent controller under Polar’s privacy policy.
Resend, United States: sends account, purchase and opted-in business emails and, using Amazon Web Services, receives support messages and outreach replies. Replies are forwarded to the Dayfaro operator’s monitored inbox and stop automated follow-ups.
PostHog, United States: usage analytics and session replay with private content masked.
Google and GitHub: sign-in, only if you choose it.
OpenAI: only when you use Dayfaro in ChatGPT. OpenAI is an independent controller of your ChatGPT conversations.
Where personal data is transferred outside the European Economic Area, we rely on the EU–US Data Privacy Framework for certified recipients or on the European Commission’s Standard Contractual Clauses. Contact us for details of the safeguard used for a provider.
We may disclose information when required by law, to protect people’s rights and safety, or in a business transfer with the same protections described here.
6. Browser storage and analytics
The app stores your sign-in token, preferences such as playback speed, and whether you accepted the cookie notice in your browser’s local storage. Sign-in tokens expire after 24 hours. Signing out removes the token from that browser.
PostHog measures visits and product actions and records page interactions to help diagnose problems. Your browser activity is linked to your account when you sign in. Recordings show the site's own interface text. Anything you type, your podcast titles, scripts, sources and account details are masked, and transcripts, credentials, media and request bodies are excluded. Account-connection and admin pages are not recorded.
7. How long we keep information
Account information and content: until you delete them or ask us to close your account.
A deleted podcast is removed from your library and our database immediately. Its audio and transcript files are deleted from storage, usually within an hour.
Account closure: we complete closure requests within 30 days. We keep the credit ledger and purchase records for as long as accounting and tax law requires, generally ten years in Italy, and information needed for an ongoing dispute or legal claim.
Links and sessions: playback and download links expire after one hour, sign-in sessions after 24 hours, and verification and password-reset links after 30 minutes. A connected app keeps access until you disconnect it.
Technical records: rate-limit counters for up to one hour. Hosting providers keep request logs for a short rolling period set by their service.
Support messages: for as long as needed to resolve your request and any follow-up.
Business research and outreach: until no longer needed for the business conversation or you request deletion. We retain a minimal suppression record when you opt out so that deleting a contact does not cause us to contact them again.
Provenance records: for each recording, an identifier, its creation time, the generating system, and fingerprints of the audio file and transcript, with no content or account details. We keep them indefinitely so that anyone can check a published file at dayfaro.com/verify, even after the podcast is deleted. Files uploaded for checking are processed in memory and not stored.
8. Security
We store passwords and access keys only as hashes, encrypt traffic with TLS, keep podcasts in private storage reachable only through links that expire, require PKCE for app connections, and let you revoke keys and connected apps at any time.
No service can guarantee absolute security. If a personal data breach puts your rights at risk, we will notify you and the competent authority as the law requires.
9. Your rights
You can ask to access, correct, delete, or receive a portable copy of your personal data, to restrict processing, or to object to processing based on legitimate interests. You can withdraw consent at any time without affecting earlier processing.
Email support@dayfaro.com from the address on your account. We reply within one month, extendable by two months for complex requests, and may need to verify your identity. Requests are free.
You can complain to the Italian data protection authority, the Garante per la protezione dei dati personali, Piazza Venezia 11, 00187 Rome (garanteprivacy.it), or to the authority where you live or work.
If you live in a US state with a consumer privacy law, you may have similar rights, including the right to appeal our decision on a request. We do not sell or share personal data for cross-context behavioural advertising, and we will not discriminate against you for exercising your rights.
10. Age and changes to this policy
Dayfaro is for people aged 18 and over and is not directed to children. If you believe a child has given us personal data, contact us and we will delete it.
We will post changes here with a new revision date. If a change materially affects how we use your data, we will tell you by email or in the app before it takes effect.
Read our Terms of service.