Who is responsible
Concept 27 SIA, registration number 40203495052, VAT ID LV40203495052, Nicgales iela 38-63, Riga, Latvia, LV-1035, provides Butterspace. Contact us at help@butter.space. This policy covers our website, app, browser demo, public shares, billing and support, including supported Butterspace domains and Butterspace Recipes in ChatGPT.
We decide how account, billing, support, security and our own website data are used. A business customer normally controls the personal data its members put into its workspace; we process that data on its instructions under our Data processing addendum. Personal users can contact us directly about their own data.
Information we process
Account and team information: your name, email, sign-in identifiers, account ID, workspace memberships, roles and sign-in activity. This comes from you, your chosen sign-in provider and the people managing your workspace.
Workspace information: products, recipes, menus, instructions, costs, supplier details, purchase orders, photos and import content entered or uploaded by workspace members. Avoid including sensitive personal information unless necessary and you are authorized to provide it.
Billing information: plan, currency, subscription and payment status, billing email, company or personal name, address, tax ID and invoices. Stripe collects payment credentials. Butterspace does not receive your complete card number.
Support and communications: your contact details and messages, delivery status for service emails, and a waitlist email if you submit one. We use a waitlist signup to respond to the request you made, not as permission for unrelated advertising.
Technical information: hosting request logs, IP addresses, browser and device information, authentication and security events, and records of days a signed-in account used its workspace. These support service operation, troubleshooting and abuse prevention.
Browser demo information: the demo workspace, images, orders and preferences are stored on your device. Demo AI Import additionally uses a short-lived request cookie and hashed session/IP identifiers on our server to control abuse. Choosing an AI import sends the selected file for processing as explained below.
Why we process it
We use account and workspace data to provide the service you request, authenticate you, save changes, manage teams, publish links you create and administer subscriptions. For a personal customer this is needed to perform our contract. When we act for a business workspace, we follow that customer's instructions; it is responsible for its own legal basis.
We process billing and tax records to perform subscriptions and meet accounting and tax obligations. We process necessary security, service-performance and support records for our legitimate interests in operating and protecting Butterspace, balanced against your rights. You can object to processing based on legitimate interests.
Optional analytics, advertising and marketing messages use consent where required. Refusing optional tracking does not prevent core use of Butterspace. We do not sell personal information, and we do not make decisions with legal or similarly significant effects about you solely through automated profiling.
Optional AI Import
When you choose AI Import, Butterspace sends your selected text, document or image and extraction instructions to Google's Gemini API. We return the extracted products, recipes or menu items for your review. This applies to signed-in workspaces and demo imports. Only submit files you may lawfully share with us and Google.
We do not use your uploads to train our own models. Google's handling is governed by its Gemini API terms and applicable data processing terms. For paid API services, those terms state that prompts and responses are not used to improve Google's products; limited safety and abuse-prevention logging can still occur, including processing outside the EEA. Avoid sensitive or unnecessary personal information in import files.
AI Import is optional. You can enter and edit workspace content without sending a file to Google. Check extraction results before relying on them.
Butterspace Recipes and ChatGPT
Butterspace Recipes is optional. Without an account connection, ChatGPT sends recipe fields and the current chat recipe library to Butterspace's hosted tools to perform the requested operation. Guest tools do not save that library to the Butterspace database or create an account. Chat-only use is not offline; the technical and security processing described in this policy still applies.
When you connect an account, we record your account identifier, chosen workspace and connection permission. The connected ChatGPT app receives a stable account identifier. We check current membership and role on account tool requests. We process these requests to provide the features you ask for, under the service and business-workspace arrangements described above.
Connected tools send workspace recipe information to ChatGPT, operated by OpenAI. This includes workspace and recipe names, yields, ingredient names and quantities, preparation notes, methods, categories and record identifiers. Listing recipes sends catalog names, categories, yields and record identifiers, without every recipe's ingredients and method. Opening or scaling a recipe sends that selected recipe's details. A whole-workspace export sends the complete active recipe library only when explicitly requested. Tools do not return saved photos, product prices or billing details. Only connect content you are authorized to share with ChatGPT.
When you review chat recipes for copying, Butterspace receives those recipes and checks the selected workspace for matches and conflicts. We save only the copies you confirm. Recipes and linked products then become ordinary content in that workspace; the original chat remains separate.
Original photos or files attached in ChatGPT are not uploaded to Butterspace photo storage by this connection. We receive the recipe fields ChatGPT sends to the tools. The web app's Gemini AI Import is a separate feature.
OpenAI handles information in ChatGPT under its applicable terms, privacy policy and your account settings. These can differ from Butterspace's arrangements, including where processing takes place. See OpenAI privacy and, for the EEA, UK and Switzerland, OpenAI's regional privacy policy. Disconnecting Butterspace blocks further account access through the connection; it does not remove copies already in ChatGPT. Use the relevant service's controls to manage those copies.
Plugin records and retention
Free plugin recipes are ordinary workspace content, not a time-limited trial. Free plugin access continues after a paid subscription or trial ends. A workspace without active paid, trial or complimentary access becomes eligible for deletion after six calendar months without connected ChatGPT use. Successful authenticated workspace tool use starts a new six-month period. Background token refreshes and monitoring do not count as use. We keep one last-use timestamp per workspace, without recipe text or photos, to apply this rule. A delivered warning gives members at least 30 days before automatic deletion. Existing explicit account and workspace deletion rules still apply, including shared-workspace consequences. No automatic deletion is activated by connecting the plugin.
We keep restricted connection records to check and revoke access. Disconnecting revokes permission rather than immediately erasing every connection record. Records linked to an account or workspace are removed when that account or workspace is permanently deleted; session-bound records can also be removed when their associated sign-in session is deleted.
For safe retries, operational records contain request identifiers, content hashes and workspace references, not recipe text or photos. They are capped at 1,000 per user. Records older than seven days are removed during a later successful recipe write, not necessarily on day seven if no write occurs.
Copy receipts separately record account/workspace and source library/recipe identifiers, a content hash, and the destination recipe identifier. They prevent later retries from creating duplicate copies, including after an edit or archive. They contain no recipe text or photos and are removed when the destination recipe, workspace or account is permanently deleted. Archiving a recipe does not delete its receipt. These receipts do not promise permanent recipe storage.
Service providers and other recipients
Supabase provides authentication, the application database and photo storage. Vercel hosts the website and app and handles delivery and request logs. Google provides sign-in, the Gemini API for selected imports, and Google Workspace for support email. Resend delivers email sign-in links and service emails, including expiry and deletion notices, and reports delivery failures and spam complaints. It processes the recipient address, email content and delivery metadata. These notices do not use open or click tracking. Stripe provides payment processing, subscriptions, tax calculation, invoices and the customer billing portal when used.
If you allow Usage analytics, we use PostHog EU for predefined website, demo and product actions, and Google Analytics 4 for visits and selected milestones. Events use a random browser identifier, simplified page paths, predefined labels and counts. Verified account creation and first paid subscriptions can also be reported by our server. Payment events contain a pseudonymous transaction reference, plan, currency and pre-tax value. We do not send names, emails, recipe text, uploaded files, search text, billing addresses, tax IDs or card details in these events. Session replay and automatic content capture are off.
If you also allow Advertising measurement, eligible Google Analytics events and advertising click identifiers can be used in our linked Google Ads account to measure campaigns. This does not enable personalized advertising, remarketing or enhanced conversions. Providers can process connection information when they receive a request. See PostHog privacy and Google privacy.
Providers process information for their service roles under applicable contracts, and some also act independently for their own legal, security or payment obligations. See Supabase privacy, Vercel privacy, Google privacy, Resend privacy and Stripe privacy. We may disclose information where required by law or necessary to protect rights or security. We do not disclose workspace content for unrelated advertising.
International processing and security
Our primary application database is in the EU, in Stockholm. Hosting delivery, support and service-provider operations can involve countries outside the EEA. A provider's EU region does not by itself mean that every processing operation stays in the EU.
Where GDPR requires protection for an international transfer, we rely on the applicable adequacy decision, standard contractual clauses or another lawful mechanism under our provider agreements. Contact us for information about the relevant safeguards.
We use authenticated access, workspace membership and role checks, encrypted network connections and restricted administrative access. No online system is completely secure. Tell us promptly if you suspect unauthorized access to your account.
Retention and deletion
Account and workspace information is kept while the service is in use. Active paid, trial or complimentary access protects a workspace. Otherwise, restricted workspace content remains available for renewal or export and becomes eligible for deletion after 6 months of dormancy, measured from the later of access ending or successful connected ChatGPT use. Such use starts a new six-calendar-month period. We also delete the account only when it has no other workspace membership. We notify affected members at least 30 days before automatic permanent deletion. An explicit account deletion does not wait for that period.
You can delete your account in Settings > Account > Delete account. After review and confirmation, the app removes your sign-in account and each workspace where you are its only owner, including its uploaded photos. This removes that workspace for all its members. Workspaces with another owner remain intact. Members who are not owners only leave the workspace. The Terms explain subscription and shared-workspace consequences.
Invoices, tax and transaction records are retained for the period required by applicable law. Security and support records are retained as needed to resolve the issue, investigate abuse, comply with law or handle a dispute, rather than as a permanent record of workspace content. We assess whether identifying information is still necessary for those purposes.
Routine service-email content is kept for 30 days and basic delivery and error records for 90 days. We keep separate, restricted copies of subscription agreements and important subscription confirmations and cancellations while the paid relationship continues and for 3 years after it ends. Other important operational notices, such as reset and deletion confirmations, are kept for 3 years from creation. These records contain the notice, recipient and relevant timing and delivery details, not copies of recipes or photos. Records needed for an ongoing dispute or a separate legal requirement may be held beyond their normal expiry, with restricted access and review when that need ends. Invoice and accounting retention is separate.
When workspace reset is available, a separate private recovery copy of workspace content and uploaded photos is kept for up to 7 days. Only authorized support can use it after verifying the workspace owner's authority; recovery cannot overwrite a nonempty workspace. Explicit account deletion does not wait for this recovery period. See the Terms for recovery requests.
Provider backups, where available, and provider security logs can outlast deletion from active systems until their applicable retention or rotation completes. Access to retained copies is restricted. If a backup is restored, deletion instructions must be reapplied. Browser-local demo data and preferences remain on your device until you clear or replace them.
Browser analytics identifiers have the cookie periods described in the Cookie policy. Server choice records expire after 180 days, checkout measurement context after 30 days, queued conversion payloads after 72 hours and opaque delivery bookkeeping after 90 days. Expired records are removed by scheduled cleanup, normally at the next daily run. These are independent of accounting records and workspace retention. Google's configured event retention is two months and user retention is fourteen months, with activity-based renewal disabled; standard aggregated reports follow Google's separate rules. PostHog's event query window follows the account plan: one year on Free or seven years on a paid plan. A query window is not a guarantee of physical deletion. Contact help@butter.space about access or erasure requests; see PostHog retention.
Your choices and privacy rights
You may request access, correction, erasure or a copy of your personal data. Depending on the legal basis and your location, you may also have rights to portability, restriction, objection and withdrawal of consent. Withdrawing consent does not make earlier lawful processing unlawful. Some data must be retained for legal reasons.
Account deletion is available in the app. Workspace exports and other privacy requests are handled at help@butter.space, without requiring another subscription purchase. We may verify your identity and workspace authority. We normally respond within one month; where a lawful extension is needed, we will explain it within that month. A request concerning a business-controlled workspace may need to be handled with its owner, without removing your individual rights.
You may complain to your local data protection authority or Latvia's Data State Inspectorate. Contacting us first is helpful, but is not a requirement for making a complaint.
Cookies, age and policy updates
Our Cookie and device storage policy explains essential authentication storage, demo storage, preferences and optional analytics. Usage analytics and advertising measurement have separate choices. Rejecting optional tracking does not prevent core use. Open the Cookies page from the website or legal-page footer, Account settings in the app, or Workspace settings in the demo to change your decision. Select Manage cookie preferences on that page to open the controls. Agreeing to the Terms is not consent to optional tracking.
Butterspace is intended for people aged 18 or older. If you believe a child has provided personal information, contact help@butter.space so we can address it. We may update this policy when the service or processing changes. We will publish the current version and date and give additional notice where required.