Privacy
Last updated 29 October 2026
Cyprian is operated by Cubeshell LLC. This policy explains the information Cyprian handles when you use our website, web workspace, mobile app and the services behind them, why we need it, who receives it, and the choices you have.
On this page
Who we are and what this policy covers
Cubeshell LLC is responsible for the personal information described in this policy. “Cyprian”, “we” and “our” refer to Cubeshell LLC and the Cyprian service.
This policy covers cyprian.ai, the Cyprian web workspace at app.cyprian.ai, the Cyprian mobile app, and the systems that receive customer conversations and schedule and publish content for you. A connected social network handles information under its own terms and privacy policy once you ask us to send content to it.
Information we handle
We handle the following categories when they are relevant to your use.
- Account and workspace information. Your email address, authentication records, workspace name, membership role, invitations, time zone, settings and preferences.
- Billing information. Your trial and subscription status, the plan and price an owner authorized and when, billing country, invoices, payment status and the Stripe customer and subscription references for your business. Stripe collects payment card details directly; Cyprian does not receive or store your card number.
- Content you provide. Images, videos, captions, titles, descriptions, instructions to the assistant, conversation history, drafts, proposals and the settings you choose for a post. We also derive technical media information such as dimensions, duration, format and checksums, and may create thumbnails or publishing renditions.
- Connected-platform information. The platform, account, Page, channel or profile identifiers and names you choose; the permissions you grant; connection status; encrypted authorization credentials held by Cyprian; and information the platform returns for the feature you requested. We do not receive your social-network password.
- Publishing and safety records. What you scheduled and approved, target settings, attempt times and outcomes, platform post identifiers, error categories, connection attempts, audit events and limited operational measurements used to prevent duplicates, diagnose failures and protect workspaces.
- Technical information. IP address, request time, browser or app and device details, operating system, referral page, cookie choices and server or security logs generated when your device communicates with Cyprian. Our product telemetry is designed not to contain post text, media or social-network credentials.
- Communications. Messages and attachments you send to us for support, privacy requests, security reports or feedback.
- Optional website analytics. If you accept analytics on cyprian.ai, Google Analytics measures page views, visits, approximate location, browser and device information, scrolls and outbound link clicks. It uses a first-party
_gaidentifier to distinguish visits. Rejecting analytics sends no information to Google, and the choice does not affect the product.
We receive this information from you, your device, members of your workspace, the platforms you connect and the providers that operate parts of the service. We do not buy personal information about you. We do not sell personal information or share it for cross-context behavioural advertising.
How we use it
We use these categories only as needed to:
- create and secure your account and workspaces;
- store, prepare, schedule, publish and report on content you approve;
- connect the exact platform resource you select;
- provide assistant suggestions for you to review;
- prevent abuse, investigate failures and avoid duplicate publishing;
- answer support, privacy and security requests;
- improve reliability using limited operational measurements; and
- comply with law and enforce our terms.
Where applicable, our legal bases are performing our agreement with you, your consent, our legitimate interests in operating and securing the service, and compliance with legal obligations. Website analytics and the authorization you grant to a connected platform can be withdrawn as described below.
Connected platforms
You choose each platform connection and see its permission request before authorizing it. Cyprian uses that authorization only for the connected feature you select. We send a platform only the content and settings you approve for that destination. Content already published is then controlled by that platform and may remain there after it is removed from Cyprian.
The permissions named below are the ones Cyprian’s own application code requests, and they are the minimum each feature needs. Cyprian holds every platform authorization directly, under its own developer application — no third party holds or brokers a credential on our behalf. In every case the authorization screen you approve is the authoritative list of what is being requested, and Cyprian cannot obtain a permission you did not approve there.
X. Connecting X requests users.read to identify the account you selected, tweet.write to publish content only after you approve it, tweet.read to read back the post we just published so we can confirm the platform actually accepted it, and offline.access so a post you scheduled for a later date does not fail on an expired authorization. This connection does not ask to read your timeline, your messages or anyone else’s posts.
Bluesky. Connecting Bluesky requests atproto, the identity permission every AT Protocol application must hold, and transition:generic, which is the permission AT Protocol currently offers for writing to your repository — what creating a post and uploading its media requires. It is broader than Cyprian uses, because AT Protocol has not yet published a narrower one; we will move to a narrower permission when it exists. We deliberately do not request the chat permission. This list is published as our client identity at cyprian.ai/client-metadata.json, which is the document your server reads before showing you the authorization screen.
LinkedIn. If you connect LinkedIn, the initial connection requests openid and profile to identify the LinkedIn member you selected, and w_member_social so Cyprian can publish content only after you approve it. We store the member and connection identifiers, authorization status and publishing receipts needed to provide that feature. This connection does not ask to read your feed, comments, inbox, contacts or messages.
YouTube. Cyprian uses YouTube API Services, and holds this authorization directly under its own Google OAuth client — no third party holds or brokers it, and the Google authorization screen names Cyprian. An authorized member of your workspace connects a channel from the Cyprian web workspace. Connecting a channel for publishing requests two permissions: https://www.googleapis.com/auth/youtube.upload to upload the video and details a member approves, and https://www.googleapis.com/auth/youtube.readonly to name the channel you are publishing to and to read back the upload, processing and visibility status of the video we just uploaded, so we can tell you the truth about whether it is actually viewable. With each upload Cyprian sends YouTube only what a member approved for that video: the video file, title, description, tags, visibility (public, unlisted or private), whether the video is made for kids, and whether it contains altered or synthetic content, with YouTube’s Howto & Style category. Cyprian never answers the made-for-kids or altered-content questions for you: a person must choose the audience, and the altered-content setting stays off until a person turns it on. Publishing does not ask to manage your account, read comments, or see your audience statistics. We do not use Google user data for advertising, sell it, use it to train AI models, or transfer it for unrelated purposes. Use of YouTube features is subject to the YouTube Terms of Service. Google handles information under the Google Privacy Policy. Cyprian’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. While the connection is active, Cyprian checks its authorization and selected channel at least every 24 hours and refreshes the channel label and avatar when they change. Cyprian does not request or retain YouTube channel statistics.
YouTube comments are an optional, separate upgrade. Cyprian offers it to customers only after Google approves the permission it uses. Comments stay off unless an owner or admin turns them on for one exact connected channel. Turning them on is a separate Google authorization that adds one permission, https://www.googleapis.com/auth/youtube.force-ssl, which YouTube requires to post a comment reply. Google’s authorization screen describes that permission broadly; Cyprian uses it only to read the comment threads on that channel’s videos, including videos that were not published through Cyprian, and to post a reply that a workspace member wrote, reviewed and sent. It does not post new top-level comments, hide, moderate or delete comments, change or delete your videos, or reply on its own. Declining the upgrade, or granting it for a different channel, leaves publishing working and comments off.
When comments are on, Cyprian stores inside your workspace: the text of each comment and reply; the commenter’s YouTube channel identifier and public display name; the video, comment-thread and comment identifiers, with a link to the video; when the comment was posted; the reply count and whether YouTube currently allows a reply; and each reply your team sends, with the identifier YouTube returns for it. We do not ask YouTube for a commenter’s email address or other contact details. Cyprian checks the channel for new comments about every 15 minutes, and refreshes each stored comment from YouTube or deletes it within 30 days of when it was last retrieved. This material is visible only to the members of your workspace. YouTube comment text and commenter details are never sent to an AI provider, never used to train any model, never used for advertising and never sold. They are left out of the account data export, because an exported copy could not be refreshed or deleted as YouTube requires; the replies your team wrote remain your workspace’s own records. Disconnecting the channel, revoking Cyprian in Google’s settings or deleting your account stops comment reads and deletes stored comments under the YouTube deletion terms below.
TikTok Accounts API for Business. Customer use requires TikTok approval and Cyprian enablement. When approved and enabled, it will use TikTok’s account-holder authorization for the exact account your workspace selects. Cyprian will use the permissions actually granted for that account to publish or schedule the video or photos a member approves, read and respond to comments on its owned posts, apply a member’s approved moderation action, and show the account’s profile and post performance measurements. Publishing, comment reads, comment actions and insights have separate controls; connecting an account does not enable every feature. This integration does not collect TikTok private messages, download TikTok videos or images, or build creator discovery or ranking lists.
For the Accounts integration, Cyprian stores the selected account and application identifiers, granted permissions and connection status; encrypted access and refresh tokens; approved post settings, media references, publishing attempts and the post identifiers and outcomes TikTok returns; comment and reply text, public commenter details and identifiers, parent and post identifiers, moderation state and action receipts; and permitted profile and post measurements with their observation times. These records belong to the business’s workspace. Tokens stay on Cyprian’s servers and are not returned to your browser or phone. A member reviews and commits each publication, reply or moderation action. Cyprian does not treat an uncertain provider response as confirmed delivery or automatically repeat it.
Disconnecting an Accounts connection stops new use in Cyprian and queues its stored credentials and provider-derived records for erasure. We show remote revocation as unconfirmed unless it has been verified; you can also remove Cyprian’s authorization in TikTok’s own settings. Minimal security and outcome records may remain under the retention terms below. Disconnecting does not delete posts already on TikTok or the original media your team uploaded separately to Cyprian. Those originals follow your workspace’s existing retention and deletion controls; backup copies expire through the recovery cycle described below.
TikTok Login Kit and Content Posting API. This separate integration uses user.info.basic to identify the selected account and video.publish to publish approved video or photos and check the publishing settings and outcome. It does not request comments, private messages, follower lists or analytics. These permissions do not grant Accounts API for Business access, and customer use requires this integration’s own review and release requirements to pass. Its credentials are encrypted on Cyprian’s servers; a provider revocation is reported as confirmed only after TikTok accepts it. Published posts remain on TikTok.
Google Business Profile. When this connection becomes available, connecting a Business Profile will request business.manage, the permission Google provides for these features. Cyprian uses it for the business you select: reading profile details, supported capabilities, reviews and replies, posts, photo records, booking links and native performance counts; preparing changes for human review; and sending only supported changes an authorized person approves. A booking-link update changes only the existing link reviewed for that command. We keep the selected account and location identifiers, authorization and connection state, and the limited feature records needed for those actions. We do not use Google user data for advertising or transfer it for unrelated purposes. Our use of it follows the Google API Services User Data Policy, including its Limited Use requirements.
Instagram and Facebook Pages. The shared Meta connection requests pages_show_list to show the Pages you manage so you can choose the exact destination, pages_read_engagement for the Page relationship and identity fields Meta requires on that publishing path, and to read the Graph fields named id, message and permalink_url for a Page post Cyprian published so you can compare Cyprian’s saved publication record with the post’s current content on Facebook. pages_manage_posts publishes the Page post you approve and, after a separate confirmation, edits its message or deletes an eligible text or single-photo Page post originally published through Cyprian. Editing does not replace the image. Cyprian retains the original publication record and later action history after the Facebook post is deleted. For an Instagram professional account linked to an eligible Page, instagram_basic identifies the exact Business or Creator profile and instagram_content_publish is used for the human-approved image publication demonstrated in this submission. That published-post readback does not ingest an arbitrary Page feed, visitor posts, audience metrics, analytics, insights or advertising statistics.
Messages and comments on Facebook and Instagram. Cyprian is the AI front desk for small businesses, so the same Meta connection can additionally be authorized to bring the conversations and comments your Page and Instagram account receive into one place your team works from. That authorization adds six permissions to the five above: pages_messaging for Messenger conversations a customer started with your Page, instagram_manage_messages for Instagram Direct conversations, pages_read_user_content to read and display the exact customer comment on your Page post, pages_manage_engagement to reply publicly to, hide and unhide that comment, instagram_manage_comments for comments on your Instagram posts, and pages_manage_metadata to subscribe the exact selected Page to Meta’s feed and messages webhook fields. Instagram’s separate app-level subscription receives its comments, mentions and messages events. You choose whether to grant them, and the Meta authorization screen you approve is the authoritative list of what is being requested.
When those permissions are granted, Cyprian receives and stores, inside your workspace: the text of a message or comment; the platform identifier and the public display name or username of the person who sent it; the type of any attachment and the platform link Meta returns for it; the post or media a comment was left on and its public permalink; whether a comment is visible, hidden or deleted at the platform; message read receipts; and the platform’s own message, comment and event identifiers and timestamps. We do not ask Meta for a customer’s email address, phone number or profile details beyond what accompanies the message or comment itself. A message you send from your Page or account is not stored again as if a customer had sent it, and a comment the platform reports as removed is marked as removed rather than erased, so you can still see what happened. This material is visible only to the members of your workspace, is not used for advertising, and is not used to train a general-purpose model.
A person decides every reply, unless an owner or admin has approved automated replies for one specific connected messaging channel. Cyprian’s assistant may read this material to summarise it and sort it. For enabled Facebook, Instagram and WhatsApp connections, an authorized workspace member types a message reply, reviews the exact words and presses Send, except where the automated-reply rule described next applies. Public comment replies are written by a member and sent with Publish reply; available moderation actions require the member to choose that action for that comment. AI-drafted Inbox reply controls are deferred. Meta has approved the Cyprian app through App Review.
Automated inquiry replies are off by default. An owner or admin can approve a rule for one connected messaging channel: a Facebook Page, an Instagram professional account or a WhatsApp Business number. Under that rule Cyprian answers private customer inquiries on that channel with replies composed only from the business profile the owner entered and approved, sends each reply automatically under the rule’s authority, marks it as automated and tells the customer how to reach a person, records it as sent automatically, stops for a conversation the moment a person takes it over or replies from the platform’s own tools, and can be turned off for that channel at any time. Cyprian will not moderate a comment or change your Page by itself. Cyprian enforces the required permissions and provider rules.
WhatsApp Business Platform. Connecting WhatsApp requests exactly two permissions. whatsapp_business_management lets an authorized workspace member onboard and select the exact WhatsApp Business Account (WABA) and Business Platform phone number, verify their connection and registration state, and read that number’s template inventory and provider approval status. Cyprian does not use it to create marketing campaigns. whatsapp_business_messaging lets Cyprian receive messages a customer sends to that number and lets a workspace member press Send on a reply inside Meta’s current customer-service window. Where an owner or admin has approved an automated-reply rule for this exact number, it also lets Cyprian answer a customer-initiated message inside that same window with a reply composed only from the approved business profile, marked as automated and pointing the customer to a person. Where a supported conversation requires a provider-approved template, Cyprian sends only the selected approved template after a member presses Send and the current consent and template rules pass; automated replies never use templates. This does not claim a separate out-of-window template-send flow, bulk messaging or marketing campaigns.
For WhatsApp, Cyprian stores the exact WABA, phone and destination identifiers; participant and message identifiers; message content and the attachment metadata or links Meta supplies; template identifier, name, language, category, status, components and version; consent and service-window evidence; and provider message identifiers, event times and sent, delivered, read or failed receipts. Authorization credentials are encrypted and kept separate from content returned to the app. Consent, service-window and approved-template status are checked again before a provider send. A workspace member commits every send unless an owner or admin has approved an automated-reply rule for this exact number; under that rule Cyprian sends replies automatically, only while that window is open and only from the approved business profile, and every automated reply is disclosed as automated. Nothing sends a template, an out-of-window message, a bulk message or a marketing message on its own. We retain these records while needed to operate and secure the workspace and meet lawful audit obligations. Disconnecting fences future use, and revoking Cyprian in Meta ends provider access. Neither action erases messages already delivered to recipients. A verified account or data-deletion request removes or de-identifies WhatsApp data from active systems unless lawful retention is required; encrypted backup copies expire through the normal recovery cycle.
Threads. Connecting a Threads profile requests threads_basic to identify and show the exact profile you selected, and threads_content_publish to publish only the text, image, video or carousel you approve. Cyprian does not request or use Threads permissions for replies, comments, inbox messages or analytics. Threads credentials are kept separate from the Facebook and Instagram app family.
Any other platform you connect receives only the account-selection information and the approved publishing payload needed for the feature you use. Their own policies govern information once received by them.
Assistant and AI processing
YouTube comments are excluded from AI. YouTube comment text, commenter names and identifiers are never included in an assistant request, an automated reply or any model training. Replies to YouTube comments are written and sent by a person.
Google Business Profile AI is deferred for the initial launch. Google review text, ratings, reviewer details and facts imported from Google into Business Context are excluded from model prompts, AI reply drafts, training and embeddings. Approving an imported fact does not make it independent input. Facts your team enters independently are kept separately and can support the assistant and approved inquiry rules described below. Human-written Google review replies remain available; an authorized person approves the exact reply before it is sent.
When you ask the assistant to prepare a plan, Cyprian may send your instruction, selected settings and limited relevant context to OpenAI’s API, or Google’s Gemini API when that provider or its optional fallback is enabled. We do not include social-network passwords or authorization credentials. The response is treated as a suggestion: Cyprian stores it with the conversation or proposal so you can review it, but the model does not itself approve, schedule or publish a post. Cyprian does not use your instructions or content to train its own general-purpose model.
Where an owner or admin has approved an automated-reply rule for a connected messaging channel, Cyprian also sends the text of customer messages received on that channel, together with the business facts the owner entered and approved in the Business Profile, to the same provider. We do not separately send customer profile fields such as a name, phone number or account identifier, or message attachments. The customer message text and recent conversation may themselves contain personal information that the customer or your team wrote, and that text is sent to the provider for this reply. Requests are sent with the provider’s storage disabled; the provider does not use this content to train its models and may keep a request only for a limited period for abuse monitoring under its own API terms. If Cyprian ever uses Google’s Gemini for this processing, it will do so only on terms that exclude training on your content.
Under an approved rule the reply is composed only from those approved business facts and is sent to the customer automatically, on the rule’s authority rather than a person’s. Every automated reply is marked as automated and tells the customer how to reach a person. Cyprian stops answering automatically in a conversation as soon as someone takes it over, whether they reply in Cyprian or from the platform’s own tools, and as soon as a customer asks for a person. Automated replies are off by default, apply only to the channel the rule names, and can be switched off for that channel at any time.
Cookies and website analytics
Essential storage remembers security and privacy choices needed for the site to work. Google Analytics loads only after you accept analytics on cyprian.ai. It uses the first-party _ga identifier and collects the website information described above. Advertising storage, advertising user data and advertising personalisation remain disabled. You can reject analytics or withdraw consent at any time through the Privacy choices control in the footer; we then remove the Analytics cookies available to this site and reload without the Google tag.
The web workspace at app.cyprian.ai uses essential cookies to keep you signed in, protect your session and remember display preferences. It loads no analytics or advertising tags.
Who receives information
We disclose only what is needed to the following categories of recipients:
- Platforms you connect, for the actions described above.
- Infrastructure providers, including Supabase for authentication and database hosting, Cloudflare for site delivery, security and media storage, and Fly.io for application hosting.
- Stripe, for subscription checkout, payments and invoices.
- Resend, for service email such as sign-in links, booking confirmations and reminders, and trial notices.
- Apple and Google, when you choose to sign in with them through Supabase Auth. They learn that you are signing in to Cyprian and return your email address, an account identifier and, where you allow it, your name.
- OpenAI, for assistant and inquiry processing when OpenAI is the selected provider.
- Google, for assistant and inquiry processing when Gemini or its optional fallback is enabled, and for website analytics only after you accept it.
- Professional advisers, authorities or a successor to our business, where necessary to comply with law, protect rights and security, or complete a legitimate corporate transaction.
Service providers may process information only for the function they provide to Cyprian or as otherwise permitted by their applicable terms and law. We do not give them permission to use your content for unrelated advertising.
Where information is processed
Cyprian’s primary account and publishing database is configured in Ireland. Media is stored in Cloudflare R2 with a Western Europe location hint. A location hint is not a legal residency guarantee. Our providers and the social platforms you choose may process information in other countries. Where data-protection law requires a transfer safeguard, we rely on an applicable lawful mechanism made available by the recipient, such as standard contractual clauses or an adequacy decision.
Security
We use encrypted network connections, encryption for sensitive stored credentials, access controls, workspace isolation, restricted storage access, and audit and security monitoring. Credentials held directly by Cyprian are separated from the content returned to the app. No Internet service can guarantee absolute security; if you believe your account or a connection is at risk, contact us immediately.
How long we keep it, and how to delete it
Google Business Profile content has a separate lifetime. It becomes unavailable for use 21 days after its original capture and is removed by day 30. These limits cover cached profile and review data, photo and post records, native performance data, and copies in reply snapshots, drafts, proposals and saved Business Context, including old revisions. Active profile and review caches are refreshed within 24 hours; other feature data is fetched when needed and marked stale after 24 hours. A successful complete fresh read can refresh a current cache; it cannot extend the life of an older snapshot or approved draft. Confirmed source removal and disconnect trigger earlier cleanup.
Facts imported from Google remain temporary, attributed Google data after your team approves them. Approval does not restart their lifetime. Cleanup removes the still-matching Google contribution while preserving independently entered replacements and your original uploaded media. Expired pending changes need a fresh read and a new exact human review before they can be sent.
Google cleanup runs in bounded hourly batches. Only content-free operational records remain for up to 90 days: local references, the approved operation, who acted, local attempt times, counts and outcome categories. They exclude Google content, native identifiers, links, review text and content digests. A separate content-free hold can remain while an uncertain external result must be reconciled, or until the whole local business workspace is deleted. That hold prevents the same action from being sent again.
The same Google content deadlines apply to temporary copies, exports and recovery copies. This connection will be enabled in a hosted environment only after its storage and recovery controls meet those deadlines. The normal backup cycle described below does not extend Google Business Profile content lifetimes.
We keep account, workspace, content and publishing information while you use Cyprian and for as long as it is needed for the purposes above. Connection credentials are kept until the connection expires, is disconnected or is deleted. Temporary upload and processing records may be kept for a shorter operational period. Limited security, audit and legal records may be retained when necessary to prevent fraud, resolve a dispute or comply with law.
To request account or personal-data deletion, email us at hello@cyprian.ai. We may verify your identity and authority over the workspace before acting. We will delete or de-identify information from active systems unless it must be retained for a lawful reason, and respond within the period required by applicable law. Encrypted backup copies may remain until they are overwritten through the normal recovery cycle and are not used for any other purpose.
Disconnecting a platform makes that connection unusable by Cyprian and removes or disables the credentials under our control. You can also revoke Cyprian directly in the platform’s security settings. For Google, use Google’s third-party access settings. Disconnecting or deleting Cyprian data does not remove content already published on a social platform; delete that content through the platform itself.
Google Business Profile disconnect. Disconnecting one business immediately stops use of that business’s connection and schedules its known Google content for the next protected cleanup batch. Another business or Google feature can still use the same Google authorization. Cyprian removes the detached business’s connection material while preserving the other active consumer, and attempts provider-wide revocation only when no active consumer remains. Detached credentials and the end-client disassociation are completed through the protected handoff no later than seven business days after termination. Uncertain revocation or permission-removal outcomes remain visible until resolved. Disconnecting does not delete content already published on Google; manage that content on Google itself.
YouTube connection deletion. When you disconnect YouTube inside Cyprian or ask us to delete its Authorized API Data, Cyprian immediately fences the connection, stops reading comments, attempts to revoke Google access, deletes the stored tokens and non-statistical YouTube Authorized API Data, including stored comments, from active systems within seven calendar days, and expires encrypted backup copies no later than 30 days after the request. If you revoke Cyprian in Google’s settings, our periodic authorization check makes the connection unusable and completes that deletion as soon as possible, no later than 30 days after you revoke that authorization. Neither path deletes videos already hosted by YouTube; delete those videos on YouTube itself.
Your rights
Depending on where you live, you may have rights to access, correct, delete or receive a portable copy of your personal information; object to or restrict certain processing; withdraw consent; and complain to a data-protection authority. We will not discriminate against you for exercising a privacy right.
To exercise a right, email hello@cyprian.ai and say what you are requesting. We may ask for information needed to verify your identity and will respond within the period required by applicable law. An authorized agent may submit a request where local law allows it, subject to verification of their authority.
Children
Cyprian is not intended for anyone under 16, and we do not knowingly collect their data. If you believe a child has an account, tell us and we will remove it.
Changes
We may update this policy as the service or law changes. We will update the date at the top and provide additional notice where the change or applicable law requires it.
Cyprian is operated by Cubeshell LLC.
Registered address: 1309 Coffeen Avenue, Suite 1200, Sheridan, Wyoming 82801, United States.
Questions, requests or complaints: hello@cyprian.ai