Privacy at Lunch Pail Labs
Pail & Co Ltd runs Lunch Pail Labs. This notice covers the studio website, writing, demos, accounts, Discord support and signup. Pipa has its own product policies. Updated November 12, 2026.
Information used to run your product
- Account: email and sign-in identity through Supabase Auth, plus a server-only record linking your account to your support setup.
- Support setup: your website, selected public sources, uploaded text, edited company guide and bot instructions. Selected material is used to generate support answers.
- Discord: installation, server, channel and role identifiers and authorization records needed to connect and manage the bot. Questions, replies and job history are processed by the support backend and its configured AI providers.
- Support activity: thread identifiers, questions, replies and job records needed to run and troubleshoot the bot, plus your plan, allowance and used-thread count.
- Signup and purchase: submitted email, website, request and email-delivery records. Stripe hosts checkout and subscription management and holds payment records. We store the account’s billing references and subscription state to apply its paid plan; card details do not enter our application. Do not send card details to us in support messages.
Only upload material you are authorized to use. Do not put passwords, API keys or other secrets into source files, bot instructions or support questions.
Our support widget processes the contact details and messages you submit, page URLs and browser/device information. Page URLs can include private demo invitation links. We do not automatically attach your bot’s guide or conversation transcript.
Cookies and local storage
The host-only labs-consent cookie remembers your choices for 180 days. Visits do not extend that choice; after expiry we ask again. reopens your Accept all or Reject optional choice for analytics and third-party media/support together. A choice that cannot be saved does not enable optional tracking.
Essential cookies keep you signed in and protect access to your saved setup and Discord connection. The saved-setup cookie renews when you return, up to a browser limit of 400 days. That limit does not determine when saved content is deleted.
Browser local storage keeps setup edits, previews and test results so you can resume work. Clearing it can remove unsaved edits. Signing out clears this browser’s setup cache and setup/Discord access cookies, but does not delete server records.
Measurement and operational records
Before you choose, and after Reject optional, PostHog receives minimal selected events on While You Sleep pages. A random anonymous identifier stays in page memory only and changes between documents. These events contain coarse page and job classifications, not campaign details, referrers, account identifiers, signup request IDs or checkout IDs. Reject optional does not stop this measurement: use Stop basic stats below to object. This choice is preserved when you accept or reject optional cookies.
Only after Accept all do we store a new analytics UUID in labs-analytics-id local storage, bounded by the consent expiry. Selected events may then include sanitized current-page campaign tags and referring-site domain. This identity is not linked to earlier anonymous events. Consented signup and verified-payment events may include operational correlation references; the signup service validates permission as it stood when browser enrichment was collected. Later browser withdrawal does not rewrite a stored transaction or retroactively withdraw that snapshot.
All event modes exclude submitted emails and websites, questions, answers, uploaded content, secrets and full page URLs. We do not enable person profiles, replay or automatic interaction capture. Our direct sender omits browser credentials and referrer headers and requests no IP or geolocation processing. Providers still receive network connection information: these flags do not prove that ingress logs or IP addresses are never processed.
Turning off a purpose immediately blocks new optional collection and removes this site’s named tracking storage, without clearing setup edits or sign-in data. Active media/support surfaces are stopped. Reload finishes removing already-loaded third-party code; save unsaved work first. We cannot remove provider-origin or HttpOnly cookies from browser JavaScript. Use your browser’s storage controls or contact the provider for those records.
Media and support providers
YouTube videos and Help Scout Beacon load only with optional permission. Without it, you can follow the ordinary YouTube link or email support. Once enabled, these providers receive connection information and may set their own cookies or storage. Beacon starts without account identity; we do not send your account, guide or conversation context automatically. Fonts are hosted on this website, not requested from Google Fonts.
Our services also process limited operational records, such as failed actions and response status codes. The support backend records model failures and reported costs where available.
Where records live
Supabase stores your shared sign-in identity and the link to your support setup. Cloudflare hosts the website and support/signup services. The support backend stores saved sources, configuration and job history. AgentMail delivers signup notifications to our team. Stripe stores payment records. PostHog stores the analytics events described above. Our AI providers process the material needed to produce answers. Each provider may keep records for a different length of time.
Anonymous labeling alone does not establish a statistical-analytics exemption. Provider ingress/IP handling, aggregate-use restrictions, retention, processor terms and international-transfer safeguards remain subject to release-owner review. We do not claim this interface certifies a legal exemption or regulatory compliance.
Retention and deletion requests
We keep saved support work until a verified deletion request, rather than deleting it because it is old. Signup submission storage has a 30-day cleanup schedule. That schedule does not remove copies in email, Stripe, other provider records or analytics.
To access, correct or request deletion of your data, email [email protected]. We verify ownership and confirm which records to handle. Requests are handled manually. We explain what was removed and what must remain for security, legal or billing reasons. We may keep restricted ownership records to prevent an old browser from regaining access to deleted work.
Deleting Discord support data does not automatically delete your shared Pipa sign-in or other Pipa data. We confirm changes affecting both products separately. Disconnecting the bot and signing out do not request deletion.