Privacy

Last updated: October 7, 2026

Information RoboRep processes

RoboRep may process account information, phone numbers a user explicitly chooses to dial, SMS contents and delivery events, user-reviewed contact details for CRM integration, calling metadata, dispositions, and optional recordings or transcripts enabled by the customer. The Chrome extension stores its secure workspace origin in Chrome sync storage and up to ten recent normalized phone numbers locally. It does not store Telnyx API keys.

How information is used

Information is used to provide calling, reporting, customer support, security, and requested CRM integrations. RoboRep does not sell personal information.

Extension authentication and communications

The extension sends your email and password to your configured HTTPS RoboRep workspace when you sign in. It clears the password field and keeps a temporary, revocable sign-in token in browser session storage for up to eight hours, along with temporary phone state. If you choose Keep me signed in, a revocable session token is also retained in trusted extension-local storage for up to 30 days of inactivity. No password is retained. Sign out clears the saved token; account disable and password changes invalidate access. The portal offers a corresponding persistent secure login cookie. Calling uses temporary telephony credentials; the extension does not store your Telnyx API key. Call audio and signaling are processed by the configured telephony service, including Telnyx. SMS/MMS recipients, message text, and supplied media URLs are sent through the workspace and telephony service; the provider may retrieve media URLs for delivery. Voicemail, uploaded voicemail recordings, and any enabled call recordings are processed and retained according to the configured services. Authorized manager listen-only sessions are logged.

Browser extension access

Page access is initiated by the user to detect phone numbers on the active page. RoboRep requests only the permissions needed for click-to-call and does not place a call without an explicit user action.

The extension reads the active website URL to offer site access, and processes selected or pasted contact text and user-requested page scans. It does not continuously record browsing history. Reviewed contact fields and source links may be passed to the workspace review page before you choose to save them. Temporary contact handoffs and selected workday/list state use browser session storage. Unsaved drafts and displayed conversations are held in the panel and cleared when the account changes.

The extension keeps release metadata and notification bookkeeping locally. It checks public release metadata periodically and can show update notifications; it does not automatically execute or install downloaded updates. If enabled while signed in, unread-chat checks and notifications operate while Chrome runs. Chat-alert preferences and seen-notification identifiers are stored locally and scoped to the account. The browser phone may remain connected while the panel is closed; closing Chrome ends background operation.

Limited use

RoboRep's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Browser and page information is used only to provide or improve RoboRep's disclosed communication and customer follow-up features.

Contact discovery and saved lists

When you request a current-page contact scan, the extension locally extracts candidate contact blocks for your review. Selected and edited names, job titles, companies, emails, phone numbers, source page URLs and capture dates are sent to your configured RoboRep workspace when you check duplicates or save a list. URL query strings and fragments are removed from saved sources. Saved contact and lead lists remain in the workspace for reuse; they are available to their owner and workspace administrators. Duplicate checks respect your access to existing records. This feature does not use an external enrichment provider, crawl other pages, or verify mailbox deliverability. Closing the panel clears unsaved scan results, but does not delete saved lists.

Calling lists

Signed-in users can retrieve authorized calling lists and prospect details from their RoboRep workspace in the extension. List selections, call requests, outcomes, notes, and callback times are sent to that workspace. List progress is stored on the server. The extension keeps the selected list ID and pause state in browser session storage, scoped to the account; draft notes and displayed contacts are cleared from the panel when the account changes.

Website chat

When you send a website chat message, RoboRep stores the conversation, timestamps, and contact details you provide so authorized team members can respond and follow up. Agents may add internal notes and save reviewed contact details and conversation history in the RoboRep workspace. Chat is not sent to an AI provider. When a chat closes, you can request an emailed copy at the address captured when it closed. An authorized agent may also send the public conversation to the configured website-owner email. Private team notes are excluded from these email transcripts. A secure, HTTP-only browser cookie keeps your conversation available on that browser for 30 days; clearing the cookie does not delete the server-side conversation. Messages can remain available to our team after you leave the site. Avoid sharing passwords, payment details, or sensitive documents in chat.

Optional website analytics

If enabled, Google Analytics loads only after you allow analytics. It measures page visits and selected button clicks; our tracking code excludes contact fields and chat messages. Your choice is stored in this browser. Use Analytics preferences on the home page to change it. Declining stops future tracking from this page but does not remove previously collected data or existing Google cookies.

Recorded voicemail campaigns

When a user creates a campaign, RoboRep saves a snapshot of selected recipient names, phone numbers and source references, the selected recording, consent evidence references, schedules and delivery results. Campaign audio is encrypted using the workspace data-protection keys. Authorized campaign owners can preview audio, send a controlled test, schedule calls, pause or cancel, and suppress a number. The configured telephony service receives destination and callback numbers and a short-lived link to the campaign recording. Campaigns place normal calls and play audio after a detected voicemail beep; ringless delivery is not provided. Incoming callbacks may be associated with the latest attempted campaign recipient using phone numbers and timestamps. This association does not prove that the recipient listened to a voicemail.

Mobile access

When you sign in through the mobile API, RoboRep stores a device identifier, device name, session timestamps and hashed access and refresh tokens in the encrypted workspace. Access tokens expire after 15 minutes; a mobile session lasts up to 30 days and can be revoked through the mobile session controls. Up to five active devices are allowed per account. Revoked and expired session records are removed during subsequent mobile sign-ins. Mobile requests use the same account permissions and workspace records as the website. This API version does not register push-notification tokens, track device location, or provide background incoming-call notifications. Signing out does not delete saved workspace records.

Inquiry source context

When you submit through the RoboRep website chat, we may record the page path, referring website origin and campaign label to help our team understand your inquiry. We do not include URL query strings or fragments in the saved page path, and this feature does not collect an anonymous browsing history.

Work applications

If you apply to work with RoboRep, we collect the details, written exercise and audio sample you choose to submit, plus your consent to application review. Your browser asks for microphone permission before recording; a recording is uploaded only when you submit. Applications and audio are stored encrypted outside the public website and are available to authorized RR administrators for recruitment review and applicant contact. We send an email acknowledgment through our configured email service. If you separately allow WhatsApp recruiting contact, we record your permission wording, timestamp and WhatsApp number so our team can follow up about your application and interview scheduling. No automatic SMS or WhatsApp acknowledgment is sent. Historical SMS consent and delivery records may remain for earlier applications. Applications do not enroll you in marketing. Contact support to request correction or deletion of your application.

Retention and controls

Extension recent-number history is limited to ten entries and can be removed by clearing the extension's data or uninstalling it. Clearing extension data or uninstalling does not delete records held by the workspace or telephony provider. Other retention depends on the customer plan, enabled features, legal requirements, and customer configuration. Customers can request access, correction, export, or deletion through support.

Contact

Privacy questions can be submitted through the RoboRep support page.