Sellonn privacy notice

Who is responsible for your information

Verve Plus is responsible for the personal information it uses to run Sellonn, administer creator accounts and subscriptions, protect access, carry out the invited pilot and respond to its own enquiries and privacy requests.

Creators choose the products, forms, connected accounts and automation rules for their businesses. When an independent creator uses Sellonn to handle its customers' information, that creator is responsible for its business purposes and we process the information on its instructions. This includes hosting customer records, delivering purchased content, applying selected message rules and recording the customer's choices. The creator's privacy information should explain its use of your information, including uses outside Sellonn. If Verve Plus also operates the creator business, Verve Plus is responsible for that business's use too.

Why Verve Plus uses information

We use account, contact, access and subscription information to provide the creator service and respond to requests about it. Where this is necessary for an agreement with you personally, or steps you ask us to take before entering that agreement, our basis is contract. If you take part in our invited pilot without a personal service agreement, or act for a business, our basis is our legitimate interest in administering your requested access and supporting the service.

We use service records to protect accounts, apply usage limits, prevent repeat or mistaken processing, investigate faults and maintain a recoverable service. We also use selected test and diagnostic records to check that the invited pilot works as intended. Our basis for these purposes is our legitimate interest in operating a secure, reliable service. These records can include identifiers, delivery outcomes and relevant message or screen content. We assess what is necessary for the particular issue; the recipients and retention sections below explain how these records are handled. You can object to use based on legitimate interests by contacting us.

We use the information needed to handle your privacy request and demonstrate our response to comply with applicable data-protection duties. For information we process on an independent creator's instructions, we assist that creator with the request. Tell us the business involved so the relevant records can be identified.

Your creator account and workspace

We use your email address, password verification record, verification and recovery records, account status and workspace membership to sign you in, recover your account and control access to your businesses. Passwords are stored as salted hashes. We also keep session, security and delivery records to operate the service and help prevent misuse; this includes processing a network-address-derived key for sign-in limits.

Workspace information includes the business details, product content, uploaded files and settings you save. Subscription records include the selected plan, billing status and payment-provider references. Account messages, such as verification and password reset emails, are separate from optional marketing.

We need an email address and password to create and secure a creator account. Checkout requires the customer contact and order details shown on the form; without required information, the relevant feature cannot be provided. Connecting Instagram and agreeing to marketing are optional. Declining marketing does not prevent a purchase.

Some service checks run automatically. Subscription status, access periods and usage limits can restrict creator features; verified order and payment status determine whether a purchase can be delivered. If you think a result is wrong, contact hello@sellonn.com and identify the account or order.

Connected Instagram accounts and conversations

When you connect an Instagram account, Meta supplies the account identifiers and account details needed for the connection. We store the selected account, permissions, connection status, expiry information and the creator who connected it. Where available, connection records also include the Meta business and login-configuration identifiers. Connection credentials are protected with encryption and used to make authorised requests to Meta.

When you ask Sellonn to check a connection token, we record the attempt time, result and relevant permission or expiry information. A previous conclusive result may remain alongside a later unfinished or inconclusive check. These dated checks are not continuous monitoring or a guarantee of future access.

For a connected business, eligible incoming events can include comments, messages, button responses, participant and account identifiers and event times. We use these to match the interaction to that business, evaluate the creator's automation rules, record the result and honour STOP requests. Conversation content can include an email address or other information a person chooses to send. Stored event and conversation content is encrypted; related identifiers and status records are also retained.

Automation rules can match words or responses, check a follow condition and choose a reply or follow-up, including a link or media card. We keep the rule and delivery information needed to process those interactions, avoid duplicate replies and apply message limits. A comment, direct message or email address supplied in a conversation does not by itself subscribe someone to email marketing.

When Sellonn can match a verified Instagram message-deletion notification to its records, it stops affected replies that have not yet been attempted and clears the message and related conversation content from active storage. This can also apply to retained records after an account is disconnected. Where older records cannot be separated reliably, other conversation records for that same participant within the business may also be cleared. Some older copies remain pending cleanup if their delivery history cannot be verified.

Limited identifiers, delivery records and existing consent or STOP records remain so deleted messages are not processed again and delivery attempts can be reconciled. This does not recall messages already submitted for delivery, revoke permissions at Meta or automatically erase provider copies, backups or customer information collected separately.

Customer orders and email choices

When an authorised pilot test uses checkout, the business receives the customer's name, email address, selected products, answers to checkout questions and order details. Sellonn keeps payment status and provider references, receipt access and fulfilment records so the order can be checked and delivered. Payment card entry takes place with Stripe.

Optional marketing is a separate choice. The checkout consent record includes the choice and the statement shown at the time. Unsubscribing applies to the relevant business. A purchase alone is not general marketing consent. Account verification, recovery and messages needed to service an order are separate from marketing. General customer marketing remains disabled during the pilot.

Where information comes from and who receives it

Information comes from you, the creator managing the business, connected Meta accounts and events, and service providers reporting delivery or payment results. Creators can view and manage information belonging to their own businesses through the features available to them.

Cloudflare provides the application hosting, database, file storage and encrypted recovery storage. Resend, operated by Plus Five Five, Inc., sends creator account emails and receives the email address and message needed for delivery. Stripe provides subscription and payment services. Meta provides the connected social-account service. These providers receive the information necessary for their respective features; social conversations are not automatically copied into an email marketing list.

Messages sent to hello@sellonn.com, including privacy requests, pass through Hostinger mail and are forwarded to the service owner's MSN mailbox. The owner is the sole person monitoring that mailbox.

We also use GitHub, Google Drive and OpenAI's Codex chat and tools for development and account setup. Operational records and screenshots can include Meta app identifiers and public business or account names. Private project and evidence copies are stored in GitHub, and some earlier copies are stored in Google Drive. Codex chat and tools have processed Meta setup screens and screenshots. These development and setup records are separate from Sellonn's full encrypted recovery copies.

If an available product-description drafting feature is used, the product title, type and brief supplied for that request are sent to Cloudflare's AI service. If stock-photo search is made available and used, the search and selection use Unsplash; loading an external image also sends a request from your browser to the image host.

International transfers

Our providers process information in the UK and other countries, including the European Economic Area and the United States. For hosting and payments, Cloudflare's and Stripe's transfer terms provide for the UK Extension to the EU-US Data Privacy Framework, with contractual alternatives. Resend's terms and Meta's Platform Terms include standard contractual clauses with the UK International Data Transfer Addendum for the UK transfers they cover. OpenAI describes the same contractual safeguards for its UK data transfers.

Contact mail passes through Hostinger and is forwarded to our owner's Microsoft consumer mailbox. Hostinger's terms cover onward international transfers; Microsoft's, Google's and GitHub's published policies describe their international safeguards, including contractual clauses and participation in the UK Extension to the Data Privacy Framework. UK adequacy arrangements also cover EEA recipients; a provider's onward transfers are a separate step. These arrangements do not mean that all data stays in one country. You can contact hello@sellonn.com for details of the safeguards relevant to your information and how to obtain a copy.

Cookies and storage in your browser

Creator sign-in uses a secure session cookie lasting up to eight hours. It is needed to keep the creator signed in and is not readable by page scripts. A social connection attempt is tied to the signed-in session and expires within ten minutes; expiry of an attempt does not itself erase every related record.

When you activate or pause an AutoDM rule, browser session storage temporarily keeps the business and draft identifiers, the type of change and its request or activation reference. An activation request also includes the saved draft revision. This lets Sellonn check an interrupted request without creating a new request identity. This reference contains no message content, password or social access token. It is cleared when the outcome is confirmed or Sellonn can establish that the older request can no longer apply. Clearing browser storage does not reverse an activation or pause already recorded by Sellonn.

During checkout tests, browser session storage keeps the pending checkout details and request reference so an interrupted checkout can be resumed. It also keeps the private key that opens a receipt and a reference for an unfinished card-update request. This storage is separate from the creator sign-in cookie. Clearing it can prevent recovery in that browser unless you still have the private receipt link. It does not cancel an order or delete server records. Keep private receipt links confidential.

Browser session storage also remembers your selected display language separately for each creator's business in that tab.

Disconnecting, closure and retained information

Disconnecting a social account removes its stored connection token from active use in Sellonn and marks the connection disconnected. It does not erase earlier messages, events or account history, and it does not revoke the separate permission held at Meta. Review that permission in your Meta account as well.

Where workspace closure is available, it records a request, suspends the workspace and disables its automations. Work already attempted or linked to a provider requires separate review. Existing order and billing records can still need servicing. A closure request is not confirmation that personal information has been erased.

Information can remain in the database, uploaded files, provider systems and encrypted recovery copies after access is stopped. Unsubscribing, disconnecting, archiving content and closing a workspace are different from requesting erasure. Contact hello@sellonn.com to request deletion or ask about retained information.

How long information is kept

We decide retention by the purpose of the information and any outstanding obligations, rather than applying one expiry period to every record.

Account, membership, business content and uploaded files are kept as needed to provide the workspace and recover access. Closure, abandonment of a test account, replacement of a file or a deletion request prompts review of what remains necessary for a specific order, security issue or recovery need.

Social content is kept for the interaction or identified automation test and any unresolved delivery or deletion issue. We review it when the interaction or test ends, a rule is retired, an account disconnects or a relevant request arrives. Limited delivery receipts, consent or STOP records and duplicate-prevention records may need to remain while the associated processing or restriction continues; that does not require keeping every message body.

Order and payment records are kept as needed to deliver the service or file, provide continuing customer access, reconcile payments and resolve an actual refund, installment, dispute or claim. Further legal retention depends on a specific applicable duty or claim, rather than an assumed period for all order information.

Correspondence and test evidence are kept for the particular request, incident or test. Identified recovery snapshots are also retained during the closed pilot to validate restoration, compare failures and maintain a recovery copy. We review that need when the relevant work finishes, a verified replacement is available or a privacy request affects the information. Older verified snapshots remain preserved pending decisions about which copies can be retired. Recovery archives do not currently expire automatically.

A review can find that a limited record is still needed. Expiry of a login session, connection attempt or access link stops its use but does not necessarily delete every associated record. Requests can cover relevant live information, provider copies, correspondence, development evidence and recovery copies; encryption alone does not make those copies erased.

Your information rights

Depending on the circumstances, UK data protection law gives you rights to access your personal information, correct it, request erasure or restriction, and receive or transfer information covered by the right to data portability. Where processing relies on consent, you can withdraw it at any time, without affecting processing that was lawful before withdrawal. Use the relevant unsubscribe option or contact us.

To raise a request or complaint, email hello@sellonn.com. No special legal wording is needed. You also have the right to complain to the Information Commissioner's Office at https://ico.org.uk/make-a-complaint/.

Your right to object

You can object to use of your personal information for direct marketing at any time. You can also object, for reasons relating to your circumstances, where processing relies on legitimate interests. Contact hello@sellonn.com and identify the relevant creator business where applicable.

Requesting deletion

Email hello@sellonn.com to request deletion, identifying the relevant creator business where applicable. Our deletion instructions explain what information helps us locate the records and how existing message-deletion, disconnect and closure controls differ from a broader request. Do not send passwords, payment-card details, social tokens or private receipt links.