1. Operator and scope#
Contact Saletise at [email protected] with privacy questions and requests about the processing described here.
We determine how account administration, security, product operation, and the shared lead pool are organized. Project communications can also be processed to provide services requested by an account customer. The legal roles and any required processing agreement depend on the particular activity; this notice is not a substitute for a required data-processing agreement.
2. Information involved#
- Account information: name, email, sign-in identifiers, password hashes for password accounts, profile pictures, preferences, and account-plan records. Google sign-in can provide a Google identifier, email, name, and profile image.
- Project information: website addresses, website-derived product facts, audience analysis, chosen methods, sender identity, social links, launch copy, images, schedules, publishing URLs, and activity records.
- Outreach information: contact names, email addresses, business or project details, public websites, available business phone information, source descriptions, relevance categories, messages, message identifiers, delivery records, reply classifications, and unsubscribe or suppression records.
- Connected-service information: authorization tokens where an integration requires them, connection identifiers, permitted Search Console or verification information, publishing status, and traffic configuration or estimates.
- Support and technical information: what you send us, request and error information, browser/device information and IP addresses received by hosting or service systems, and security or operational logs.
- Billing information: selected plan and billing period, checkout references, provider customer, subscription, payment and refund identifiers, transaction amounts and currencies, subscription and payment status, trial-related subscription records and next billing dates, and invoice information retrieved when requested. Dodo Payments collects payment and required tax or billing information on its hosted pages.
Free-trial accounts and billing data#
The same account, project, automation, security, and billing processing described in this policy applies during a free trial. Dodo Payments collects the required payment method on its hosted checkout even when no subscription fee is due during the trial. Saletise receives subscription identifiers, status and billing dates needed to verify trial access, display billing information, and manage the transition to paid access or suspension.
Cancelling a trial stops renewal according to the confirmed subscription status; it does not itself delete your account, workspace, or provider records. Account deletion and privacy requests are separate controls. Trial records follow the retention and deletion provisions below, including any records needed for billing, security, disputes, or legal obligations. Starting a trial is not consent to optional marketing or non-essential tracking.
3. Where information comes from#
Information can come from you, a project website, emails and replies, authorized connected accounts, public business pages or repositories, lead suppliers, and services used to operate the product.
A website analysis or public source may contain information about people who never created a Saletise account. Public availability does not remove privacy rights or by itself authorize marketing.
4. Purposes and choices#
- Create and authenticate accounts, provide requested project features, preserve preferences, and respond to support requests.
- Analyze project information; categorize and compare contacts; generate messages or launch copy; process replies; and keep project activity records.
- Carry out the email, publishing, traffic, or connected-account operations requested through the relevant workflows and settings.
- Prevent duplicate sends, honor unsubscribe requests, investigate errors or abuse, protect access, maintain service records, and meet applicable legal obligations.
- Create checkout sessions, verify free-trial subscriptions, purchases and renewals, maintain account plan access, retrieve payment history and invoices, and handle billing, cancellation, or refund inquiries.
5. Providing information and applicable grounds#
You choose whether to create an account or submit a project. Account and project information needed for a requested feature cannot be omitted while still expecting that feature to operate. Optional integrations, profile images, and support details need not be provided unless you want the related functionality.
Processing must have a valid basis under the laws that apply to it. Depending on the activity, this may concern a requested service or contract, a legal obligation, a permitted legitimate interest, or consent where required. We do not treat acceptance of Terms, public contact details, or a project score as universal consent to marketing.
Where consent is the basis, you can withdraw it for future processing through the relevant control or support. Withdrawal does not automatically undo processing already lawfully completed. Additional rights depend on applicable law.
6. AI and other recipients#
Website or project text, relevant contact information, and message history may be sent to configured AI providers or routing services for analysis, ranking, drafting, and reply classification. AI services can return inferences or incorrect information about a contact.
Information needed for the selected operation can also be provided to hosting and storage services, email providers such as Sendcorex, lead suppliers, Google services, traffic providers, and the external launch platforms you use. Recipients and other email systems receive the messages sent to them. Support information can be handled by the systems used for support.
For paid subscriptions and Starter free trials, account name, email, selected plan, and an internal checkout reference are sent to Dodo Payments. Account name and email may be prefilled. Dodo Payments collects the billing country and any postal code or other information required for tax or the payment method; required fields cannot always be skipped. It acts as merchant of record and independently processes transaction data for payment, fraud prevention, tax, and other applicable obligations. Payment details are entered on its hosted pages; Saletise does not receive or store full card numbers or security codes. Saletise stores provider identifiers and checkout or subscription summaries, verifies provider notifications, and retrieves payment history and invoice PDFs for authenticated account access. Invoices may contain the billing information held by the provider.
Verified payment and refund notifications can be sent to an operator-controlled Discord channel with account identity, plan, billing cycle, payment, subscription and refund identifiers, amount, currency, status, and full or partial refund classification. Billing addresses, card details, and free-text refund reasons are excluded from these Discord notifications.
Account and project activity logs can be sent to an operator-controlled Discord channel for operational monitoring. These logs include account email and user ID, relevant project names, domains and IDs, action types, selected setting summaries, and timestamps. Error reports can also include account identity when signed in, route patterns, HTTP status, error types, code locations, and a request identifier. Browser reports cover JavaScript, resource-loading, and network failures. Passwords, access tokens, payment details, private message contents, raw exception messages, request bodies, and URL query strings are excluded from these Discord reports. Pending logs are queued locally for delivery. Browser error reporting uses a session token; a keyed hash of the request IP address is used locally to limit report abuse, and the IP address is not included in the Discord embed.
Activity monitoring records selected account and project actions such as sign-in, signup, project creation, and saved settings; it does not record every click or page view. Routine signed-out responses, missing-page responses, validation rejections, and expected offline or navigation failures are filtered from Discord error alerts. Monitoring is for operation and diagnosis, not a guarantee that every error will be captured. Discord processes delivered messages under its own policies.
A provider's retention, processing location, and use of submitted content depend on its applicable terms and configuration. Do not assume that this notice guarantees a particular provider's zero retention or that all providers exclude every form of model improvement. Contact us for information relevant to a planned sensitive use.
8. Public publishing and the optional extension#
Content you authorize for publication can become public on external platforms and may be copied, indexed, or retained by others. A later account deletion does not remove those independent copies.
The optional launch extension reads and fills supported platform pages to carry out the launch flow. It handles saved launch copy, media references, page state, and progress information, and communicates results back to Saletise. Installing the extension gives it the browser permissions shown at installation. It also uses browser or site session storage as described in the Cookie Policy.
9. Processing locations#
Our providers and the external platforms used for a project may process information across national borders. The countries involved depend on the services and configuration in use.
This policy does not by itself provide a legal transfer mechanism. Where applicable law requires a particular basis or safeguards for an international transfer, those requirements must be satisfied separately. Contact [email protected] for details relevant to your data or integration.
10. Retention and deletion#
Account, project, and message records are generally kept while needed to operate the service, maintain requested records, or address a legitimate legal or operational requirement. Not every record category currently has a fixed automatic deletion period. We do not promise that all data disappears immediately or after one universal deadline.
Account and project deletion controls remove the associated active workspace records handled by those controls. Separate logs, shared contact records, delivery-provider records, or legally necessary records can require separate handling. Independently delivered emails and public third-party posts are not withdrawn by deleting your account.
Pending Discord reports are held locally for delivery. Successfully delivered payloads are removed from the local delivery queue, while the messages remain in the Discord channel; failed delivery records can remain for diagnosis. Deleting a project or account does not automatically remove previously delivered Discord messages. Provider billing records, invoices, and payment or refund records may need to remain for accounting, legal, security, or dispute handling. Contact support for a request concerning these separate records.
A minimal suppression or used-contact record can be retained to honor objections and avoid another send. Contact support to ask about the records, recipients, and retention relevant to you, or to request deletion where you have that right.
11. Security#
The application uses access controls and password hashing for password accounts. Some integration credentials use encrypted storage. These measures are not a promise that every stored field is encrypted or that unauthorized access can never occur.
Protect your sign-in access and notify support if you suspect an incident. Do not place secrets or unnecessary sensitive information into project text, outreach messages, or support requests. Any legally required incident notifications are governed by applicable law.
12. Your rights and outreach objections#
Depending on applicable law and the circumstances, you may have rights to access or correct personal information, request deletion or restriction, object to particular processing or direct marketing, receive a copy, or withdraw consent. Some rights have exceptions and are not unconditional in every situation.
Email [email protected] and identify the relevant account or recipient address. We may request proportionate verification to protect against unauthorized disclosure. We will assess requests under the applicable rules and explain a refusal or limitation where required.
Outreach recipients can use the email's unsubscribe link or ask to stop in a reply. You may also ask about the source of your information or request review of a contact record. An automated Interested or Converted label is not proof that you visited a site or purchased a product.
You may contact a competent privacy regulator where applicable. Contacting us first is not a condition for exercising an independent complaint right.
13. Updates#
We will date material revisions and provide additional notice where required. This notice describes the current product and does not grant permission for unrelated future processing. Questions: [email protected].