How AwesomeSoft collects, uses, stores, and protects information when you use the Postli Shopify application and the usepostli.com website.
Postli is operated by AwesomeSoft ("we", "us"). Postli helps Shopify merchants create short links, schedule social content, and measure clicks, conversions, and revenue. Contact us at awesomesoft.io@gmail.com.
We act as a processor for personal data merchants entrust to us to run their links, publishing, and attribution. The merchant is the controller (or a processor acting for its own controller). We act as a controller for our own account administration, billing records, support, security, and marketing-site analytics. Our Data Processing Agreement (DPA) governs processing on merchants' behalf.
This policy covers usepostli.com, the embedded app at app.usepostli.com, short links at pstl.sh, and Postli tracking on participating merchant storefronts. Shopify and connected social platforms have their own privacy policies. Merchants must explain their use of Postli in their own privacy and cookie notices.
Shop identifiers and domain, merchant contact and store settings, approved Shopify access tokens, subscription and usage records, and messages you send us. Shopify handles subscription payment collection; Postli does not need your payment-card number.
When you authorise a connection, we receive account, profile, page, organisation or board identifiers, display names, profile images, granted permissions, access and refresh tokens, and available account and post statistics. We store drafts, captions, media, schedules, platform settings, auto-comments, publication results and error logs. Content and media are sent to the platforms you select and may become public there.
We process link destinations, short codes, tags, UTM parameters, click identifiers, timestamps, referrers, device/browser/operating-system information, and bot or abuse signals. The click-processing job uses the incoming IP address for approximate location (country, region, city and coordinates) and stores a SHA-256 hash combined with an application secret, rather than a raw IP in the click record. User-agent information is parsed and hashed. Raw request information may pass through servers, queues and security/activity logs; hashing click records does not make all processing anonymous.
Storefront tracking can record page interactions related to a Postli link, add-to-cart leads and checkout conversions. Conversion records can include a customer email address and external customer identifier, event name/type, amount, currency, time and metadata supplied by the merchant or Shopify. Order attribution uses order identifiers, totals, currency, item counts, line items and related click information. We do not need full customer profiles or shipping addresses to provide attribution.
The app configuration requests read_products, read_orders, read_files, write_files, read_themes, write_themes, write_pixels, and read_customer_events. These support product/media selection, order attribution, and storefront tracking setup. The installation and permission screens show the permissions actually authorised.
When you ask Postli to generate or improve content, we send your prompt or draft and selected context (such as product title/description, link URL, platform, language and tone) to Anthropic to generate a response. This is separate from conversion tracking; Postli does not automatically send shopper conversion records to the AI content service. Avoid including customer data, secrets or sensitive personal information in prompts. Generated text may be stored when you save it as a post.
The public site loads Microsoft Clarity (interaction analytics, click maps and session replay) and Google Tag Manager (GTM). These services can process online identifiers, device/browser information, page URLs and interactions. GTM is a container; the data collected also depends on the tags configured in it. Hosting and request logs may include IP addresses and other request details. Contact enquiries include information you choose to send. These services should not be assumed to produce only anonymous data.
We use data to authenticate stores, manage subscriptions and quotas, create and redirect links, publish authorised content, retrieve engagement statistics, provide requested AI drafts, measure conversions, answer support enquiries, maintain security and understand use of our public website.
For our controller activities, applicable legal bases include performance of our contract, legitimate interests in operating and securing the service, legal obligations, and consent where required for optional analytics or communications. When we act as processor, the merchant determines the lawful basis, provides notices and obtains any required consent for tracking. A merchant's use of Postli does not itself establish a lawful basis for shopper tracking.
We do not sell shopper personal data or use it to train our own AI models. We do not add shopper conversion records to advertising audiences. Third-party providers' own processing is described in their policies.
Authorised personnel and service providers may access data as needed to operate and support Postli. We may disclose information where legally required, to address fraud or abuse, or in a business transfer subject to appropriate confidentiality and privacy protections. The DPA describes sub-processor authorisation for merchant-controlled data; social platforms are also subject to the merchant's own agreements.
Available connections depend on platform approval, account type and your plan. We request permissions to identify accounts, select pages/boards/organisations, publish posts and comments, refresh access and retrieve available engagement or account statistics:
threads_basic, threads_content_publish, threads_manage_insights.tweet.read, tweet.write, users.read, offline.access.youtube.upload and youtube.readonly.boards:read, boards:write, pins:read, pins:write, user_accounts:read.business.manage.You can disconnect an account in Postli to mark the connection inactive. Disconnecting does not immediately erase its stored tokens or remove posts already published. Revoke Postli's access in the platform's own settings to invalidate authorisation, and contact us for deletion of stored connection data. Deletion in Postli does not delete copies held by a social platform.
Use of YouTube features is also subject to the YouTube Terms of Service and Google Privacy Policy. You can revoke Google access at Google account permissions.
| Item | Purpose | Duration |
|---|---|---|
_pl_click | Short-link click attribution | 7 days by default |
_pl_id | Remember a Postli click on a merchant storefront and associate leads/checkouts | 90 days by default; settings may vary |
_pl_lead:… session storage and cart attribution attributes | Deduplicate lead events and carry click information to checkout | Browser session or cart lifecycle |
| Application session and CSRF cookies; Shopify session tokens | Authentication and request security | Session or configured expiry |
postli-theme local storage | Remember public-site theme | Until cleared |
Clarity cookies, including _clck and _clsk | Marketing-site analytics and session association | Typically 1 year and 1 day, respectively |
| Cookies from tags configured in GTM | Depends on the enabled tag | Depends on provider/configuration |
Cookie lifetime is separate from the attribution reporting window. Merchants control their storefront notices and consent setup; the Shopify web pixel declares analytics processing. You can block or clear cookies/storage using your browser and adjust the store's privacy choices where offered; this can reduce attribution accuracy. Browser controls do not necessarily stop every request. Microsoft describes Clarity's cookies in its cookie documentation. We do not promise that enabling Do Not Track alone disables every analytics service.
We retain merchant app records while needed to provide the installed service, subject to deletion requests and applicable legal duties. There is no blanket 30-day expiry for active-account clicks, posts or conversion history. Request an export before uninstalling; contact us for records not available through the app.
Shopify's app/uninstalled event ends the installation. Full shop erasure is handled by shop/redact, which Shopify ordinarily sends no earlier than 48 hours after uninstall (and may withhold if the app is reinstalled). The handler removes the shop record and related links, clicks, posts, social accounts, conversion/attribution records, products, media records and stored media files. Uninstalling does not instantly erase all records.
The customers/data_request handler identifies matching conversion events and returns event details. The customers/redact handler clears matching customer emails and external identifiers in conversion records; it does not automatically erase every associated click or aggregate. Merchants should contact us if a request requires additional access, return or erasure. Logs, backups and records required for security, legal or accounting purposes may have separate retention; we restrict their use and provide details on request. Published social content remains subject to each platform's deletion controls.
Application controls include Shopify session-token verification, shop-scoped access checks, encrypted social access/refresh token fields, authenticated compliance webhook handling, and hashed IPs in click records. We use HTTPS for service connections and restrict access to data needed to operate the service. Hashes, access controls and encryption reduce risk; they do not make data anonymous or guarantee security. If we become aware of a personal-data breach affecting merchant-controlled data, we will notify the affected merchant without undue delay and provide available information under the DPA.
Depending on applicable law, you may request access, correction, deletion, portability or restriction, object to processing, withdraw consent, and complain to a supervisory authority. California residents may also have rights to know, correct and delete personal information, opt out of sale/sharing where applicable, and receive equal treatment when exercising rights. We do not sell personal information or share shopper records for cross-context behavioural advertising.
Email awesomesoft.io@gmail.com. We may verify your identity and authority and respond within the time required by applicable law. Shoppers should contact the merchant whose store they visited; we assist that merchant as processor. Where we independently control your data, contact us directly.
Our app and database are hosted on Vultr in Piscataway, New Jersey, United States. Service administration and support may involve access from Bangladesh. Vercel, Anthropic, Shopify and connected platforms may process data in other countries under their respective arrangements. Postli does not promise EU-only data residency.
Where a restricted international transfer requires safeguards, the parties must put the appropriate transfer mechanism in place, including completed standard contractual clauses or a UK addendum where applicable. This policy and the DPA do not themselves constitute completed transfer clauses. Contact us before transferring data if your requirements depend on a particular transfer mechanism or location.
Postli is a business service intended for adult merchants, not a service directed at children. Merchants must not intentionally submit children's personal data or sensitive-category information through Postli. Contact us if you believe such information was provided inappropriately.
We update this policy when our practices or legal requirements change and revise the date above. We will provide notice of material changes through appropriate service or account channels where required by law. Changes do not retrospectively remove rights or consent requirements.
For privacy, security, data requests and support, contact AwesomeSoft at awesomesoft.io@gmail.com. Please identify the shop or link involved and avoid sending passwords or access tokens. Email us for our current postal contact details. See also our DPA and Terms of Service DPA.