Privacy policy

Effective October 28, 2026

Dayclip ("we", "us") provides this service. Contact: hello@dayclip.ai.

Dayclip turns footage from a camera station in a business (for example a barbershop) into short videos that the business owner reviews and may post to their own social media accounts. This policy explains what we collect and how we use it, for business owners and for the people who appear in their footage.

What we collect

Owner account: the sign-in method the owner chooses (a mobile phone number for text codes, an email address for sign-in links, or the name, email address and profile picture from Google Sign-In), plus the business name, contact email, type and time zone.
Camera footage: video recorded by the Dayclip Station the owner installs, during the business hours the owner sets and never with sound. It can show the owner, staff, customers and visitors in the Station's view.
Phone sessions and uploads: video recorded in the owner app and photos or videos the owner selects. Phone sessions use the camera only by default; owners can explicitly enable the microphone after confirming permission from everyone whose voice may be recorded. Recording stops when the owner ends the session. These visual edits use background music rather than the recorded conversation.
Still pictures: pictures the Station sends while the owner or their team is lining up the camera or watching it live. Only the latest one is kept.
Clips: short videos and captions made from that footage.
Connected social accounts: when an owner connects Instagram, Facebook, TikTok, YouTube or another platform, we receive access tokens and basic account details (account name, page or channel name, profile picture) from that platform, and the IDs and links of posts we publish on the owner's instruction.
Setup requests: the email address and business type entered on dayclip.ai, used only to contact you about Dayclip setup and availability.
Device and usage data: the station's model, app version, status and error logs, and standard server logs.
Agreement records: when an owner accepts the recording agreement or changes whether Dayclip may feature their shop, we keep the wording they saw, the time and basic device details.

How we use it

To record, analyse and edit footage into clips for the owner.
To show clips to the owner and, only when the owner approves a clip, publish or schedule it to the social accounts they connected.
To keep the service running, secure and supported.
To improve how Dayclip finds moments and edits clips.
To show a shop in Dayclip's own marketing, only when the owner allows it (see Marketing).

We do not sell personal data or use it to target ads, and we use social platform data only to publish the owner's approved posts and show their outcome in the app.

YouTube API Services

Dayclip uses YouTube API Services to connect a business owner's YouTube channel and upload the clips the owner approves. By using Dayclip you agree to the YouTube Terms of Service (see our Terms). Google's handling of your information is described in the Google Privacy Policy (http://www.google.com/policies/privacy).

What YouTube information Dayclip accesses and stores

When you connect a channel: your Google profile name and picture (to show which Google account you signed in with), your YouTube channel's ID, title and handle, and the authorization tokens Google issues to Dayclip.
When you approve an upload: the video, title, description, privacy and "made for kids" choice you reviewed, and the video ID, link and upload status YouTube returns.
Dayclip does not access YouTube analytics, comments, subscribers or other people's data, and does not download videos from YouTube.

How Dayclip uses it

To show you which channel is connected and whether it needs attention.
To upload a clip to your channel, only after you review it and press Publish for that clip and that channel.
To show you the result of each upload, with a link to the video.

How Dayclip processes and stores it

The tokens and channel details are held by our publishing service (the open-source Postiz software, which we run ourselves on our own Google Cloud server in the United States). Upload results are stored in Dayclip's database on Google Cloud (Firestore) in the United States. Google Cloud encrypts this data at rest. Backups of the publishing service are deleted automatically after five days.

How often Dayclip refreshes or deletes it

Every day, Dayclip uses the YouTube API to reread your channel's title and handle with your authorization, which also confirms that your authorization is still valid. Dayclip does not keep your channel's profile picture.
Channel details that could not be refreshed, and the video IDs, links and results of uploads, are deleted after at most 27 days, in our publishing service and in Dayclip's database.
If Google tells us you revoked Dayclip's access, Dayclip deletes the tokens and channel details at that daily check (failed checks are retried hourly).
When you remove the channel in Dayclip, Dayclip revokes its access at Google and deletes the tokens and channel details.
When you ask us to delete your data, or delete your Dayclip account, we delete stored YouTube data as soon as possible and within seven calendar days.

How Dayclip shares it with internal parties

People you invite to your shop in Dayclip can see the connected channel's name and upload results, and can publish only as you allow them to.
People who work on Dayclip access YouTube data only when needed to provide support you ask for, keep the service secure, or meet legal requirements. It is not shared with other Dayclip customers.

How Dayclip shares it with external parties

YouTube (Google): the video and the details you approved, when you press Publish.
Google Cloud: hosts and stores Dayclip, as described above.
Notification providers: our email provider (Namecheap Private Email) and, for the mobile app, Expo's push service and Apple's or Google's notification service may carry a notice that names your connected channel and the next step. Notices never contain tokens or video.
Legal reasons and business transfers: as described in How we share, transfer and disclose Google user data below.

Dayclip does not sell YouTube data, use it for advertising, or send it to analytics providers, and does not allow third parties to serve ads in Dayclip.

Revoking access and deleting data

In addition to removing the channel in Dayclip, you can revoke Dayclip's access to your data at any time on the Google security settings page: https://security.google.com/settings/security/permissions. Deleting data stored by Dayclip does not delete anything stored by YouTube, such as videos already uploaded; to delete those, use YouTube Studio or another YouTube app. To ask us to delete your data, use our deletion instructions. Questions or complaints about Dayclip's privacy practices: hello@dayclip.ai.

"Google user data" means information we receive from Google APIs: the name, email address and profile picture from Google Sign-In, and the Google profile, YouTube channel information and authorization tokens described above. We share, transfer or disclose it only as follows:

Service providers that run Dayclip. Google Cloud (Cloud Run, Compute Engine, Firestore, Cloud Storage, Firebase Hosting, Firebase Authentication and Secret Manager, in the United States) hosts and stores it, including encrypted backups. Our publishing service is the open-source Postiz software, which we operate ourselves on our own Google Cloud server; it holds the authorization tokens and sends uploads to YouTube. Postiz's developers do not receive this data. We send the owner account notices, such as clip-ready messages and alerts that a connected channel needs attention, through our email provider (Namecheap Private Email) and, for the Dayclip mobile app, Expo's push-notification service and the phone's Apple or Google notification service. A notice can go to the email address from Google Sign-In and can name the connected channel and the next step; it never contains authorization tokens or video.
YouTube. We send a video and the title, description, visibility and audience choices to YouTube only when the owner approves that upload in Dayclip.
Legal and safety reasons. We disclose information when required by law, subpoena or other legal process, or when necessary to protect the security of Dayclip, its users or the public.
Business transfer. If Dayclip is merged, acquired or its assets are sold, Google user data may transfer to the successor, which must continue to follow this policy. We will notify affected owners first.

We do not sell Google user data, use it for advertising, share it with other Dayclip customers, send it to analytics providers, or use it to develop, improve or train generalized artificial-intelligence or machine-learning models. People who operate Dayclip access it only when needed for security, support you request, or legal compliance. Dayclip's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Retention, deletion and revocation of this data are described in YouTube API Services above, in the Retention section below and in our deletion instructions.

Browser storage

We use browser storage and authentication cookies to keep you signed in and maintain the account-connection flow. Connecting a social account opens that platform's sign-in service, which has its own privacy and cookie policies.

People in the footage

The business owner decides where the Station goes and agrees to our recording rules: a visible "recording in progress" sign at the door and near the work area, telling staff before recording starts, never pointing the Station at restrooms, changing rooms or other private places, pausing or keeping out of view anyone who asks, and getting a parent's or guardian's permission before posting anyone under 18. The Station also shows on its own screen that it is recording. Owners review every clip before it is posted and are responsible for any consent the law requires.

If you appear in footage from a business that uses Dayclip, you can ask the business not to film or post you, or to delete clips that show you. You can also email us: we will help, and we will remove or blur you in anything Dayclip itself has published. See Delete your data.

Who can see footage and clips

The owner, and the people the owner invites to the shop in Dayclip.
People who work on Dayclip, when needed to support the shop, check quality, keep the service safe or meet legal requirements. Each time raw footage is opened, it is recorded in the shop's log.
AI assistants our team sometimes uses to review footage or help edit clips, from providers such as Anthropic, OpenAI and Google. Those providers process this material under their own terms.
Google Cloud AI, for Smart edit: it watches a small, low-resolution copy of the photos and videos the owner adds, with their sound and a transcript, to find the moments worth clipping, and watches each finished clip to check it before the owner sees it. Google processes this on its global network under the Google Cloud terms, which don't allow it to use this content to train its models.
TypeSafe, an AI service that helps choose and check what goes into clips. For a spoken video it receives the text of what is said (in English, translated if needed); for Smart edit it also receives short descriptions of the chosen moments and the captions and on-screen text we draft. It doesn't receive the video itself and doesn't train its models on it.
Google Cloud Speech-to-Text and Translation, for a video the owner adds in a language our own transcriber doesn't handle well, such as Amharic: the audio is transcribed in Google Cloud's Europe region, and the text is translated to English so the moments can be chosen.

Face data

Dayclip records ordinary video, so people's faces can appear in footage and clips. This section explains exactly how we handle that.

What the app does not collect: the Dayclip apps do not use Face ID, the TrueDepth camera, face scanning or facial recognition, and do not create face templates, faceprints or any other biometric identifier. Dayclip never tries to identify who a person is.
What face information we derive and why: to edit a clip, our servers look at frames of the footage to find where the customer's head is (a rectangle's position in the frame) and whether their face is visible, so the clip is framed on the work and shows the finished result. Before the owner sees a clip, we check sampled frames for faces outside the customer's area, and reject the clip if a bystander's face would be shown. The only results are frame positions, yes/no answers and counts. They are used only to frame and check that clip.
Who processes it: Dayclip's own servers on Google Cloud in the United States, and Google Cloud AI (Vertex AI), which analyses low-resolution frames under the Google Cloud terms and does not use them to train its models (see Who can see footage and clips). We do not sell face information, share it with other third parties, or use it for advertising, identification, tracking people across videos or training third-party AI models.
Storage and retention: the frame positions and check results are stored with that clip's edit record in Google Cloud in the United States and deleted when the clip is deleted, when the owner deletes their account, or on request. Raw footage is deleted as described in Retention (within 48 hours, or after at most 90 days for a business that joins the pilot archive).
Deletion: owners can delete any clip in the app at any time; anyone who appears in footage can ask us to delete or blur it through Delete your data or hello@dayclip.ai.

Payments

If you buy video minutes, Stripe processes the checkout information you provide, including payment and billing details. Dayclip sends purchase and workspace identifiers to Stripe and receives the payment amount, currency and status so it can add minutes once. Dayclip does not store your full card details. Stripe handles payment information under its Privacy Policy.

Purchase receipts and the identifiers needed to reconcile payments, prevent duplicate credit and resolve payment problems can remain after account deletion. Contact hello@dayclip.ai about retained billing records.

Marketing

Dayclip shows a shop's name, logo or clips in its own marketing (our website, social media, app-store pages and sales material) only if the owner turns this on. We blur or leave out anyone who hasn't agreed to appear, and we remove or blur anyone who asks us to within 7 days. Sample reels made with AI are labelled as AI samples.

Retention

Raw camera footage is deleted automatically within 48 hours of upload, except for businesses in the pilot program below.
A video the owner uploads to clip, and the transcript we make of it, are deleted once its clips are made, or once it fails. Uploaded photo/video collections and phone-session source files follow the same rule. An upload that never finishes is deleted within 24 hours.
Phone recordings are temporarily saved in this browser on this device to recover an interrupted session or upload. The app removes its saved recording after the cloud confirms receipt, or when the owner discards it. Browser storage can be cleared or evicted by the device; it is not a permanent backup. A copy the owner downloads stays on their device until they delete it.
Clips are kept until the owner deletes them or closes their account.
The latest still picture from a Station is replaced as new ones arrive and is deleted with the shop.
Agreement records are kept, including after an account is deleted, as evidence of what the owner agreed to.
Social account tokens and profile details support the connected account. Removing an account stops its use for new posts. Operational records and backup copies can remain after disconnection; contact us to request deletion of retained data. For YouTube data, see How often Dayclip refreshes or deletes it; deletion requests are completed as soon as possible and within seven calendar days, as explained in our deletion instructions. Minimal internal deletion records prevent a removed connection from being restored from an older backup.
Copies of media sent to a social platform are also governed by that platform's own policies once published.

Pilot program

While Dayclip is in its pilot, a business that agrees in writing can let us keep its raw camera footage for up to 90 days in a private archive, so we can test and improve how clips are made. Archived footage is used only to build and test Dayclip’s editing. It is not shared outside Dayclip and its service providers, is not used for advertising, and is deleted automatically after 90 days. The business can ask us to delete it sooner at any time, and anyone who appears in it can ask through Delete your data.

Website and product analytics

In the native iPhone and Android owner apps, we record when you open a clip review and when the clip actually starts playing. These observations are sent through Dayclip's authenticated API to PostHog, using the same pseudonymous account and shop identifiers as our service events. They include the action, its time and whether it came from iPhone or Android. Video, captions, clip links and contact details are never included. You can turn these native review and playback observations off in Settings → Privacy & data → Product analytics. Your clips, review decisions and playback still work when it is off. The essential service-outcome events described below continue to operate.

We use PostHog to understand visits and improve Dayclip. It records page and screen views, approximate traffic source and region, device and browser information, and actions such as playing a demo, joining the waitlist, signing in, starting or recovering a recording, sending an upload, reviewing a clip and approving a publication. It uses a random browser identifier stored in browser storage and a secure cookie for up to 90 days to connect visits between dayclip.ai and app.dayclip.ai; signed-in app events use pseudonymous identifiers. We do not send email addresses, phone numbers, passwords, sign-in codes, camera footage, clips, captions, or social-platform authorization data to PostHog. Analytics session replay and automatic collection of form contents are disabled. The phone recordings owners intentionally create are a separate content feature and are never sent to PostHog. Analytics is not used for advertising.

You can turn browser analytics off using the control in the website footer. We also respect browser Do Not Track and Global Privacy Control signals. Turning it off does not affect the waitlist or the app. Essential server-side service records still operate; pseudonymous service-outcome events help us understand onboarding, confirmed uploads, clip processing, connection and publishing reliability.

Service providers

We use Google Cloud and Firebase (hosting, storage, database, sign-in and backups) in the United States; a text-message provider for sign-in codes and notifications; Namecheap Private Email for account email; Expo's push-notification service for the Dayclip mobile app; and a self-hosted publishing service (the open-source Postiz software, run on our own Google Cloud server) that sends approved posts to the platforms the owner connected. These providers process data only to run Dayclip. For Google user data, the complete list of recipients is in How we share, transfer and disclose Google user data.

Your choices

Owners can delete any clip, disconnect any social account, pause the station, and turn Dayclip marketing on or off from the app.
People who appear in footage: see People in the footage.
Anyone can ask us to access or delete their data: see Delete your data.
You can also revoke Dayclip's access from your social platform's settings at any time.

Your rights

Depending on where you live, for example in California, the European Union or the United Kingdom, you may have the right to know what personal information we hold about you, to get a copy of it, to correct or delete it, and to object to or limit some uses. Email hello@dayclip.ai; we will answer within 30 days and will not treat you differently for asking. We do not sell personal information or share it for cross-context behavioural advertising.

Where data is stored

Dayclip stores data in the United States. If you use Dayclip from another country, your information is transferred to and processed in the United States.

Requests from public authorities

If a court, law-enforcement agency or other public authority asks us for personal data, including data we receive from Meta, Google or another platform, we:

review whether the request is lawful and properly issued before responding;
challenge or decline a request that we consider unlawful, overbroad or improperly issued;
disclose only the minimum information the request lawfully requires; and
keep a record of each request, our response, the legal basis and who was involved.

Unless the law forbids it, we tell the affected business owner before disclosing their data.

Security

Data is encrypted in transit. Social authorization tokens are held on the server, and access through Dayclip is limited to the owner's own business. Stations are locked devices that run only Dayclip, each shop's footage and clips are kept separate and opened through short-lived signed links, and access to raw footage by people who work on Dayclip is logged.

Children

Dayclip is for businesses and is not directed at children under 13. Footage can show young clients who visit a business: owners must get a parent's or guardian's permission before posting anyone under 18, and a parent can ask the business or us to remove a clip that shows their child.

Changes

We will post changes here and update the effective date.