Appearance
Security & privacy
This page gathers everything that keeps a Replora installation safe and its visitors' data private: who may do what (installation administrators and the roles inside an account), how sign-in is protected (password rules, two-factor sign-in, Google, reCAPTCHA, rate limits), what API tokens can reach, how visitor data is masked, anonymised and deleted, how people get or delete their own data, and how uploaded files are checked.
Roles
Replora has two independent layers of rights.
Installation administrators
An administrator (is_admin) runs the installation: the Administration section (Overview, Users, System, Translations, Announcements, Help center and, on SaaS, Plans, Website pages, Affiliates, Support desk) and Settings › Installation. The first account is an administrator; others are made on the Users page. Administrators are also the only people who can work and sign in during maintenance mode, and they receive the service status emails.
Administrators don't see other accounts' recordings: the role is about the installation, not about other people's data.
Roles inside an account
Every user also has a role in their own account (the team that owns websites and recordings). The account's managers set them on the Team page (Team & roles).
| Role | May do |
|---|---|
| Manager | Everything in the account, including the team (invite, change roles, remove) and billing / plan. |
| Member | Everything with the account's data — websites, recordings, heatmaps, funnels, surveys, A/B tests, alerts, settings of websites — but not the team or billing. |
| Viewer | Read only: watches recordings and reads reports, changes nothing. The dashboard shows You have view-only access: you can look, but not change anything. Ask a manager of the account for more rights. |
Members and viewers can be limited to some of the account's websites. Some paid AI actions are for managers only (for example switching the site summary on).
Support desk roles SaaS
On the SaaS edition's support desk, a user can additionally be an agent (sees and answers the tickets assigned to them) or a manager (sees every ticket and assigns them). Set under Users › ⋯ › Support role. Administrators always have every right there. See Support desk.
Sign-in protection
| Protection | Details |
|---|---|
| Passwords | 10 to 200 characters (new accounts, invitations, password changes). Stored as hashes only. |
| Changing the sign-in email | Needs the current password. |
| Password reset | A one-time link by email (Forgot password), limited to 6 requests a minute. |
| Sign-in attempts | At most 5 a minute for one email from one address, and 20 a minute for one email from all addresses together. |
| Two-factor sign-in | Optional per person (Settings › Account › Two-factor sign-in): a 6-digit code from an authenticator app (Google Authenticator, Microsoft Authenticator, 1Password, Authy…) after the password. 10 one-time recovery codes are shown once; new ones can be made. After 10 wrong codes the account's code checks stop for 15 minutes. An administrator can turn it off for someone who lost phone and codes: Users › Turn off two-factor sign-in. |
| Sign in with Google | Optional, set up under Settings › Installation › Sign in with Google (Installation settings); 20 attempts a minute per address. |
| reCAPTCHA v3 | Optional, invisible: checks that sign-ins (from the dashboard), password-reset requests, sign-ups (SaaS) and contact messages come from people. Set up under Settings › Installation › Spam protection (reCAPTCHA) (details). If a wrong key ever locks everyone out: php artisan replora:recaptcha off. |
| Suspension | A suspended person can't sign in, and is signed out everywhere at once with all their API tokens deleted (Users). |
| Browser sessions | Expire after 120 minutes without activity (SESSION_LIFETIME in .env). |
API tokens and their abilities
People create API tokens under Developers › API tokens (API tokens). Creating one asks for the person's password. Each token has:
| Setting | Values |
|---|---|
| Name | Up to 120 characters |
| Access (abilities) | Full access (*: everything the account can do), or a selection: recordings:read — list sites and sessions, replay recordings; recordings:write — create, change and delete sites and recordings. Modules can add abilities. |
| Expires | After 1 to 3650 days, or never |
A token's value is shown only once. Tokens act with their owner's role and websites, and an ability can only narrow that.
Limited tokens can't take an account over
Routes about the person, the account and the installation — profile, team, tokens, users, settings, billing, integrations — accept only the dashboard's own session or a full-access token. A token with only some abilities (for example a key with recordings:read in a script) gets 403 there, so it can never make itself a full-access token. Ask AI reads data with the abilities of the token the question came with.
Details for developers: REST API: overview.
Rate limits
| What | Limit |
|---|---|
| The dashboard (a signed-in browser session) | 600 requests a minute per person |
| The API with a token, and anonymous API calls | 120 requests a minute per person (or per address) |
| Sign-in, two-factor codes, invitations, sign-up | 5 a minute per email and address; 20 a minute per email |
| Password reset | 6 a minute |
| Recording uploads from the tracking script | 600 a minute per visitor address (setting Uploads per minute per visitor address, 60–100 000: Installation settings) |
| Surveys and A/B tests on your websites | 120 a minute per visitor address |
| AI features | Summaries 20 a minute, AI search 20 a minute, session questions 30 a minute, Ask AI 20 a minute, help chat 10 a minute (and 50 questions a day per person) |
| Exports, installation settings, license, maintenance | between 5 and 20 a minute each |
Over the limit, the server answers HTTP 429 and the dashboard shows the message.
Visitor privacy
What the tracking script records is controlled per website under Website › Settings (Website settings) and in the page's own HTML (Privacy & masking attributes). The main tools:
| Setting (Website › Settings) | What it does | Limits |
|---|---|---|
| Censor all input fields | On: everything typed is recorded as *** except the fields you allow. Off: typed text is recorded, except passwords, card numbers and other secret fields. | on/off |
| Mask the text of these elements | Text of matching elements is recorded as ***, in the visitor's browser. | up to 30 CSS selectors, 200 characters each |
| Leave these elements out | Matching elements aren't recorded at all (an empty box of the same size in replays). | up to 30 |
| Record what is typed in these fields | Exceptions to masking (passwords and card numbers stay masked). | up to 30 |
| Never record these IP addresses | No recording from these addresses, ranges (10.0.0.0/8) or patterns (203.0.113.*). | up to 100 |
| Exclude your own visits | An opt-out link that stops recording in each browser it is opened in. | |
| Remove these query parameters from addresses | Removes parameters (e.g. token, email) from every recorded address; * removes the whole query string. | up to 50 names |
| Record network request details, Record canvas drawings, Record frames from other domains | Whether request/response bodies (passwords and tokens replaced by ***), <canvas> drawings and frames of other domains are recorded. | on/off |
| Only record visits that start on, Never record these pages, Record this share of sessions, Only record sessions that last at least | Record only part of the traffic. | share 1–100 %, length 0–600 s |
| Retention | How long recordings are kept: 7, 30, 90, 180 or 365 days (default for new websites: Default retention (days), 30 — Installation settings; plans can limit it). Older recordings are deleted automatically. |
IP addresses are never stored in full. Replora zeroes the last part of IPv4 addresses (203.0.113.0) and the last 80 bits of IPv6 addresses before saving. An account's managers can make this stricter under Settings › Account › Visitor privacy › Anonymize visitor IP addresses more strongly: only the first two parts of IPv4 addresses are kept (203.0.0.0), and the first 32 bits of IPv6. That applies to new visits of every website of the account; location and IP filters become less precise.
Personal data: export and deletion
| Who | How |
|---|---|
| Anyone, for themselves | Settings › Account › Your data › Download my data: one JSON file with everything kept about them — profile, account, sign-in settings, API tokens, websites, plan, and each installed module's part (e.g. support tickets, affiliate data on SaaS). Secrets (password hash, two-factor secret, token values) are never included. 6 downloads a minute. |
| Anyone, for themselves | Settings › Account › Delete account: removes their sign-in after the password; when nobody else is in the account, its websites, recordings and subscription go too. |
| Administrators | Users › Remove user: the same deletion for someone else. |
| Members of an account | Delete single recordings, or many at once from the session list, and whole websites (with all their recordings). |
| Recorded visitors | Their sessions are deleted with the retention period, or by hand. Visitors identified with identify can be found by that identity in the session list (Filters & search) and deleted. |
On SaaS, accounts accept the Data Processing Agreement; the date shows on the Users page (DPA accepted). See Website pages & SEO.
AI and your data
When the AI features are on, parts of recordings are sent to Anthropic's Claude API: for summaries and questions the session's facts and moments (pages, clicks, errors) without the visitor's identity; for AI search only the question and today's date. Masked text stays masked. Details: AI features.
Uploaded files
Files people upload (support ticket attachments, website page documents, affiliate payout proofs) are checked before they are kept:
- always: PDFs that run scripts or launch actions or carry other files, Office documents with macros, and archives with encrypted entries, programs, scripts or far too much content (zip bombs) are refused;
- with a ClamAV scanner set up (Settings › Installation › Virus scanning of uploads, e.g.
unix:///run/clamav/clamd.ctlortcp://127.0.0.1:3310), every file is also scanned for viruses. While the scanner can't be reached, uploads are refused rather than kept unchecked.
Logos and favicons are re-encoded as pictures and SVG is refused (it can carry scripts); announcement images are redrawn as JPEG.
Secrets in settings
Passwords and keys entered under Settings › Installation (SMTP password, API keys, webhook secrets…) are stored encrypted with the app key (APP_KEY) and never sent back to the browser: the field only says Saved. If the app key changes, those values can't be read any more and the .env values apply again. Keep APP_KEY in your backups (Backups & moving servers).
Related
- Users · Installation settings · Service status & maintenance
- Privacy & masking attributes — masking in the page's HTML
- AI features (Claude)
- Environment (.env)
