Who we are
LinkRunway is operated by Kimeur Labs, LLC, 4848 Lemmon Ave STE 420, Dallas, TX 75219, United States. Contact us at support@linkrunway.com. We do not sell personal information, and we do not use it for our own advertising.
This policy covers linkrunway.com, the LinkRunway console and partner portal, and the links, SDKs, and API that our customers use.
Two kinds of data
Some information is about you as our visitor, customer, or partner contact. We decide how it is used, and this policy describes that.
Other information is collected by businesses that use LinkRunway to measure their own links and apps, for example when you open one of their links. That business decides what is collected and why, and its privacy notice applies. We process the data only to provide the service to that business. If you have a request about it, contact the business. If you write to us instead, we will pass your request on.
Your account
When you create an account, we store your name, your email address, and a salted scrypt hash of your password, never the password itself. We also store the workspaces you belong to, your role in each, and what you create there, such as links, domains, settings, and API keys. API keys and sign-in tokens are stored only as hashes.
A session is a hashed token that expires after seven days. We do not store your IP address, device, or location with your account, your sessions, or the audit log. If you turn on two-step verification, your authenticator key is stored encrypted and your recovery codes are stored as hashes. If your organization uses single sign-on, its identity provider sends us your name, email address, and an account identifier.
To limit abuse and password guessing, we use your IP address when a request arrives. The address itself is not stored: short-lived counters keep a one-way digest of it for up to about a day.
We keep an audit log of changes made in a workspace: the account that made the change, what it was, and when. Our team can see account and workspace records when that is needed to run the service, investigate abuse, or answer a support request.
Payments
Stripe processes payments on its own checkout and billing pages. You give your email address, card details, and any billing address or tax ID directly to Stripe. We never receive or store card numbers. We send Stripe your workspace’s identifier, and we store the Stripe customer and subscription identifiers, your plan, the subscription’s status, and its renewal or cancellation date. If you fund a partner payout through Stripe, we also pass it your account email address so that checkout is filled in for you.
Purchase records may need to remain with Stripe for accounting, dispute handling, and its legal obligations. See Stripe’s privacy policy.
Partners
If a business adds you to its partner program, it gives us your name and email address, and we record your links, clicks, commissions, and payouts in that program. You sign in to the partner portal with a link emailed to that address. There is no password.
In the portal you can give that business a tax profile: your legal name, country, entity type, tax form type, and tax identifier. The identifier is stored encrypted, and only its last four characters are ever shown. LinkRunway does not check it with a tax authority and does not file tax forms.
If the business pays through Stripe, we create a Stripe account for you with your email address, name, country, and entity type, and you finish setting it up on Stripe’s own pages. Stripe collects the identity and bank details it requires. We do not receive them. We store the account’s identifier and whether it can be paid.
Plan requests, support, and email
When you send a plan request from our pricing page, we store your name, work email address, company, the plan you asked about, your message, and when you agreed to be contacted, so that our team can reply.
When you email us, your message and our replies are kept in our access-controlled support inbox, hosted on Cloudflare, and forwarded to our team’s mailbox at Google so that we can respond. Please do not send passwords, API keys, or card details.
We send account email only: address verification, password resets, invitations, security notices, partner sign-in links, and alerts you set up. Messages are plain text with no tracking pixels. We keep a record of each one (recipient, subject, and delivery status) and clear its text once it has been sent. We do not send marketing email.
This website and the console
Our website keeps your privacy choice in your browser so that it does not ask again. Optional analytics starts only if you choose Allow analytics. We then use Google Analytics to count visits and see which pages are useful, with advertising storage and advertising signals turned off. Google keeps this event data for 14 months. You can change your choice at any time with Cookie settings in the footer, and rejecting removes the Analytics cookies. A Global Privacy Control or Do Not Track signal counts as a refusal.
We also measure how quickly pages load. A measurement holds the metric, the page path, and whether the device is a phone, tablet, or desktop. It carries no cookie or visitor identifier, and it is not sent if you rejected analytics or your browser sends a privacy signal.
If a page fails, the website or the console sends an error report to Sentry. A report holds the error, the page address without its query string, and your browser’s user agent. Cookies, request bodies, and account details are removed first, email addresses in messages are masked, and our Sentry organization is set not to store IP addresses.
The console loads one typeface from Fontshare’s servers, which receive your IP address and browser details when your browser requests it. The console uses no analytics.
What our customers collect with LinkRunway
When someone opens a LinkRunway link, we record the time, the link, the site they came from, the kind of device, operating system, and browser, the browser’s language, campaign parameters and advertising click identifiers in the link, and, when our network provider supplies it, the country. We do not store the IP address or the full user agent. We keep a keyed hash of the two that changes every day, to estimate unique visitors and to spot abuse. The redirect sets no cookie. It adds a signed click token to the destination address so that the business’s site or app can connect what happens next to the click.
If the browser sends a Global Privacy Control or Do Not Track signal, the visit is still counted, but without the hash, without advertising click identifiers, and without a click token, and it is never used for attribution.
A business’s app or server can send events such as an install, an app open, a sign-up, or a purchase, together with the identifier that business uses for its customer and any details it chooses to attach. Our SDKs send nothing until the app records the person’s consent, and they do not read advertising identifiers. On a website, the SDK keeps its state in the browser’s local storage on that business’s own site and removes it when consent is withdrawn.
A business can give us a customer’s email address or phone number to build advertising audiences. We store only hashes of them, and only while the business tells us the person agreed to advertising use. If a business turns on probabilistic or view-through matching, we also keep a keyed hash of the network address, for at most seven days, to connect an app install to a click or an ad view.
A business can send this data on to services it connects, such as its ad platforms, analytics tools, and webhooks. They receive it on that business’s instructions, not ours. In our built-in ad platform integrations, a conversion can carry the click identifier that platform put in the link. Customer identifiers are sent only as hashes, and only for people the business says agreed to advertising use.
A workspace owner can export or erase what LinkRunway holds about one of their customers and, on plans that include retention controls, set how long clicks and events are kept.
How we use information
We use the information above to provide and secure LinkRunway, to bill for it, to answer you, to prevent abuse, and, with your permission, to understand how our website is used. Where the GDPR applies, we rely on our contract with you, our legitimate interest in running a secure service, your consent for optional analytics, and our legal obligations.
We use the data our customers collect only to provide, secure, and troubleshoot the service for them. We disclose information to others only as this policy describes, on your instructions, or when the law requires it.
Service providers and where data is processed
We use these providers to run LinkRunway, and share with each only what it needs: Railway hosts our API and database in the United States (US West); Vercel hosts our website and the console; Cloudflare provides DNS, sends our account email, and hosts our support inbox; Stripe processes payments and payouts; Sentry receives error reports; and Google provides website analytics, if you allow it, and our team’s mailbox.
Your information is processed in the United States.
How long we keep data
We keep your account and workspace records, including the audit log, for as long as the account or workspace exists. Sessions expire after seven days, and sign-in, verification, and invitation links are deleted a week after they expire.
Records of the email we send and other delivery logs are deleted after 180 days, unless a workspace owner chooses a different period. Clicks and events are kept until the workspace owner’s retention setting removes them. Revenue, commission, and payout records are kept as accounting records.
Our database backups expire on a rolling schedule: daily backups after 6 days, weekly backups after 27 days, and monthly backups after 89 days. Deleted data is therefore gone from every backup within 89 days.
Plan requests and support messages are kept while we need them to help you and for our records. Ask us and we will delete them.
Your choices and rights
In the console you can reset your password, turn two-step verification on or off, end your other sessions, and leave a workspace you do not own. To change your name or email address, close your account, or delete a workspace, write to support@linkrunway.com.
You can ask us to access, correct, export, or delete your personal information, or to stop using it, and exercise the rights you have under laws such as the GDPR or California privacy law. Email support@linkrunway.com. We may need to verify your identity, and we respond within 30 days.
If your request is about data that a business collected with LinkRunway, we will pass it to that business, which decides how to answer.
Security
Passwords are hashed with scrypt. Session tokens, sign-in links, and API keys are stored only as hashes. Authenticator keys, integration credentials, and tax identifiers are encrypted. Connections use TLS. No system is perfectly secure: if you think your account has been misused, tell us at support@linkrunway.com.
Children
LinkRunway is a service for businesses. It is not directed to children, and we do not knowingly collect personal information from anyone under 16.
Changes to this policy
We will post any changes here and update the effective date. If a change is significant, we will tell you by email or in the console before it takes effect.