Privacy

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 mobile app, and the systems that 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.
• 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 _ga identifier 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. Connecting YouTube requests exactly two permissions and no others: https://www.googleapis.com/auth/youtube.upload to upload the video and metadata you approve, and https://www.googleapis.com/auth/youtube.readonly to name the channel you are publishing to and to read back the visibility of the video we just uploaded, so we can tell you the truth about whether it is actually viewable. This connection does not ask to manage your account, read your comments, or see your audience statistics. We do not use Google user data for advertising 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, and our use of Google data follows the Google API Services User Data Policy, including its 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.

TikTok. Cyprian holds this authorization directly under its own TikTok client, and the TikTok authorization screen names Cyprian. Connecting TikTok requests exactly two permissions and no others: user.info.basic to identify and show you the exact TikTok account you are about to post to, and video.publish to post the video or photos you approved and to read back what TikTok did with them. That second permission is also what lets Cyprian ask TikTok, immediately before you review a post, which privacy settings and interaction settings your account currently allows — so the choices we show you are yours and current, never assumed. Access and refresh tokens are held encrypted on Cyprian’s servers and are never sent to the app on your phone. Disconnecting a TikTok account revokes the authorization with TikTok and deletes the stored tokens; posts already published stay on TikTok and are yours to delete there. This connection does not ask to read your inbox, your comments, your followers or your analytics, and Cyprian requests no TikTok permission that does.

Google Business Profile. When this connection becomes available, connecting a Business Profile will request business.manage, which is the only permission Google publishes for this API — there is no narrower read-only or publish-only alternative, so the same permission covers listing the locations you manage, publishing the posts you approve, and replying to reviews when you ask. Cyprian will use it only for those three things. If you connect a profile, we will store the account and location identifiers you select, the authorization status and the publishing receipts needed to provide the feature. We do not use Google user data for advertising, do not transfer it for unrelated purposes, and do not use it to train a general-purpose model. 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 an inbox and social media manager, 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 App Review and Advanced Access for ordinary customers remain pending.

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.

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

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.

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.
• 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

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.

YouTube connection deletion. When you disconnect YouTube inside Cyprian or ask us to delete its Authorized API Data, Cyprian immediately fences the connection, attempts to revoke Google access, deletes the stored tokens and non-statistical YouTube Authorized API Data 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 we detect that the authorization can no longer be refreshed. 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.