Data & privacy

Who operates Siren?

Siren is operated by Novatorius, LLC. Contact Alex Standiford at alex@novatori.us about privacy, processing terms, or a customer security review.

Cloud and WordPress are different deployments

Siren Cloud receives the program and integration data sent to our hosted service. With the self-hosted WordPress plugin, records in the merchant's WordPress database are hosted under that merchant's arrangements. An enabled remote service or integration may receive the information needed for that feature.

Does every integration use cookies?

No. Some integrations use browser cookies or local storage to connect a referral to later activity. Others send server events, partner codes, or existing customer references without a Siren browser cookie. The enabled integration determines the data flow.

Merchants control their own website notices, consent platform, and tracking setup. Where an integration uses optional browser attribution, the merchant is responsible for required notices and permissions and for ensuring that tracking runs only when permitted. The integration must be assessed alongside the merchant's consent setup. Server order processing and financial records are separate from that browser choice.

Choices made through this website's privacy controls apply to this website. They do not change the settings on a merchant's website.

What does the Cloud storefront visit endpoint record?

The Cloud storefront visit request uses a referral code and may include a signed visit token. It does not ask for a visitor's name or email. A visit can create an opportunity with an identifier, status, and timestamps, plus engagement records connecting that opportunity to a program and affiliate.

A merchant's integration may later link that identifier to a customer record or to order references. An identifier is therefore not a promise of anonymity. Information you supply through an enquiry or chat is handled separately. IP addresses may also be processed for security and rate limiting.

What does Siren keep about a merchant's customers?

Siren keeps a customer record only for a shopper who takes part in a merchant's program. That happens when Siren records a sale, renewal, or lead for them, when a referred visitor signs in or registers, or when the merchant links a customer to an affiliate. Siren doesn't copy a store's whole customer list.

A customer record holds the customer ID each store uses for that shopper, such as a WooCommerce or Stripe customer ID, a one-way hash of the shopper's email address, and the name each store reports for them. It links the shopper to their visits, their sales, and any affiliate the merchant has linked them to. It holds no address or phone number.

How does Siren handle email addresses?

Siren stores a one-way hash of the shopper's email address, never the email itself. Each merchant has its own hashing key, so the same address produces a different hash at every merchant. The hash lets a merchant recognize a returning shopper, or find a customer by typing their exact email address, without Siren keeping the address. Because a merchant can look up a shopper this way, Siren treats the hash as personal data.

A WordPress site connected to Siren Cloud hashes the email on the merchant's own server before it sends anything to Siren Cloud. Shopify and Stripe send their events to Siren Cloud directly, and Siren hashes the email as soon as an event arrives. A self-hosted WordPress site that isn't connected to Siren Cloud keeps its customer records, hashes included, in its own database.

Who sees a customer's name?

Only the merchant's team sees it. Siren keeps the name each store reports so the merchant can recognize a customer and judge whether two records belong to the same person. Names stay out of activity notes, webhooks, and logs.

Why does Siren keep customer records?

Customer records let Siren credit the right affiliate for a sale and keep renewals credited. Where a merchant's program pays an affiliate for a customer's later purchases, the record holds the link between that customer and the affiliate. The record also lets Siren recognize a returning customer and point out records that may belong to the same person.

Siren uses customer records only for the merchant's program. It doesn't use them for advertising or for any purpose of its own, and it doesn't share them with affiliates or other merchants.

Can Siren connect a customer's records across stores?

Only within one merchant, and only when the merchant's team chooses to. Siren never combines two customer records on its own. When two records look like the same person, such as the same email hash on two of the merchant's stores, Siren suggests a match and the merchant decides whether to merge them. A merge can be undone.

Suggestions across stores appear only after the account owner confirms that those stores belong to one business. Because each merchant has its own hashing key, Siren can't match a customer across different merchants.

Who controls customer data?

The merchant decides how its customers' data is used. In Siren Cloud, Siren processes customer records on the merchant's behalf and only on its instructions. With the self-hosted WordPress plugin, customer records stay in the merchant's WordPress database unless the merchant connects the site to Siren Cloud.

Novatorius decides how it uses the information in Siren accounts, billing, this website, and our own communications, as our Privacy Policy describes.

What can affiliates see?

The standard affiliate engagement view is limited to that affiliate's own records. It includes opportunity and program identifiers, status, and timestamps; its standard engagement fields do not include a visitor's name, email, or IP address. Merchant administrators have broader access. Custom fields, permissions, and integrations can change what a particular program shares.

Affiliates can't see customer records, so they don't see a customer's name, email hash, or store customer ID.

How long is data kept?

An attribution window determines when a referral can qualify for a reward. It does not itself delete database records, customer mappings, financial evidence, logs, or backups. Browser storage, program records, and operational records have separate lifetimes.

Siren keeps a customer record while the merchant's program needs it to credit sales and linked affiliates, then removes the shopper's store IDs, email hash, and name. A merchant can erase a customer at any time.

Ask us for the retention details that apply to your deployment and intended integrations. A browser cookie's lifetime should not be treated as the retention period for the whole service.

Processing agreements, hosting, and transfers

Contact alex@novatori.us for a review of the processing agreement, hosting providers and locations, subprocessors, and international transfer arrangements for your proposed use. Obtain the applicable completed terms and locations before relying on them for your own privacy assessment.

This page does not assert Data Privacy Framework certification or that a transfer agreement has been executed for a particular customer.

Privacy requests

If your request concerns a merchant's program, such as a store you bought from, contact the merchant, which normally decides how its program data is used. If you contact us instead, we'll pass your request to the merchant. For our own website, account administration, or communications, write to alex@novatori.us. Please do not send passwords, payment-card details, or unnecessary identity documents.

Merchants answer customer requests with Siren's own tools. On WordPress, Siren adds itself to WordPress's Export Personal Data and Erase Personal Data tools. In Siren Cloud, a merchant exports or erases a customer from that customer's page. When a WordPress site is connected to Siren Cloud, erasing a customer in WordPress erases them in Siren Cloud too.

An export lists the customer's store IDs, when Siren first and last saw them, their visits and sales, and whether an affiliate is linked to them. The email appears as a hash that Siren can't reverse. Erasure removes the customer's store IDs, email hash, and name, along with the links between that customer and their visits, sales, and affiliates. The merchant's sales and commission records stay for its accounting, without those links. A linked affiliate stops earning from that customer's future purchases.

See our Privacy Policy for our website notice.