Privacy Policy

Nightshift (the “Service”) is an automated video production tool: a web dashboard on this domain and a pipeline that researches, writes, narrates, renders and uploads videos to YouTube channels its users connect. The Service is operated by [operator name to be published] (“we”, “us”), [country to be published]. Contact: [contact address to be published].

This policy explains what information the Service collects, how it is used and shared, and the choices you have. It applies to this website and to the automated pipeline that acts on your behalf.

• Account information: your email address and a password, handled by our authentication provider (Supabase Auth). We never see or store your password in readable form.
• Configuration you enter: channel names, niche, language, voice and style choices, schedules, series, and your review decisions (for example, approving a video), which are recorded with your user id as an audit trail.
• API keys you enter for third-party services: they are encrypted in our server the moment they arrive, written to our pipeline's encrypted secret store (GitHub Actions secrets), and discarded. They are never saved in our database, shown back to you, or logged.
• Telegram notifications, only if you connect a chat: the Telegram chat id and the first name or @username Telegram gives us for it, the language you chose for the messages, which notifications you switched on and when the last message was delivered. You can pause or disconnect the chat in Settings at any time; disconnecting deletes this data.
• Google user data you authorise us to access, described in section 3.
• E-mail preferences: whether you want an e-mail when a video is ready or a weekly summary, and the language you use the app in, so the e-mails are written in it. “Video ready” e-mails are service messages about work you started: they are on until you turn them off in Settings or with the link in any of them. The weekly summary is off unless you turn it on. We send no marketing e-mail.
• Technical data: our hosting and database providers record standard request logs (such as IP address, browser type and time of request) to operate and secure the Service. We do not use analytics, advertising or tracking tools.

When you connect a YouTube channel, you are sent to Google’s own consent screen, where you choose the Google account and see exactly what is requested. We request the following OAuth scopes and use each one only for the purposes listed:

We do not request access to your Gmail, Google Drive, contacts or any other Google service, and we do not read your YouTube watch history, subscriptions or private messages.

Google user data is used only to provide and improve the user-facing features you see in the Service: uploading and captioning your videos, adding them to your playlists, posting the engagement comment, preventing duplicate uploads, showing your channel’s performance in your dashboard, and choosing future topics from what performed well and what your audience asked for.

To produce those insights, the text of comments on your videos and your videos’ performance figures may be sent to our AI text provider (Google’s Gemini API) to be classified and summarised for your channel. We store the result — for example, a topic your audience requested and how often — not the comment text itself.

Nightshift’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

• we use Google user data only to provide or improve the user-facing features described above;
• we transfer it to others only as necessary to provide those features (the processors in section 7), to comply with applicable law, or as part of a merger, acquisition or sale of assets with notice to you;
• we do not use or transfer it to serve advertisements, including personalised or retargeted ads;
• we do not sell it, and we do not use it to determine creditworthiness or for lending purposes;
• we do not allow humans to read it unless you give us affirmative consent for specific data, it is necessary for security purposes (such as investigating abuse), it is needed to comply with applicable law, or it has been aggregated and anonymised for internal operations;
• we do not use it to develop, improve or train generalised artificial intelligence or machine-learning models.

After you consent, Google returns an access token and a refresh token to our server. Where they are kept depends on whose channel it is:

• Channels operated by us (our own organization): the token is immediately encrypted (sealed to our pipeline repository’s public key) and stored as an encrypted GitHub Actions secret, which only the pipeline can read when it runs.
• Channels that your organization connects: only the refresh token is kept, encrypted at rest in Supabase Vault. The dashboard can store or delete it but can never read it back — not for you, and not for anyone in your organization; only our pipeline reads it, with a server-only key, while a run for that channel is in progress, and it is held in memory or in a file readable only by the pipeline that is deleted when the run ends. When you disconnect the channel, the stored token is destroyed.

In both cases tokens are never sent to your browser and never written to a log. What the dashboard shows is only non-secret connection information: which YouTube channel is connected, when and by whom, and which permissions were granted. Our OAuth client credentials are kept in server-only configuration.

During the connection a short-lived, http-only cookie (10 minutes) protects the flow against cross-site request forgery.

We use the following providers to run the Service. Each receives only what it needs for its task.

Only Supabase, GitHub, Google and the notification services in this list receive Google user data, and only for the purposes above. We do not sell personal information to anyone.

Payments. Credits are sold through Paddle, our online reseller and Merchant of Record: when you buy credits, you enter your payment and billing details in Paddle’s own checkout, and Paddle processes them as the seller under the Paddle Privacy Notice. We never receive or store your card details or billing address. Paddle sends us only what we need to credit a purchase and to reverse it on a refund: the transaction and refund ids, the amount and currency paid, the credits bought, and the organisation (and, where known, the user) the purchase is for. We keep these records with your organisation’s credit history for as long as its account exists, or longer where tax or accounting law requires it.

• Google tokens are kept while your channel is connected. They stop working the moment you revoke access, and we delete them when you disconnect the channel or ask us to.
• Review copies of videos in our storage are limited to the five most recent per channel; older copies are deleted automatically.
• Pipeline output (the rendered video, thumbnails and run log) is kept by GitHub Actions for 7 days and then deleted automatically.
• Account data, configuration, video records and performance figures are kept while your account is active, and deleted within 30 days of a verified deletion request.
• Audit records of approvals and other decisions are kept as long as the account exists, because they are the record of who authorised an action on a channel.

You can revoke Nightshift’s access to your Google account at any time at https://myaccount.google.com/permissions. To delete your account and the data we hold, email [contact address to be published].

Nightshift uses only what it needs to work. We set no advertising, tracking or analytics cookies, we use no third-party analytics, and we show no cookie banner: everything below is strictly necessary for something you asked for (signing in, a choice you saved, or protecting a sign-in or a connection while it is in progress).

Third parties. The Pricing page loads a price-preview script from Paddle, our payment provider, so that prices show in your currency. The script and any cookie it or Paddle’s content network sets (for example a bot-protection cookie) are Paddle’s; see the Paddle Privacy Notice. Checkout runs in Paddle’s own window. When you connect your YouTube account you are sent to Google. We load no other third-party scripts.

Page statistics. To see which public pages are read, we count page views ourselves, on our own servers: for each public page and each day, how many views, from which referring website (its name only), on a phone-sized or a larger screen, and in which language. This uses no cookie and no local storage, and stores no IP address, user agent or identifier, so it cannot be tied to you or to your other visits. If your browser sends Do Not Track or Global Privacy Control, nothing is counted. No data goes to an analytics provider.

You can delete cookies and local storage in your browser’s settings at any time. The Service then forgets your language, theme and view choices, and you are signed out.

Traffic is encrypted in transit (HTTPS). Database access is restricted per user by row-level security, the website uses only a restricted public key, and secrets are encrypted before they are stored. No system is perfectly secure; if we learn of a breach affecting your data we will notify you as required by law.

You can disconnect a channel, revoke Google access, and ask us to access, correct, export or delete your personal data by emailing [contact address to be published]. Depending on where you live, you may have further rights under local law, including the right to complain to a data-protection authority.

Our providers operate in the European Union, the United States and other countries, so your data may be processed outside your country. Where the law requires it, we rely on the providers’ standard contractual safeguards.

The Service is not directed to children and may not be used by anyone under 13, or by anyone below the minimum age YouTube requires to manage a channel in their country.

Nightshift uses YouTube API Services. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service. Google’s handling of your data is governed by the Google Privacy Policy.

We will post any change on this page and update the effective date ([date to be published]). If a change materially affects how we use Google user data, we will tell you in the Service and ask for your consent again where required.

[operator name to be published], [country to be published]. Email: [contact address to be published].