Privacy Policy
Last updated: 23 October 2026.
- 01
Introduction
Postflare is operated by Emil Lykke in Denmark, the controller of the personal data described here. Contact emillykkeg@gmail.com with questions or privacy requests. This policy covers the website, sign-in, subscriptions and the YouTube features described below.
- 02
Account and billing information
We process your email address, account identifier, profile information you share at sign-in, subscription status, payment references and support messages to provide your account, subscription and support. Clerk handles authentication. Stripe handles payment details; Postflare does not receive your full card number. Google sign-in shares basic identity information and does not itself grant access to your YouTube Channel.
- 03
YouTube availability and permissions
YouTube publishing is being prepared and is not yet available in the public application. The following YouTube sections describe the processing that will apply when you choose to connect a Channel. That connection uses YouTube API Services and separate Google consent for youtube.upload and youtube.readonly. Upload permission lets Postflare send your videos to YouTube. Read-only permission identifies the Channel you selected and reads Channel capabilities and upload processing status. Postflare does not ask for your Google password.
- 04
YouTube data and use
When you connect a YouTube Channel, Postflare needs its identifier, name, image, capabilities, authorization tokens and the identifiers and processing status of uploads made through Postflare. It processes the videos, titles, descriptions, thumbnails, audience settings, privacy choices and schedules you provide to carry out your publishing instructions. Videos and their metadata are sent to YouTube for the Channel you select. The connection is not permission to publish without your instruction. You choose the privacy setting for each Publication.
- 05
Google API data restrictions
Postflare uses Google user data only to provide the features you request. We do not sell it, use it for advertising, transfer it to data brokers or use it to train generalized artificial intelligence models. Postflare use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
- 06
Providers and sharing
Railway hosts the application, Neon stores application data, Cloudflare provides the network edge and file storage, Clerk provides authentication, Stripe provides billing, and Resend sends service emails. These providers process the information needed for their role. Google and YouTube receive identity requests or content when you use their features. Authorized support access is limited to operating the service and resolving your requests. We may disclose information when required by law. Providers may process data outside your country, including outside the EEA, subject to applicable data protection safeguards.
- 07
Retention, deletion and revocation
We keep account and subscription records while needed to provide the service, meet legal obligations and resolve disputes. Contact emillykkeg@gmail.com to request account or data deletion. When YouTube publishing is enabled, you can also revoke Postflare access in your Google permissions settings. Requests to delete stored YouTube data, or revocation of access, require deletion of the affected authorization tokens and YouTube API data as soon as possible and within 7 calendar days. This does not delete videos already on YouTube; manage those in YouTube Studio. Retained billing records required by law are separate from YouTube data.
- 08
Publishing data retention
Before YouTube publishing becomes available, its retention and deletion controls must be in place. The planned file retention is 30 days after a Post settles, including failed Publications, or 60 days after the last edit of a Draft. Files are also removed after 90 days without a Subscription. YouTube API data must be refreshed or deleted within 30 days, and the 7-day deletion requirement after revocation or a deletion request takes precedence. Your own content and legally required billing records follow their separate retention rules.
- 09
Cookies, analytics and logs
Authentication uses cookies and browser storage to keep you signed in. Our hosting and network providers process request metadata such as IP addresses, browser information, requested pages, timestamps and errors for delivery and security. If PostHog analytics is enabled, it collects page views, page exits, interactions, URL and referrer metadata and browser identifiers through cookies and local storage. Its configuration can enable session recording. YouTube embeds, when shown, send device and playback information to Google and may show content or advertisements under Google policies.
- 10
Legal basis, security and your rights
We process account, billing and publishing information to perform our contract with you, required records to meet legal duties, and security and service diagnostics for our legitimate interest in running a reliable service. Where consent is required, you may withdraw it. We use HTTPS and restrict access to service data; no internet service can promise absolute security. You may request access, correction, deletion, restriction, portability or object to processing by emailing emillykkeg@gmail.com. You may also complain to the Danish Data Protection Agency or your local supervisory authority.
- 11
Changes to This Privacy Policy
We publish changes on this page and update its date. We will notify you before material changes to how we use your personal data take effect. This policy will be updated when YouTube publishing becomes available so it reflects the actual service.
- 12
Contact Us
Postflare is operated by Emil Lykke in Denmark. Contact emillykkeg@gmail.com about this policy, access to your personal data, correction, deletion or other privacy requests.