Privacy Policy
Effective date: October 1, 2026
Superlaunch is operated by Individual Entrepreneur Piven Bohdan, the sole proprietor registered in Ukraine. We are the data controller for the account, billing, security and support activities described here. Contact: privacy@superlaunch.pro.
This policy covers our website, application, account administration and support. For personal data supplied through a business workspace, the business may determine the purposes of processing and we may process it on that business's instructions. Contact the workspace's responsible business about its handling of that data; we can help identify the appropriate route. Our own account, billing, security and support activities remain covered by this policy.
1. Information we process
| Information | Examples and source |
|---|---|
| Account and membership | Email, display name, profile image where supplied, authentication identifiers, verification status, workspace memberships, roles and invitations. We receive these from you, your sign-in provider or an authorized workspace member. Our authentication service handles password sign-in. |
| Workspace and connected advertising data | Workspace settings, brand information, connected business/ad-account identifiers, campaign and creative information, performance data, and credentials or tokens needed for authorized connections. We receive these from you and the advertising platforms you connect. |
| Rules, tools and memory | Rule settings and schedules, authorized tool requests and results, action/approval records, usage and audit records, and the memory text and search requests needed for the features you use. |
| Billing | When paid checkout is available and used: billing contact and purchaser details, workspace and subscription references, purchased items, amounts, currencies, taxes, payment and refund status, invoices and trial dates. Our payment reseller supplies relevant purchase records. |
| Support | Messages, attachments and information provided when you contact us, together with account/workspace context used to handle the request. |
| Technical and usage information | IP address, device/browser information, request and event times, diagnostic/security logs, page interactions and analytics information described below. |
Provide only data you are authorized to share. Do not send passwords, access tokens or full payment-card details in support messages.
2. Why we use information
We use personal data for the purposes below. Where applicable law requires a legal basis, the basis depends on the activity and our relationship with you.
| Purpose | Basis and practical examples |
|---|---|
| Provide the service | Perform our contract with you: create your account, authenticate sign-in, manage workspace access, connect accounts and carry out authorized rules and tool requests. We process customer-controlled workspace data on the customer's instructions under the applicable customer arrangement. |
| Support and improve the service | Our legitimate interests in answering support requests, diagnosing errors and understanding usability, taking account of your rights. For example, we use navigation events to identify a confusing setup step. |
| Protect accounts and operations | Our legitimate interests in preventing unauthorized access, investigating misuse and maintaining reliable operations. For example, we review access logs to investigate a reported unauthorized action. |
| Manage billing and legal records | Perform our contract when administering a purchased plan and comply with applicable legal obligations for financial records and required disclosures. |
| Processing that requires consent | Consent where required by applicable law for an optional activity. You may withdraw consent by contacting us; withdrawal does not affect earlier lawful processing. |
Your right to object: where we rely on legitimate interests, you may object for reasons relating to your circumstances by contacting privacy@superlaunch.pro. We will assess the request under applicable law.
We need account and authentication information to provide sign-in and workspace access. A connection requires the identifiers and authorization needed to access that platform. If you do not provide this information, we cannot provide the corresponding feature. You choose whether to supply optional profile information or connect an external account.
3. Workspace access and external AI clients
Information is available to workspace users according to their permissions. When workspace billing screens are available, financial-management screens are restricted to the current workspace owner. Authorized service personnel may access information where needed to provide support, maintain security or administer the service.
If you authorize an external AI client to use Superlaunch tools, that client can receive data returned by permitted requests and may cause permitted actions. Its separate provider controls its own processing. Review the client's permissions and privacy terms before connecting it. Revoking access prevents future authorized requests; it does not retrieve copies already delivered to that client.
4. Payments
Our current payment reseller provides hosted checkout and customer portal services for new purchases. We share the billing contact and selected offer needed to process the purchase. See Payment Reseller Privacy Notice. For earlier purchases, consult the privacy notice identified in your receipt.
Payment-card entry and updates take place in our payment reseller's hosted checkout. Superlaunch does not receive or store the complete card number or security code from that flow. Where available, we receive limited payment-method information, such as card brand, last four digits and expiry date, for billing display and support.
The reseller also determines how it processes information for payments, fraud prevention, taxes and legal obligations. It acts as an independent controller for those activities. Our Terms of Service describe the reseller's role and link to its purchase terms. Review the privacy notice provided in checkout. A payer's receipts remain separate from permissions to view a workspace's billing screen.
5. Who receives information
We use service providers for the activities below. The information they receive depends on the feature you use and its configuration. Contact privacy@superlaunch.pro for the identity and processing details of a provider relevant to your data.
| Recipient category | Purpose and information shared |
|---|---|
| Cloud hosting and authentication | Store and operate the service and authenticate accounts. Information can include account identifiers, authentication records, workspace content, connection credentials and technical or security logs. |
| Platforms you connect | Exchange account data and access tokens needed for the connections and actions you authorize. Social sign-in and advertising-account access are separate authorizations. |
| Customer support | Process support messages and attachments. In the signed-in app, the integration receives your user identifier, available name, email and avatar, and workspace identifier, name and role. This can happen before you open a chat. |
| Usage analytics and session replay | Analyze website and app interactions to understand navigation and diagnose usability issues. Activity can be associated with an internal user identifier and workspace role, workspace count and onboarding status. An internal identifier is not anonymous. |
| Font delivery | Deliver fonts requested by your browser. These requests disclose information needed to deliver the files, such as your IP address and browser information. |
| Current payment reseller; previous reseller for earlier purchases | Provide hosted checkout and process purchases, subscription records, payments, refunds and related financial information as described in section 4. |
| Semantic search and embedding services | When semantic memory is enabled, process saved memory text and search-query text to create and search numeric representations. |
| Email delivery | Process message addresses, content and delivery information to send or receive account and support emails. |
We may also disclose information to authorities or other recipients where the law requires it, to protect legal rights, to address security or fraud, or with your authorization. We limit disclosure to the information needed for the relevant purpose.
6. Browser storage and analytics
Authentication and application features use browser storage to maintain sessions and necessary state. Support and analytics integrations also process browser activity and identifiers. Blocking browser storage can affect sign-in or support continuity.
Our analytics integration sends denied advertising-storage and analytics-storage signals. These settings limit storage; they do not stop all analytics processing or session replay. The integration can process interactions without cookies and supplies the internal user identifier and workspace tags described in section 5.
Browser privacy settings let you manage stored information. For questions, consent withdrawal or an applicable objection to analytics processing, contact privacy@superlaunch.pro. We will assess and honor rights and choices required by applicable law.
7. International processing
Superlaunch is established in Ukraine. Service providers may process information outside your country, including in the United States, where our cloud backup storage is configured. These countries may have different data-protection laws.
Contact privacy@superlaunch.pro for the countries and safeguards relevant to a specific processing activity, including how to obtain information about an applicable transfer mechanism. The relevant safeguards depend on the recipient, destination and processing activity.
8. Retention and deletion
We keep information for the purposes described here and do not use the same retention rule for every category.
| Category | Retention approach |
|---|---|
| Active workspace content | Kept as needed to provide the workspace's service and carry out authorized instructions. |
| Ended workspace content | Workspace content is handled under the deletion process described below. Contact us about a specific workspace or verified deletion request. |
| Connection credentials | Kept while needed for authorized connections; access is revoked or disabled when the connection ends. |
| Billing, purchased-usage balances and disputes | Only records necessary for outstanding balances, transaction integrity, refunds, disputes and applicable legal obligations are retained separately from operational workspace content. Ending a subscription does not require erasing a legally required financial record. |
| Routine cloud logs | Kept for troubleshooting and security according to the configured retention periods. Separate audit records may be kept longer where needed to investigate actions or meet legal obligations. |
| Support, diagnostics and security records | Kept as needed to resolve the request or investigation, protect the service and meet applicable legal obligations. Contact us for the retention criteria for a specific record. |
| Backups | Deleted information may remain in restricted backups until the relevant backup copies are deleted. Contact us for the current backup schedule for a particular request. |
We assess exceptions individually, such as an unresolved dispute or a legal preservation obligation. Payment resellers and other independent controllers apply their own retention rules to records they control.
9. Your choices and rights
Depending on the law that applies, you may request access, correction, deletion, restriction, a portable copy, or an objection to processing. You may withdraw consent where processing relies on it; withdrawal does not affect earlier lawful processing. You may complain to the competent data-protection authority, including the authority where you live or work when applicable law gives you that right. You may contact us first to help resolve a concern, but this is not a condition for making a complaint.
Contact privacy@superlaunch.pro, preferably from the email associated with your account. Identify the account or workspace and the request, but do not include passwords, tokens or full card details. We may ask for proportionate information to verify identity and authority. A request concerning shared workspace data may need coordination with the business responsible for it; one member's departure does not automatically delete records other authorized members still need.
See our data-deletion instructions. Disconnecting a provider stops future access through that connection but does not automatically delete existing records. A data-deletion request is handled separately from subscription cancellation; ask for and retain the payment reseller's cancellation confirmation if you have a paid purchase. A request to delete an individual member's information does not itself cancel another owner's workspace. Necessary financial records may remain, but payment reconciliation is not a reason to retain all workspace content indefinitely. We will explain any lawful restriction and respond within the applicable legal timeframe. For requests subject to the GDPR, this is normally within one month of receiving the request; if a permitted extension is needed, we will explain the reason and timing.
10. Security, children and changes
We use technical and organizational measures intended to protect information, including access controls and secured connections. No system provides an absolute security guarantee.
Superlaunch is intended for business users aged 18 or older. If you believe a child has supplied personal data, contact privacy@superlaunch.pro.
We may update this policy as processing changes. The effective date identifies the current version, and we will provide additional notice where required for a material change.