™United States
privacy, security, consumer-protection, and opt-out expectations
privacy
Privacy fundamentals for creators and teams.
lykbl is launching for US/Australia/EU customers with data minimisation, customer control, and Stripe-hosted payments as defaults.
Australia
Privacy Act and Australian Privacy Principles expectations
European Union
access, export, deletion, and consent expectations for later GDPR review
Regional launch posture
- US customers: outreach stays customer-facing, opt-outs are honored, and sensitive categories are not used for targeting.
- Australia customers: collection stays limited to the stated purpose, and personal information is protected against misuse, loss, and unauthorized access.
- EU customers: request, export, deletion, consent, and connection history stays reviewable for later privacy review.
What lykbl keeps focused
Account, billing, agent, connection, and content data should stay tied to the workflow a customer chooses.
- Privacy by design: privacy and security checks are part of the workflow before launch traffic scales.
- Data minimisation: lykbl asks for the information needed to run the selected workflow.
- Purpose limitation: creator, billing, agent, and connection data stays tied to the product experience the customer chose.
- Customer control: customers can request access, export, correction, deletion, and social connection disconnect support.
- Consent and provenance: social connections, agent runs, paid intent records, and publishing actions keep reviewable evidence.
- No automation-only outreach: external messages and contact forms require human approval before anything is sent.
Privacy requests
Customers can ask for access, export, correction, deletion, or help disconnecting a social account. Some billing, tax, fraud, dispute, and security records may need to be retained where required.
Contact: support@lykbl.ai
accessexportcorrectiondeletionconnection disconnect
Payments
- Stripe-hosted Checkout Sessions, Stripe Payment Links, and Stripe-hosted billing portal flows are the allowed payment surfaces.
- Card details are handled by Stripe; lykbl does not collect, store, display, or proxy raw card data.
- Payment links use HTTPS and real Stripe-hosted payment pages.
- Checkout uses non-secret reference IDs and avoids putting buyer email in payment-link URLs.
- Payment help routes customers back to Stripe-hosted checkout instead of app-hosted card forms.
- Credits activate after Stripe confirms payment or a reviewed support record is complete.