Privacy Policy
Seedr, last updated: November 14, 2026
1. Introduction
This Privacy Policy describes how INFLUXX IO LLC (“we,” “us,” or “our”) collects, uses, stores, and protects information through Seedr (“the App”), available on the Shopify App Store. By installing or using the App, you (“Merchant”) agree to the practices described in this policy.
Seedr is a Shopify application that runs a merchant’s creator program inside Shopify. This policy covers data practices for both merchants who install the App and creators who take part in merchant programs.
2. Information we collect
2.1 Merchant data (collected via Shopify)
When you install Seedr, we access the following data through Shopify’s API with your explicit consent:
- Store information: Shop name, domain, email, currency and storefront domain, and your Shopify access token
- Order data: Order and line item IDs, order number, totals, currency, dates, discount codes, order tags, the App’s own attribution attributes on the order, and Shopify’s customer ID for the buyer together with whether they had ordered from you before. This is what attribution and commission arithmetic need. The order note and any other cart attribute a customer typed are not kept.
- Product data: Product IDs, titles and prices, read when you pick products to send or to set a product-level rate
- Discount data: The discount codes the App creates for your creators
We do not store your customers’ names, email addresses,
phone numbers or postal addresses. The App has Shopify’s customer ID and
nothing else that identifies a buyer, which is all attribution needs.
2.2 Creator data (collected via the creator portal)
When creators sign up through a merchant’s portal, or a merchant adds them, we collect:
- Account information: Name, email address, and a password stored only as a bcrypt hash
- Payment information: The PayPal email address the creator gives at signup and can change in the portal, and any payout details the merchant records, so the merchant knows where to send the money
- Shipping address: A creator’s shipping address is stored when they enter it on their dashboard or the merchant enters it on the creator’s page, through an import, or by saving it from a send. It is used only to send the creator product, and the creator can change or clear it on their dashboard.
- Signup answers: When a merchant adds extra questions to a group’s signup page, the creator’s answers, kept on the creator and shown to the merchant on the creator’s page
- Activity data: Referral link clicks, attributed orders, commission history
- The merchant’s note: A private note the merchant can write against a creator. It is shown to the merchant only and is never displayed in the creator’s portal.
2.3 Tracking data
To attribute sales to creators, the App collects:
- Referral cookies: First-party cookies set on the store’s own domain when a customer arrives on a creator’s link (duration set by the merchant, 30 days by default)
- UTM parameters: Campaign tracking parameters from referral URLs
- A visitor identifier: A random value generated by the App and stored in a first-party cookie. It identifies a browser so a click can be matched to a later order. It is not derived from anything about the person, and it is not linked to a name, an email address or a Shopify customer record.
- Shopify’s own identifier for the browser: The client ID Shopify gives the App’s web pixel for the same browser. It is kept on the click record beside the visitor identifier, so a click reported twice, once by the web pixel and once by the app embed, is counted once, and it stands in for the visitor identifier when the web pixel cannot read the App’s cookie. It is not linked to a name, an email address or a Shopify customer record by the App.
- A page view identifier: A random value the App makes when a visitor who allows analytics opens a link that carries a referral code. It is kept on the click record so a click reported twice, once by the web pixel and once by the app embed, is counted once. It names one page view, and it is made only once the visitor allows analytics.
- Landing page and referring URLs: The page a referred customer first visited, and the site they arrived from
The App does not collect or store IP addresses, browser
user agents, device fingerprints, or any customer name, email address,
phone number or postal address. The tracking runs as a Shopify Web Pixel
and as an app embed in the store’s theme, both on the store’s own
domain. The app embed records a click only when the visitor allows
analytics, the same permission the web pixel asks Shopify for. The
creator portal loads nothing from a third-party server: its font is served from our own domain rather than
from a font provider. The one exception is reCAPTCHA, which loads
Google’s script on the creator signup form, and only if the merchant has
switched it on with their own keys. See section 4.
2.4 Technical data
- Session data: Shopify OAuth access and refresh tokens, so the App can read your orders while you are not looking at it, and a signed cookie holding the identifier of the signed-in creator
- Webhook receipts: A record that Shopify delivered something, narrowed to the fields listed under 2.1. See retention in section 6.
IP addresses are used in memory to rate limit requests and are not
written down. Application logs record what happened and which store it
happened to, not who was buying.
3. How we use your information
We use collected information to:
- Operate the App: Track referrals, calculate commissions, record payouts, manage creator accounts
- Count each click once: Recognize the same browser, so one visit to a referral link is not counted more than once and a click can be matched to the order it led to
- Send notifications: A welcome email when a creator signs up or is added, an email when the merchant approves a creator who signed up, a password reset link when one is asked for, a notice when the PayPal email on a creator account is changed, and a note to a creator when they earn a commission
- Email the merchant about the App: The App emails the store’s contact address about the store’s own creator program, such as a creator applying or commissions becoming ready, and about setting the App up. Every one of those emails carries an unsubscribe link, and the merchant can turn each of them off in Settings.
- Provide support: Diagnose issues and respond to support requests
We do not:
- Sell personal data to third parties
- Use merchant or creator data for advertising
- Share data between different merchants’ creator programs
- Access data beyond what the approved Shopify API scopes allow
- Run any analytics, tracking or telemetry on our own screens
4. Data sharing
These are every party that receives data, and what each one gets:
- Between a merchant and their creators: Merchants can see their creators’ performance. A creator can see their own clicks, commissions and payouts for that merchant, and nothing about anybody else.
- Render: Our hosting provider. The App and its PostgreSQL database run on Render in the United States, so Render holds everything described above as part of running them.
- Resend: Our email provider. Resend receives the recipient’s email address and the contents of the message whenever the App emails a creator.
- Sentry: Our error monitoring. When something in the App fails, our server sends Sentry the error, the store’s Shopify domain and which part of the App failed. In the merchant’s admin, the browser also sends errors, with the path of the admin page they happened on (for example /app/settings) and never its query string. Before anything is sent we remove request details, user details and session tokens. The creator portal and public pages load nothing from Sentry in the browser.
- Crisp: The live chat in the merchant’s admin, run by Crisp IM SAS in France, which stores chat data in the European Union. The chat loads on each page of the merchant’s admin, and each time it does Crisp receives the store’s Shopify domain, its store name and its Seedr plan, along with an identifier the App derives from the store so the conversation is still there on the next visit. When the store has a contact email in its Shopify settings, Crisp also receives the store’s contact email, so our replies can reach the merchant, and no other address. Crisp also receives the messages a merchant sends us through the chat. The chat runs in the merchant’s browser, so Crisp also receives what any website receives from a browser that loads it, such as its IP address, and the address of the admin page it is open on; we take Shopify’s session token out of that address before the chat loads. Nothing about creators, customers or orders is sent to Crisp. The creator portal and public pages load nothing from Crisp.
- Google: reCAPTCHA, and only on a store whose merchant has switched it on in Settings with their own keys. It runs on the creator signup form and Google receives what reCAPTCHA collects about that browser. No merchant or creator record is sent to Google. Separately, when a merchant has set up Google Places on their own account, the Send product form in the merchant’s admin suggests addresses as the merchant types: Google receives the characters typed into the Address field, the chosen country and the suggestion picked, from the merchant’s browser, and nothing about who the parcel is for. Without that setup the App loads nothing else from Google.
- PayPal: No longer used. An earlier version of the App could send payout batches through PayPal, and PayPal received the creator’s PayPal email address and the amount. That was switched off, and the App now sends nothing to PayPal at all. If your store saved PayPal credentials while it worked, they are still in our database, read by nothing; write to support@getseedr.app and we will clear them.
- Legal Requirements: We may disclose data if required by law, court order, or governmental regulation.
5. Data storage and security
- Storage location: One PostgreSQL database, managed by Render, in their Oregon region in the United States.
- Encryption: In transit over TLS, and at rest by Render, who encrypt their managed database volumes.
- Access controls: The database is reachable only by the App’s own service over Render’s private network.
- Password hashing: Creator passwords are stored as bcrypt hashes. We cannot read them, and neither can the merchant.
- Separation between stores: Every query the App makes is scoped to one store’s id, and a signed-in creator’s session is checked against the store whose portal they are on.
- Session management: Shopify OAuth tokens are held in the database and refreshed as Shopify requires. The creator portal’s cookie is signed and http-only, so it cannot be read or forged by a script, and resetting a password signs out every device that was already signed in.
6. Data retention
Every window below is enforced by a job that runs every night, not by a person remembering.
- Merchant and creator data: Kept while the App is installed. When a merchant uninstalls, everything belonging to that store is deleted 30 days later: creators, their codes and payout details, the commission history, the webhook receipts and the App’s copy of the Shopify access token. Reinstalling inside those 30 days restores it; after that it is gone and cannot be recovered. A merchant can also delete an individual creator at any time.
- Click records: Deleted once both conditions hold: the referral window set by the merchant has closed, and the click is at least 90 days old. The 90-day floor exists because the merchant’s reporting covers the last 30 days and a shorter cookie duration would otherwise make yesterday’s figures shrink. A click record holds the referral code, a random visitor identifier, Shopify’s own identifier for the browser when the web pixel reported one, an identifier for the page view, the landing page, the referring URL and any UTM parameters. It holds no IP address and no user agent.
- Webhook receipts: Kept 7 days when the App handled the delivery, and 30 days when it failed or was refused, so a failure can be looked into. Both outlast Shopify’s own retry window. For a store with no creators, a handled delivery keeps no order fields at all, only what arrived and when. Otherwise a receipt keeps only the fields the App reads: order and line item IDs, order number, amounts, currency, dates, discount codes, tags, the App’s own attribution attributes, and Shopify’s customer ID with whether that customer had ordered before. The shopper’s name, email address, phone number, shipping address and billing address are dropped before the receipt is written, and so are the order note and every cart attribute the shopper typed, so nothing a shopper wrote at checkout is stored at all.
- Tracking cookies: Expire on the merchant’s configured referral window, 30 days by default, except
affhub_pl, which lasts 30 minutes. They live in the visitor’s own browser and we cannot delete them; clearing cookies removes them.
7. Your rights
For merchants (data controllers):
- Access: View all data the App stores via the admin interface
- Export: Export creator lists, commission reports, and payout history as CSV
- Deletion: Uninstall the App to trigger data deletion; or contact us for immediate deletion
- Portability: Request a full data export in machine-readable format
For creators (data subjects):
- Access: View your data through the portal dashboard
- Correction: Change the PayPal email on your account in the portal at any time, and ask the merchant to correct anything else
- Deletion: Request account deletion through the merchant or by contacting us directly
- Email: The App sends you a welcome message, an email when the merchant approves you, a reset link when you ask for one, a notice when the PayPal email on your account is changed, and a note when you earn a commission. It sends no marketing, so there is nothing to unsubscribe from; ask the merchant to remove your account and it stops.
For EU/EEA residents (GDPR):
In addition to the above, you have the right to:
- Lodge a complaint with your local data protection authority
- Withdraw consent at any time (without affecting prior lawful processing)
- Request restriction of processing
To exercise any rights, contact us at support@getseedr.app.
8. International data transfers
Data is processed in the United States, except what the live chat in the merchant’s admin sends Crisp (section 4), which Crisp stores in the European Union. For EU/EEA users, transfers are conducted under Standard Contractual Clauses (SCCs) as approved by the European Commission, ensuring adequate data protection.
9. Children's privacy
Seedr is not intended for use by individuals under 18. We do not knowingly collect personal information from children. If we become aware that we have collected data from a child, we will delete it promptly.
10. Cookies
| Cookie | Purpose | Duration |
affhub_ref | The creator code the visitor arrived on, so a later order can be attributed | The merchant’s referral window, 30 days by default |
affhub_vid | A random identifier for the browser, so one click is not counted many times | The merchant’s referral window, 30 days by default |
affhub_pl | A random identifier for one page view of a link that carries a referral code, with that code, so the two reports of that page view are counted as one click. Set only once the visitor allows analytics | 30 minutes |
__portal_session | Keeps a creator signed in to the portal. Signed and http-only. | 30 days |
Crisp chat cookies, names beginning crisp-client | Keep the merchant’s support chat and its messages between visits. Set by Crisp, in the merchant’s admin only | 6 months, renewed each time the chat loads |
| Shopify session cookies | Authenticate merchant sessions in the Shopify admin | Set by Shopify |
The first three are first-party cookies on the merchant’s own storefront
domain. Crisp’s cookies are set only in the merchant’s admin, and
Crisp states they are not used for tracking. No third-party tracking
cookies are used, and the App sets no
cookie for advertising.
11. Changes to this policy
We may update this Privacy Policy from time to time. Material changes will be communicated via the App’s admin interface and/or email. Continued use of the App after changes constitutes acceptance.
12. Contact us
For privacy-related questions or requests:
For Shopify-specific data questions, contact Shopify at privacy@shopify.com.