Version 2.1 — published 5 September 2026, effective 5 October 2026. Version 2.0 (effective 3 September 2026) applies until then.
What changed in version 2.1: section 5 says that some technical measures depend on the application version your employer has installed; section 8 states the roles of our payment and invoicing providers; section 10 adds retention periods for profile photographs, diagnostic records, logs, audit records and backups; section 12 describes support access to accounts. Nothing else changed.
This service is operated by SCREENish LTD, a company registered in the Republic of Bulgaria, UIC 205586868 (VAT BG205586868), with its registered address at 2A Angel Kanchev Street, 3rd floor, 4000 Plovdiv, Bulgaria. You can reach us at info@screenish.com. We have not appointed a data protection officer; the contact for all data protection matters is the address above.
Account information. First and last name, business email address, company name, billing address, VAT number where applicable, account identifiers and account preferences.
Authentication data. Username, password hash, password-reset requests, two-factor authentication settings and trusted-device records, session identifiers and login history.
Support and correspondence. Support tickets, e-mail correspondence, contact forms, chat transcripts with our support team, attachments you choose to send, and feedback.
Billing information. Subscription plan, invoice details, billing history, transaction identifiers, payment status and tax information. We do not store complete payment card numbers. Payments are processed by Braintree (a PayPal service) and, where offered, Revolut; what we retain is the last four digits of the card and the payment provider's customer and payment-method tokens, which let us charge the subscription without ever holding the card itself.
Technical information. IP address, browser type and version, operating system, device information, language, time zone and referring page, as recorded in ordinary server and application logs; and the version of the tracking application your device runs.
Security information. Authentication and security logs, failed sign-in attempts, account lockouts and fraud-prevention records.
Website visitors. When you visit screenish.com we determine the country your IP address belongs to, on our own server, solely to decide whether to show you the cookie consent banner; the address is not sent to anyone else for this purpose and no record of it is kept beyond ordinary server logs. Cookies and similar technologies — including the analytics and marketing tools that load only with your consent — are described in the Cookie Policy.
Marketing. We send no newsletter and run no mailing list today. If you consent to marketing cookies, advertising measurement happens as described in the Cookie Policy; that is the extent of our marketing processing.
Where a customer uses SCREENish to monitor its personnel, we process on that customer's behalf: employee names and identifiers; screenshots; activity records (keyboard and mouse activity counters — the applications record how much you type and click, never what); application names and window titles; project assignments, attendance records, work schedules and notes; location information where the customer enables it; face-verification images where the customer enables them; timestamps and productivity reports; and the other monitoring data the customer configures.
Face verification. Where the customer enables it, the SCREENish application periodically checks that the person at the device matches the enrolled profile. The application presents the monitored person with a face-verification notice and records the person's acknowledgement or consent action as the customer has configured it; where the customer relies on explicit consent under Article 9(2)(a) GDPR as the applicable condition for the processing of biometric data, that recorded action functions as the record of explicit consent. The comparison happens on the device itself — the recognition models are built into the application and no photograph is sent anywhere for matching. A check that succeeds stores no photograph at all. A check that fails stores the frame encrypted on the device, and a small composite of such failed frames is uploaded to the customer's account for human review, after which the local copies are deleted; the uploaded composite is itself deleted after 45 days. Because laws governing biometric and workplace-monitoring technologies differ between jurisdictions, the customer is responsible for determining whether the feature may lawfully be enabled for particular personnel and for establishing the applicable legal basis under Article 6 GDPR and a condition permitting the processing of biometric data under Article 9(2) GDPR, together with any further notice, consent or other authorisation required under the law that applies to them.
Automated assessments. Where a customer enables monitoring, the Service may automatically assess activity records and face-verification integrity signals for indications of unusual activity, manipulated input, or a spoofed or replayed camera feed. These indicators are personal data processed on the customer's behalf and are made available to the customer's authorised reviewing users for human review; they are not automatically displayed in the monitored individual's own dashboard. SCREENish does not make employment, disciplinary, compensation or similar decisions on the customer's behalf. The customer remains responsible as controller for the purposes, lawful basis, use and consequences of the assessment and for responding to data-subject requests concerning it.
This data is processed exclusively under the Data Processing Agreement. SCREENish does not decide the purposes or means of that processing, does not use it for its own purposes, and does not sell it or make it available to third parties except as the DPA permits.
The desktop applications and the SCREENish browser extension for Chrome collect the monitoring data described in section 4, on the employer's behalf. What they do not collect is part of their design: they count keyboard and mouse activity but never record which keys are pressed or what is typed, and the browser extension additionally collects no browsing history and no list of applications — it captures only the screen you yourself choose in Chrome's sharing dialog when you start tracking, and only while you are tracking. When tracking stops or the screen share ends, the extension has no access to your screen at all; its activity level is derived solely from whether your computer is in use.
Screenshots and not-yet-reported working time are stored temporarily on your own computer, encrypted with a key generated on your device that cannot be exported from your browser profile, until they are uploaded to your employer's account. If you choose "remember me", your sign-in is stored the same way — encrypted, on your device only.
Which of these measures apply to you depends on the version of the application your employer has installed. Earlier generations of the desktop application, which on some computers can no longer be updated, protect this local store with an older scheme rather than a key generated on your device, and do not offer screenshot blurring. The measures described here and in section 12 are those of the current version; your employer is warned in its dashboard when it enables a setting that the version on your device cannot apply.
The applications include team communication. While you track time for a team, your online and in-call status and the display photo you choose are visible to the members of that team.
Calls are transmitted in real time, encrypted, directly between the participants; where a direct connection is impossible they pass through SCREENish's own relay server, which cannot read them. SCREENish does not record calls and stores no call content. The person who started a call can record it locally, to their own device; when that happens, every participant sees a recording indicator and a notice naming who is recording. What that person then does with their local recording is their responsibility, and — where they record colleagues — their employer's.
Chat messages pass through SCREENish servers only for the moment of delivery; the server keeps no copy. Your conversation history is stored solely on your own devices, encrypted with the same non-exportable key.
Files sent to teammates travel directly from device to device and never touch SCREENish servers. If a direct connection cannot be established, the transfer fails with a notice — it is not rerouted through us.
Whiteboard. Sketches on the shared whiteboard are relayed to the people in the call and are not stored on our servers; someone who joins late receives the current board from the relay's in-memory snapshot, which disappears when the room closes.
| Purpose | Legal basis (GDPR Article 6) |
|---|---|
| Providing the service: accounts, authentication, running the platform | Performance of a contract — Art 6(1)(b) |
| Billing, invoicing and tax records | Contract — Art 6(1)(b); legal obligation — Art 6(1)(c) for accounting and tax law |
| Support and correspondence | Contract — Art 6(1)(b) |
| Security: abuse prevention, sign-in protection, fraud prevention, logs | Legitimate interest — Art 6(1)(f): keeping the service and its accounts secure |
| Website analytics and advertising measurement | Consent — Art 6(1)(a), given through the cookie banner and withdrawable there |
| Establishing, exercising or defending legal claims | Legitimate interest — Art 6(1)(f) |
We share controller data only with the providers needed to run the service, each bound by a data processing agreement or its own controller obligations:
| Recipient | What for | Where |
|---|---|---|
| Amazon Web Services, Inc. | Data storage (S3) and transactional e-mail (SES) | United States, US-West (Oregon) region |
| Akamai Technologies, Inc. (formerly Linode) | Hosting infrastructure | United States — Atlanta, Georgia (see section 9) |
| Braintree (PayPal) | Card payments — an independent controller for the payment processing itself, under its own privacy terms | United States / EEA entities |
| Revolut | Payments, where offered | EEA / United Kingdom |
| inv.bg (Invoicing Solutions Bulgaria AD) | Issuing invoices (company or individual name, contact person, address, VAT number) — our processor under section 4 of its terms of service | Bulgaria and Germany; no transfer outside the EEA |
| reCAPTCHA on sign-in forms; analytics only with your consent | Google Ireland Ltd / Google LLC | |
| Meta Platforms | Advertising measurement, only with your consent | Meta Platforms Ireland Ltd |
We may also disclose data to professional advisers, to authorities where the law requires it, and to a successor in a business transaction. We do not sell personal data.
Screenshots and other captured images are stored with Amazon Web Services in the US-West (Oregon) region of the United States, and the application is hosted on infrastructure operated by Akamai Technologies in the United States (Atlanta, Georgia). Transfers outside the European Economic Area are covered by European Commission-approved Standard Contractual Clauses. A current list of the providers involved, with the transfer mechanism for each, is kept in our Data Processing Agreement, available to customers on request.
| Data | Period |
|---|---|
| Account information | While the account exists; deleted on account deletion |
| Billing and invoicing records | The period Bulgarian accounting and tax law requires |
| Screenshot and phone-photograph images | Deleted 45 days after capture |
| Application names and window titles | 93 days |
| Screenshot activity records (times, counters, notes — no image) | 365 days |
| Phone-photograph records (coordinates, note) | 45 days |
| Desktop-application check-in log (IP, app version) | 21 days |
| Automated activity assessments | 93–365 days depending on outcome |
| Facial reference photographs | Deleted on consent withdrawal, replacement, or deactivation of the employment; kept while the employment continues so returning staff do not re-enrol |
| Face-verification result records | The verification images are deleted at 45 days; the result records (scores and timestamps, no image) at 365 days |
| Profile photograph (avatar) | Until you replace it: the previous photograph is deleted when a new one is uploaded |
| Diagnostic records sent from the desktop application for support | Deleted 45 days after upload |
| Web-server access and error logs | At most 52 days |
| Application logs (user id, endpoint, IP address) | 90 days |
| Audit records — support access to accounts, setting changes, data exports, consent and acceptance records | For the life of the account |
| Database backups | 1 year |
These periods are enforced by automated jobs and storage lifecycle rules; the authoritative statement, per category with its mechanism, is Annex I of the Data Processing Agreement.
Where SCREENish LTD is the controller, you may ask us for a copy of your personal data, ask us to correct or erase it, object to or ask us to restrict how we use it, and ask for it in a portable form. Where processing rests on consent, you may withdraw the consent at any time, as easily as you gave it, without affecting the lawfulness of what was done before. Write to info@screenish.com; to protect your data from impersonation we will ask you to write from the e-mail address registered on the account, or otherwise verify who you are.
If you are monitored through SCREENish by your employer, these rights exist against your employer as controller. Ask them; we assist them in answering, under the Data Processing Agreement.
You also have the right to complain to a supervisory authority. Ours is the Commission for Personal Data Protection of the Republic of Bulgaria (Комисия за защита на личните данни), 2 Prof. Tsvetan Lazarov Blvd, Sofia 1592, Bulgaria — www.cpdp.bg. You may also complain to the authority of the country where you live or work.
Data is encrypted in transit (TLS). Captured images are stored encrypted at rest and are served only through short-lived, per-request authorised links — never as public URLs. Access to personal data is limited to personnel who need it to run the service. Support access to an account by our personnel is limited to one authorised role, requires a recorded reason, and is notified to the account holder on every use. The technical and organisational measures we commit to, in detail, are Annex II of the Data Processing Agreement.
We update this policy when what we actually do materially changes. The date at the top shows when it was last updated; material changes are announced through the service or by e-mail.
SCREENish LTD
2A Angel Kanchev Street, 3rd floor
4000 Plovdiv, Bulgaria
UIC 205586868
info@screenish.com