Last updated 26 October 2026
This policy says what Nowhere Lab. LLC, operator of Namesworn, collects, why, and what you can ask us to do about it. It describes what the platform actually stores today, not what a platform of this kind could store.
Nowhere Lab. LLC, 30 N Gould St, STE R, Sheridan, WY 82801, United States, is the controller of the personal data described here. Privacy requests: [email protected].
For visitors to a Business’s own website, that Business is the controller of what happens on its site, including the attribution cookie described in section 5. We are its processor for the events that reach us.
For the customers of a Business described in section 4, we are a controller in our own right: we decide what we read about them, and we use it for our own purposes, to certify the Conversions we sell and to detect abuse across Namesworn.
When someone clicks a Promoter’s link, we record a Funnel Event: which link, what kind of event, when, and the page that referred it.
That record holds no name, no email address and no account of the visitor. The IP address and the user agent of the request are stored only as keyed hashes — computed with a secret key we hold — and the raw values are never written anywhere. A keyed hash cannot be turned back into the address it came from, but it is the same value every time for the same visitor, and we hold the key that produces it: it is data about a person, pseudonymous rather than anonymous, and we treat it as such.
The hashes exist for one purpose: detecting abuse — bot traffic, click floods, clusters that do not look like people. They are never shown in any dashboard, to a Business or to a Promoter, and they are not used to profile anyone or to target advertising. That includes checking the clicks behind a purchase later made in an app.
The referring page is stored as the browser sends it, because checking that a promotion carried its disclosure means being able to look at the page it was posted on. Most browsers send only the site it came from, but a full address including its path and query string is possible, and such an address can carry personal data put there by whoever wrote the link. We do not use it for anything but attribution and abuse checks, and it is deleted with the Funnel Event it belongs to. A click that arrives with no referring page at all — which is what a message forwarded privately looks like — is ordinary and blocks nothing.
If the Business has declared the Android app of its Product, a click from an Android device may be sent to the app’s page on Google Play, with the tracking code in the address. Google then receives the code of the link, which says nothing about the visitor.
When a customer referred through a tracking link pays a Business, we read that payment from the provider the Business connected for its Product, with the key it gave us. That customer gave their data to the Business, not to us, which is why we say here where it comes from.
We store the customer’s identity and the card fingerprint only as keyed hashes, like those in section 3, to count each customer once per Campaign and to detect abuse, such as a Promoter buying through their own link or one card paying for several Promoters. We compare the email address with the Promoter’s own and do not store it. The hashes are kept with the Conversion they belong to, under section 9. The one time we hold an app user id in a form that is not a hash is the wait for RevenueCat to confirm an event, which section 9 describes.
On Namesworn itself we set one cookie: the session cookie that keeps you signed in. There is no advertising cookie and no third-party analytics on our own pages.
On a Business’s own website, our optional snippet stores the attribution reference from the link the visitor arrived through in a first-party cookie on that site’s domain, for up to 30 days. It holds the tracking code and nothing else — no identifier of the person, no browsing history — and for a visitor who did not arrive through a tracking link the snippet does nothing at all and sends no request.
That cookie sits on the Business’s own site, under the Business’s own control, which is why obtaining whatever consent the law of its market requires is the Business’s responsibility and not ours. A Business that installs the snippet is making that choice.
A report filed through our abuse channel stores what was reported, the category chosen, the account of what happened, and an email address if the reporter chose to leave one so we can come back with a question. Leaving one is optional and reporting does not require an account.
We do not sell personal data, and we do not share it for advertising.
Account and transaction records are kept while your account exists and afterwards for as long as tax and accounting law requires. Funnel Events and the hashes attached to them are kept while they can still matter to a Reward or to an abuse decision, and then deleted. An abuse report is kept for as long as the conduct it describes can still bear on a decision — its own and any later one about the same account — and no longer than the account it concerns.
The events RevenueCat sends us about a Business’s customers, whatever their kind, are kept for 60 days and then deleted, unless the event became a Conversion, which stays with it as the paragraph above says. An event keeps only what section 4 lists. While it waits for RevenueCat to confirm it, we also hold the customer’s app user id and its aliases, encrypted, because we have to name the customer to ask; we delete them as soon as the event is settled, and from then on the customer is known to us only by the keyed hash held with a Conversion.
You can ask for a copy of what we hold about you, ask us to correct it, ask us to delete it where we are not required to keep it, and object to our use of it. Write to [email protected] and we will answer within a month.
If you are in the European Economic Area or the United Kingdom, you can also raise it with your own data protection authority.
For the hashed values in section 3 we hold nothing that says which of them are yours: they are keyed hashes, not records in your name. Tell us the IP address or the user agent you used and roughly when, and we can compute the hash and look — we may have to ask for enough to be sure the request is really yours, and we can only search what we still hold under section 9.
The same holds for the hashes in section 4: tell us which Business you paid, the email address you paid with and roughly when, and we can look.
We will update this policy when what we collect changes, and we will say so by email at least 30 days before a material change takes effect.