Privacy

The short version

Coming soon. The LinkedIn lookup isn't available yet. Until it is, nothing leaves your computer through ARTie, and you can bring in your LinkedIn history with theLinkedIn data export. This page says how the lookup will handle your data when it arrives.

ARTie runs on your computer, and your resume, your knowledge graph and your tailored versions stay there. The one exception is the LinkedIn lookup, which you can skip. When you give ARTie your LinkedIn URL, a small service run by ARTie asks a data provider for that profile and passes it straight back to you. The service keeps counters, not profiles.

Last updated October 2026.

What passes through the lookup service

Each lookup sends three things through the service, and the service handles them only for as long as the request lasts:

• Your LinkedIn profile URL. Only addresses of the formlinkedin.com/in/your-name are accepted. Anything else is refused.
• A GitHub token from art github login. The service sends it to GitHub to learn your numeric GitHub user id, so it knows whose daily limit to use. GitHub's answer also includes your public profile details; the service uses only the user id, keeps none of the rest, and does not store the token.
• The profile the data provider returns. The service hands it back to you and doesn't keep a copy.

The service never writes the URL, the token or the profile to its logs, and it adds no analytics or tracking. It also sees the network address your request comes from, which it uses for one thing: slowing down a single address that sends too many requests.

What is kept, and for how long

Counters are all the service keeps. They are stored under keys that carry no profile text, and each one expires on its own:

• A daily count per GitHub user id. It holds a number and the date, and expires about two days after its last use.
• A rate-limit count per network address, stored as a one-way hash rather than the address. It expires after two minutes.
• A monthly count of lookups across everyone, which is how the service stops before its budget runs out. It carries no user id and expires after about six weeks.
• A five-minute memory of a token check, stored under a hash of the token and holding your GitHub user id, so a burst of requests doesn't ask GitHub every time.

The service keeps no account for you, no profile data, no URLs and no tokens after the response is sent. Deleting the counters needs nothing from you: they expire by themselves.

Who else sees it

• GitHub receives your token to confirm who you are, the same as any app you sign in to with GitHub.
• Bright Data, the data provider, receives the LinkedIn URL and returns the profile. Its own terms and privacy notice apply to what it does on its side.
• Vercel hosts the service and keeps its standard request records for a short time (the path, the status and the time of each request). ARTie adds no request bodies to them.

Fetch your own profile only

The LinkedIn data export instead

The LinkedIn data export is always an alternative, and ARTie supports it fully. Request the archive from LinkedIn's own settings, then give your agent the file when you run setup. That route doesn't touch the lookup service, and it needs no GitHub login.The usage page shows how.

Limits

The lookup is small by design. Each GitHub user gets a few profiles per day, one network address can only send so many requests a minute, and the service switches itself off for the rest of the month when its budget is used up. When any of these stops a request, ARTie says so and points you to the export.

Questions

To ask about data the service holds or to report a problem, open an issue inthe project's repository.