Reklis is a companion extension for Rekzon, an applicant tracking system (ATS). It lets a signed-in Rekzon user capture a LinkedIn profile they are actively viewing and save it as a candidate in their own Rekzon hiring pipeline. This policy explains exactly what data Reklis handles, why, and who it is shared with.
Reklis has one purpose: to copy a LinkedIn profile that the user opens into the user’s own Rekzon candidate database, on the user’s explicit action. Reklis does not run on any site other than LinkedIn and does nothing until the user clicks Capture (or the matching right-click menu item).
| Category | What it includes | Why |
|---|---|---|
| Personally identifiable information | Candidate details read from the LinkedIn profile: name, email address and phone number (only if the profile displays them), LinkedIn profile URL, job title, employer, location, work history, education, and profile summary. Also the signed-in recruiter’s own name and email from their Rekzon account. | To create the candidate record in the user’s Rekzon pipeline. |
| Authentication information | The Rekzon login session (access and refresh tokens) issued to the user when they connect the extension from the Rekzon web app. Stored locally in the browser only. | To securely save candidates to the correct Rekzon workspace as the signed-in user. |
| Website content | Text read from the LinkedIn profile page the user is actively viewing at the moment they trigger a capture. | This is the source of the candidate details above. |
Reklis does not collect your browsing history, your device location or GPS, financial or payment information, health information, personal communications, or keystrokes, and it does not track your activity across websites.
Captured data is used only to operate the feature described above. We share data with the following service providers strictly to provide the service:
| Recipient | Purpose |
|---|---|
| Supabase (the Rekzon backend) | Hosts the user’s Rekzon workspace database and authentication. Captured candidates and the user’s login session are sent here over HTTPS. Access is restricted per-organization by row-level security. |
| Google (Gemini API) | Selected candidate text fields (name, title, employer, location, skills, and summary) are sent to Google’s Gemini API to automatically suggest which department the candidate fits. No login credentials are sent. |
We do not sell your data, share it with advertisers, or transfer it to any party for purposes unrelated to Reklis’s single purpose. We do not use the data to determine creditworthiness or for lending.
The login session and a few small preferences (such as your default job and your daily capture
counter) are stored locally in your browser using chrome.storage.local. Captured
candidate records are stored in your organization’s Rekzon workspace. All network traffic uses
HTTPS.
The Rekzon customer organization (the recruiter and their employer) is the controller of the candidate data captured with Reklis and is responsible for having a lawful basis to process it. Reklis processes that data on the organization’s behalf. Users are expected to use Reklis in compliance with applicable laws and with LinkedIn’s terms.
Captured candidates remain in your Rekzon workspace until you delete them there. Your local session is removed when you click “Disconnect” in the extension or sign out of Rekzon. To request access to, or deletion of, data associated with your account, email support@rekzon.com.
We may update this policy as the product evolves. Material changes will be reflected by updating the effective date above.