ZERO-HOUR
Privacy Policy
The short version
- Zero-Hour is a Mac app. Your recordings, transcripts, reels and brand stay on your Mac. We never receive them, except finished reels you send to Buffer, which we host for a short time.
- Claude Code runs on your Mac under your own Anthropic account. We never see what you send to it or what it returns.
- What we do receive: your email and licence details for sign-in, an anonymous id for each Mac, your app version, your app settings (never API keys or other secrets), billing details through Stripe, invite emails you type in for the referral program, finished reels for Buffer, and what you send us if you join the beta waitlist, answer our survey or open a support ticket.
- Hosted reels are deleted once they are posted, or after 6 months at the latest.
- On the website, the Meta Pixel only runs if you accept marketing cookies. Without that consent it is never loaded.
- Our servers are in Frankfurt, Germany. We do not sell your data.
- You can access, correct, export or delete your data, and complain to a supervisory authority. See Your rights.
This summary is for convenience only. It does not replace the full policy below, which governs.
1. Who we are and how to reach us
Zero-Hour Content System is operated by LP Studio, Leon Panjtar s.p., a sole proprietor registered in the Republic of Slovenia under Registration No. 6493211000, VAT ID SI23530898, with its registered address at Kamnitnik 17, 4220 Škofja Loka, Slovenia (we, us, our).
Privacy questions and requests: [email protected].
Data Protection Officer: we have not appointed a DPO because we are not required to. The owner, Leon Panjtar, is responsible for data protection questions and requests. Reach him at the email above.
UK representative (Article 27 UK GDPR): not appointed. UK residents can contact us at the email above.
This policy covers the website at zerohoursystem.com (including the Get started page), the Zero-Hour app for Mac (the App), and the servers the App talks to. Use of the App is governed by the Master Software Subscription Agreement (MSSA). Use of the website is governed by the Terms of Service.
2. Scope and our roles
- Controller. We decide how and why your sign-in, licence, device, settings and billing data are used, and how the website works. For that data we are the controller.
- Processor. For finished reels we host for Buffer (and the people who appear in them) and for the invite emails you type into the App, we act on your behalf and on your instructions. You are the controller of that data. See section 6 and MSSA section 9.
- Neither. Everything that stays on your Mac (recordings, transcripts, reels, brand, work in progress) is not processed by us at all. Claude Code and Buffer run under your own accounts with Anthropic and Buffer, under your agreements with them.
3. What we do not collect
The App is built so that your content does not leave your Mac. We do not receive, store or have access to:
- your call recordings, audio or video, or anything other people say on your calls;
- transcripts, clip choices, captions or drafts;
- your brand profile, looks you create, or other brand content;
- anything you send to or receive from Claude Code, or your Anthropic account details;
- your Buffer API key or any other secret. These stay in your Mac's Keychain, and our settings sync rejects anything that looks like a key, token or password;
- your card number. Stripe handles payment details and we never see them in full.
The only exception is a finished reel and its posting text, when you publish it through Buffer (section 6).
4. What we collect
4.1 When you buy
- Name, email, billing address, country, and tax or VAT ID if you give one, collected by Stripe Checkout.
- The plan, price and offer you bought, Stripe customer and subscription ids, payment status, invoices and refunds. We do not receive full card details.
- That you ticked the box accepting the MSSA, and when.
4.2 Licence sign-in and refresh
- Your email address and the 6-digit sign-in codes we email you. Codes are single use and deleted once used.
- Your licence id, status, renewal date and referral code.
- For each Mac you use (up to 2): an anonymous Mac id created by the App, a hashed access token, the App version, when it first signed in and when it last refreshed, and which weeks it was active. This is how we enforce the 2-Mac limit and see which App versions are in use.
- Your IP address, used briefly for security and rate limiting (section 9).
4.3 Settings sync
Your App settings, so they match on both Macs: for example the looks you picked, which channels are enabled, and other preferences. Never passwords, API keys or other secrets.
4.4 Referral invites
If you invite someone from the App: their email address, your name as you want it shown, the optional note you write, the date, whether the invite was sent, and whether they later bought. If someone unsubscribes from invites, we keep their email address on a suppression list so we never email them again.
4.5 Reels you publish through Buffer
The finished reel file, a storage key, its size, and when it was uploaded and posted. The posting text goes from the App to Buffer.
4.6 Emails
The emails we send you (sign-in codes, receipts and billing notices, a short onboarding series after you buy, and important notices about the App or these policies), and whether each was sent. If you write to us, we keep the conversation.
4.7 Website
- Your cookie choice (cookie
zh_consent). - Only if you accept marketing cookies: Meta Pixel data (page views; viewing pricing, starting checkout, purchase, confirming your email on the Get started page, downloading the App, joining the beta waitlist and confirming your waitlist email; and the
_fbpand_fbccookies). For starting checkout, purchases and the waitlist, our server also sends Meta the event with your IP address, browser user agent and those cookie values (Meta Conversions API): for a purchase also your hashed email, hashed country and the order value; for the waitlist your hashed email, first name and waitlist id. To do that we store your IP address and user agent with the Stripe checkout session or your waitlist entry. - Standard request data (IP address, browser, pages requested) that our hosting provider handles to serve the site.
4.8 Admin and security records
A log of actions we take in our admin tools (for example extending or revoking a licence), with who did it, when, and which licence it affected.
4.9 Beta waitlist and survey
If you join the beta waitlist: your email address, first name, your answers to the three fit questions, whether you confirmed your email, a private page link (stored only as a hash), your referral code, who referred you, which share buttons you clicked, the addresses you invite (up to 5, so we do not invite anyone twice), the campaign tags in the link you arrived from, a hash of your IP address, and whether you prepaid or were picked as a tester. If you answer our discovery survey: your email address, your answers, the campaign tags and a hash of your IP address; you are added to our mailing list without the buyer onboarding emails.
4.10 Support tickets
If you open a ticket or suggest a feature in the App: your licence email, the subject and messages, our replies, the ticket status, and the App and macOS versions.
5. Why we use it and our legal bases
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Selling you a licence, invoicing, collecting renewals, refunds | 4.1 | Contract (Art. 6(1)(b)); legal obligation for tax and accounting records (Art. 6(1)(c)) |
| Signing you in, checking your licence, enforcing the 2-Mac limit | 4.2 | Contract (Art. 6(1)(b)) |
| Syncing your settings between your Macs | 4.3 | Contract (Art. 6(1)(b)) |
| Hosting reels for Buffer; sending invites you ask us to send | 4.4, 4.5 | We act as your processor (section 6). For tracking referral rewards and the suppression list: our legitimate interest in running the referral program fairly and not emailing people who said no (Art. 6(1)(f)) |
| Service emails: sign-in codes, receipts, billing and legal notices | 4.1, 4.2, 4.6 | Contract (Art. 6(1)(b)); legal obligation where we must notify you |
| Onboarding emails after you buy | 4.6 | Legitimate interest in helping customers get started (Art. 6(1)(f)). Every email has an unsubscribe link |
| Security, abuse prevention, rate limiting, admin audit log | 4.2, 4.7, 4.8 | Legitimate interest in keeping the service and your account safe (Art. 6(1)(f)) |
| Running the beta waitlist and survey: confirmation email, position, referrals, picking testers | 4.9 | Steps you asked for before a contract (Art. 6(1)(b)) and our legitimate interest in choosing beta testers and understanding customers (Art. 6(1)(f)) |
| Answering support tickets and feature suggestions | 4.10 | Contract (Art. 6(1)(b)) |
| Understanding App version use and fixing errors | 4.2 | Legitimate interest in running and improving the App (Art. 6(1)(f)) |
| Measuring which Meta ads lead to purchases (Meta Pixel and Conversions API) | 4.7 | Consent (Art. 6(1)(a) and the ePrivacy rules). Withdraw it any time with "Cookie settings" |
| Handling disputes and legal claims | Any of the above, as needed | Legitimate interest (Art. 6(1)(f)); legal obligation |
We do not use your data to train AI models, and we do not make decisions about you based solely on automated processing that have legal or similarly significant effects.
6. Where we act for you (processor)
This section matches MSSA section 9.
- Hosted reels. When you publish through Buffer, the App uploads the finished reel to our storage at DigitalOcean so Buffer can fetch it. We use it only for that. It is deleted once Buffer reports it posted, or after 6 months at the latest. People who appear in your reels are your responsibility: you need a lawful basis to publish them.
- Invite emails. When you invite someone, we use their email, your name and your note only to send one invite email and to track whether it leads to a purchase. We send it through our email provider (section 7). The invite has an unsubscribe link. We will not invite the same address again within 90 days, whoever sends it.
- For both, we process the data only on your instructions, keep it secure, use only the subprocessors listed in section 7, and help you respond to requests from the people concerned. If someone asks us about data in your reels or invites, we will pass the request to you where we can identify you.
7. Who we share data with
We do not sell personal data. We share it only with these providers, under contracts that limit their use of it:
| Provider | What they do | Data | Location |
|---|---|---|---|
| DigitalOcean, LLC | Hosting: servers (App Platform), database (Managed PostgreSQL), file storage and CDN (Spaces) for hosted reels and App downloads | All data in section 4 that reaches our servers | Frankfurt, Germany (EU). US company |
| Stripe Payments Europe, Ltd. and Stripe, Inc. | Checkout, subscriptions, invoices, tax calculation, tax ID collection, fraud prevention | 4.1, plus IP address and user agent stored with the checkout session | Ireland and USA |
| Resend (Plus Five Five, Inc.) | Sending our emails: sign-in codes, receipts and notices, onboarding emails, referral invites, waitlist confirmations, support replies | Recipient email, name, email content | USA |
| Meta Platforms Ireland Ltd. | Ad measurement, only with your consent (Meta Pixel and Conversions API). Meta acts as a joint controller for this, under Meta's terms | 4.7 | Ireland and USA |
| Our email hosting provider | Receiving and storing email you send to support@, privacy@ and [email protected], and our replies | Your email address, name and message | EU or USA, depending on the provider |
| Google LLC (Google Fonts) | Serving the typefaces our web pages use | IP address and browser request headers when fonts load | USA and worldwide |
We may also disclose data to professional advisers (accountant, lawyer) under confidentiality, to authorities where the law requires it, or to a buyer of our business, who would have to respect this policy.
Anthropic (Claude Code) and Buffer are not our providers. You use them under your own accounts. See section 15.
8. International transfers
Our servers, database and storage are in DigitalOcean's Frankfurt region in the EU. Some providers are US companies or may access data from the United States. Where data goes outside the EEA, the UK or Switzerland, we rely on:
- the EU-US Data Privacy Framework (and its UK Extension and Swiss-US framework) for providers certified under it; or
- the European Commission's Standard Contractual Clauses (2021/914), with the UK Addendum where needed, in the provider's data processing terms, together with encryption in transit and at rest.
You can ask us for a copy of the relevant safeguards.
9. How long we keep data
| Data | How long |
|---|---|
| Licence, Mac and settings data | While your licence exists. Deleted when you ask us to delete your account, apart from what the law makes us keep. Deleting a licence also deletes its Macs, settings and referral records. |
| Sign-in codes | Until used or replaced; they expire after a short time. |
| Billing records (invoices, payments, tax data) | 10 years after the end of the year they relate to, as Slovenian VAT and accounting law requires. Stripe keeps its own records under its policy. |
| Hosted reels | Deleted once posted, or after 6 months at the latest. A daily job removes them. |
| Referral invite records | 90 days, then deleted automatically, unless the friend bought a licence. Then we keep the record while the inviting licence exists, so the reward stays traceable. Always deleted with that licence or on request. |
| Suppression list (people who unsubscribed) | Kept, so we never email them again. |
| Onboarding email records | While you are a customer, or until you unsubscribe and ask us to delete them. |
| Rate-limit records with IP addresses | About 2 hours (some abuse counters up to 2 days). |
| Beta waitlist entries and invites | Until the beta ends or you ask us to remove you. If you become a customer, what we need moves to your licence. |
| Survey answers | Until you ask us to delete them. |
| Support tickets | 3 years after the ticket is closed, like support emails. |
| Admin audit log | 24 months, then deleted automatically. |
| Support emails | 3 years after the conversation ends. |
| Cookie choice | 180 days in your browser (zh_consent). |
| Backups | Database backups are kept by DigitalOcean for a limited period and then overwritten. Deleted data may stay in backups until then and is only restored for disaster recovery. |
10. Security
- Encryption in transit (TLS) between the App, your browser, our servers and our providers; encryption at rest for the database and file storage.
- Passwordless sign-in with single-use codes; access tokens are stored only as hashes on our side; rate limiting on sign-in.
- Hosted reels are stored privately with hard-to-guess names and deleted on schedule.
- Settings sync rejects anything that looks like a key, token or password.
- Admin access is limited to named people and every admin action is logged.
No system is perfectly secure. If a personal data breach affects you, we will tell you and the relevant authority as the law requires. We do not hold certifications such as SOC 2 or ISO 27001 and do not claim to.
11. Cookies and the website
Where we ask for consent, the website stores your cookie choice. The Meta Pixel only loads if you accept marketing cookies, and a Global Privacy Control signal from your browser counts as "no". The full list of cookies and similar technologies, and how to change your choice, is in the Cookie Policy. The App itself does not use cookies.
12. Your rights
Depending on where you live, you have some or all of these rights over data for which we are the controller:
- Access: get a copy of your personal data and information about how we use it.
- Rectification: correct inaccurate or incomplete data.
- Erasure: ask us to delete your data. We keep only what the law requires (section 9).
- Restriction: ask us to pause processing in certain cases.
- Portability: receive the data you gave us in a structured, machine-readable format. Your content is already on your Mac, in your hands.
- Objection: object to processing based on legitimate interests, and to onboarding or other promotional emails at any time (every such email has an unsubscribe link).
- Withdraw consent: for the Meta Pixel, use "Cookie settings" in the website footer, or email us. This does not affect what happened before.
- Complain to a supervisory authority (sections 13 and 17).
To use a right, email [email protected] from the address on your licence. We may ask you to confirm with a sign-in code. We reply within one month, which can be extended by two more months for complex requests (we will tell you). Requests are free unless they are clearly unfounded or excessive.
If you appear in someone else's reel, or received an invite, our customer is the controller of that data. Please contact them first. We will pass your request on where we can identify them, and help them respond. To stop invites, use the unsubscribe link in the invite email.
13. Region-specific disclosures
13.1 European Economic Area
The GDPR applies. Our lead supervisory authority is the Information Commissioner of the Republic of Slovenia, Dunajska cesta 22, 1000 Ljubljana, Slovenia, www.ip-rs.si. You may also complain to the authority where you live or work.
13.2 United Kingdom
The UK GDPR and Data Protection Act 2018 apply. You can complain to the Information Commissioner's Office, ico.org.uk.
13.3 Switzerland
The revised Federal Act on Data Protection (nFADP) applies. You may contact the Federal Data Protection and Information Commissioner (FDPIC).
13.4 United States
In the last 12 months we collected: identifiers (email, name, IP address, Mac id); customer records (billing name and address); commercial information (licence and purchase history); internet activity (website and App version data); and approximate location from IP. Sources, purposes and retention are in sections 4, 5 and 9. We do not sell personal information. With your consent on the website, we share purchase events with Meta for ad measurement; Global Privacy Control and "Decline" turn this off. Residents of California and other states with privacy laws can ask to know, delete or correct their data, and opt out, using the contact in section 12. To appeal a refusal, reply to our decision email.
13.5 Other countries
Wherever you are, you have the rights in section 12 to the extent your local law gives them, and we will answer requests in good faith.
14. Children
Zero-Hour is a business product and is not directed at children. You must be at least 18 (or the age of majority where you live) to buy a licence. We do not knowingly collect personal data from anyone under 16. If you think a child has given us personal data, contact us and we will delete it.
15. Third-party services you use
Claude Code runs on your Mac under your own Anthropic account, and Buffer under your own Buffer account. What they receive from the App (prompts and transcripts for Claude Code; reels and captions for Buffer and the social networks you post to) is handled under your agreements with them and their privacy policies. We are not responsible for their practices. Stripe and Meta also have their own privacy policies for the data they handle as controllers.
16. Changes to this policy
We may update this policy as the App, the law or our providers change. The version date at the top shows when it last changed. For material changes we will tell you by email or in the App at least 14 days before they take effect, or longer where the law requires. Previous versions are available on request.
17. Contact and complaints
Email: [email protected]
Post: LP Studio, Leon Panjtar s.p., Kamnitnik 17, 4220 Škofja Loka, Slovenia
If you are unhappy with how we handled your data, please tell us first and we will try to fix it. You also have the right to complain to a supervisory authority. In the EU our lead authority is the Information Commissioner of the Republic of Slovenia (www.ip-rs.si). Others are listed in section 13.