Privacy and saved information

Operator and data controller

WORKPAY FI is operated by ALBERT DUSHI, the data controller for this service. Contact: hello@workpaying.com.

Who to contact

WORKPAY FI is responsible for operating this service. Send privacy questions, requests to access or correct your records, deletion requests, or objections to usage statistics to hello@workpaying.com. We may need to verify that the request concerns your own account.

Public calculator and guides

The public calculator processes the example wage and hours inside your browser. These values are not sent to WORKPAY’s server or stored in your private profile. Public pages do not load the app’s account or usage-analytics code.

Like other websites, the hosting infrastructure receives connection information needed to deliver pages and protect the service. This can include an IP address and request information. That is distinct from the app’s aggregate usage statistics.

Purposes and legal grounds

Account access, saved work and synchronization provide the service you request, under the service relationship with you. We use necessary security records to protect accounts and delivery, and limited usage statistics to understand and improve the service. Our stated legitimate interests are operating a secure, reliable and useful service; you can object to the usage-statistics processing by contacting us.

Optional daily email reports depend on your choice to enable them, which you can withdraw in the app. Any future personalized advertising will require its own consent choices. Where data protection law applies, you may also request restriction of processing or a portable copy of your data, as applicable. WORKPAY does not make employment, credit or tax decisions about you.

Private work history and email

Signing in stores your verified email, an account identifier and session information. If you use the app, it saves your selected language, profession, settings, work and travel records, allowances and other information you enter. Records are linked to your verified account so that the same account can retrieve them on another device.

A device may also keep an account-specific offline copy of your work. A fresh page needs a connection to verify the session. Use a device lock and sign out on shared computers. Signing out hides your records in the app; it does not erase the cloud history. Unsynced changes may remain on that device until the same account signs in again.

Verification codes are sent through our Google business mailbox. Daily reports are optional and are sent when you choose the finish-day email action. Report subscriptions, prepared report content and delivery status are stored to send the message and prevent duplicates. You can disconnect reports in the app.

Cookies, device storage and account security

WORKPAY uses secure session and verification cookies for sign-in. A verification code expires after 10 minutes. A remembered session lasts up to 30 days; a shared-device session has a 12-hour server limit. Your language and account-specific offline work may be kept in browser storage. These functions support the service you request.

Access checks, request limits and security records help prevent account misuse and repeated email requests. Some abuse-prevention records use hashed identifiers. A cookie or token is not a public link to your work.

Usage statistics

The owner dashboard shows totals for verified accounts, successful sign-ins, active days, professions and approximate connection countries or regions. It does not list private hours, wages or work notes. The owner’s admin account is excluded from these totals.

Country information can come from the browser’s connection to our hosting edge. The browser fallback supplies only a country code; the connection trace and IP address are not saved in analytics. The server stores account-linked activity and sign-in events with timestamps, the country and any region supplied by the hosting edge. The owner dashboard presents aggregates of these records. These estimates can reflect a VPN. Regions appear as Unknown when unavailable.

The dashboard covers up to 90 Helsinki calendar days. Older activity and sign-in events are removed during subsequent service use; cleanup does not run while the service receives no requests. Work histories and report records are kept until removal is requested or the service’s retention arrangements change.

Public company statistics

Signed-in users can see how many other verified WORKPAY accounts have the same current saved employer. The viewer is excluded and each other account counts once across devices. This count is visible only to users who have saved that employer; it is not displayed in the public directory or monthly rankings. The current employer comes from the latest saved employment period effective today in Helsinki. Counts include accounts without recorded earnings and update as profiles sync. Unlisted employers have no shared count. Employment is self-reported; these are not verified employees or the full workforce. Multiple email accounts can belong to one person.

When you choose an employer, we save the employer and its effective date in your private profile. Your recorded gross pay automatically contributes to monthly company statistics. This is explained in the employer form; it is not a separate opt-in. The operator uses these records to provide industry comparisons as part of WORKPAY, relying on its interest in producing useful service statistics. You may object to this processing or request correction or deletion at hello@workpaying.com; we will assess your request.

Only work dates with a selected catalog employer contribute. Unlisted employer names stay private. Public reports contain a company name and a rounded gross-pay estimate. Worker counts and contributor-count ranges are not published. Names, email addresses, individual wages and work notes are not displayed. At least five verified accounts with positive earnings are required, and one account may not contribute more than 40% of the company total. Account verification does not verify an employment relationship.

Company reports begin with September 2026. A month closes at 00:00 Helsinki time on the 7th of the following month. Completed entries synchronized before that time may contribute. Public totals are rounded to the nearest 100 euros. Gross earnings above 20,000 euros per account per month are excluded from public totals as an outlier safeguard, without changing the private history. Tax-free and unconfirmed reimbursements are excluded. Larger totals do not establish better pay or represent all company employees.

After the cutoff, the aggregate report is created when that month is first opened. It then stays fixed; later private corrections do not revise the published aggregate. Account-linked contribution rows are removed when their report is created. Private source work histories remain subject to the existing retention policy. Small-group suppression and rounding reduce disclosure risks; they are not a promise that all inference is impossible.

Providers and your choices

The website and stored app data use OpenAI Sites and its Cloudflare hosting infrastructure. Google provides the business-mail sending service. These providers process information needed to deliver, secure and operate their services; this notice does not promise that every processing step takes place in Finland.

You can change your profile, disconnect daily emails, sign out or contact us about access, correction and deletion. If you believe your data has been handled incorrectly, you can also contact Finland’s Office of the Data Protection Ombudsman at tietosuoja.fi.

Advertising

Advertising is not active on this website. We are preparing an AdSense application for public content pages. The private app, account screens and admin dashboard do not load Google advertising code.

Before personalized advertising is activated for visitors in Finland, the wider EEA, the UK or Switzerland, the public pages will use a Google-certified consent system. The notice and consent choices will identify advertising providers and explain relevant cookies and data use.