attenta.

Attenta

Privacy Notice

Version 2026-10-13. This notice explains how Glimtheim AS handles personal data in Attenta and on the Attenta website.

Who is responsible?

Glimtheim AS, located in Norway, is controller for account, security, support and website data. A company using Attenta is normally controller for employee profiles and working-time records; Glimtheim AS processes that data for the company under the Data Processing Agreement. Contact support@attenta.io.

Data we use

We process account identifiers, name, email, login providers, language and security events; company, employee, project and working-time information entered into the service; support communications; and limited technical logs needed to operate and secure Attenta. The mailing list separately stores the submitted address, language and subscription events. We do not sell personal data or use advertising trackers.

Why and legal basis

We use account and service data to provide and administer the service, control access, investigate faults or abuse, answer requests and meet legal obligations. Processing necessary for a contract with the individual relies on that contract. Where the contract is with an organisation, necessary account administration, support and security may rely on our legitimate interests in operating and protecting Attenta, subject to individuals' rights. Processing required by a specific legal obligation relies on that obligation. The customer determines the lawful basis for its employee records. Acknowledging this notice is not blanket consent. Optional newsletter marketing uses separate consent, withdrawable through unsubscribe or by contacting us.

Processors and transfers

The application and primary PostgreSQL database, including stored export files, are hosted with Hetzner in Germany. Resend processes recipient addresses, message contents and delivery information for service and requested marketing emails. Resend's published documentation states that stored email data is held in the United States; a European sending region does not change the storage location. Emailing an hours export also sends that attachment through the provider to the selected recipient. Resend publishes contractual transfer safeguards in its Data Processing Addendum. Transfers subject to applicable data-protection law require a valid transfer mechanism and any necessary additional safeguards. Contact us for information about the arrangements and how to obtain copies. Chosen sign-in providers also process login information under their own applicable notices.

Optional phone reminders

Phone delivery is off for a company until its owner explicitly allows it in Company settings. The owner can decline or later stop this processing while retaining email reminders and time recording. The approval is recorded with the stated provider-notice version; a new provider list requires new approval. Each person also chooses whether to enable their phone. Android delivery uses Google Firebase Cloud Messaging; iOS delivery uses Apple Push Notification service. The Hetzner API sends reminder text, including the company name and the fact that a clock is still running, company/session identifiers and the destination notification token to the chosen platform provider. We do not copy the account or time-record database into these services. Notifications can reveal work status on the phone screen. Firebase additionally processes an installation identifier and delivery-related technical information, and may process it on Google’s global infrastructure. Firebase Analytics and messaging auto-initialization are disabled; the Android app registers when phone reminders are chosen. Disabling phone reminders or deleting the account revokes server registration. The Android app also requests deletion of its Firebase installation when that phone removes reminders; other/offline phones may retain provider installations until cleanup. Failed local cleanup is retried when the app starts or before re-registration. Google states that associated installation data is removed from live and backup systems within 180 days after an installation deletion request. Apple handles device/delivery data under its service terms. We request zero offline retention for reminder messages from both providers; this does not claim immediate erasure of all provider logs or backup copies.

Retention and security

Account, support and security information is retained for its stated purpose and longer only where necessary for a documented legal obligation or legitimate claim. Workspace records are processed on the organisation's lawful instructions. Deactivating access or hiding a record does not necessarily erase archived records or audit history. Start account deletion from Account in the app or from the public deletion page; a sign-in email link verifies the person and a final review confirms the scope. No fixed service availability or recovery guarantee removes our applicable security or data-protection obligations.

Account deletion

Confirmed deletion removes the login, connected sign-in records, preferences, memberships, account legal-acceptance rows, invitations addressed to the person, account support records, push registrations and matching newsletter subscription from the active service. Sessions stop working. Owners choose transfer to an active member or explicit company closure. Closure removes that company's active-service data, including employee profiles, hours and saved exports. Surviving companies remain controllers of their employee and work records and must assess lawful retention and erasure instructions; a login deletion is not treated as their instruction to erase every work record. Exported files and recipient mailbox copies are outside our direct control. A minimal account/company-action journal is kept for 30 days to reapply erasure after restoration; the receipt address is erased after sending or after seven days if delivery fails. Database backups and email-provider copies have their separate schedules described below.

Your rights

Depending on the processing, you may request access, correction, deletion, restriction, portability or object. For employee records, contact your employer first; we assist the employer with requests. Email support@attenta.io for Attenta-controlled data. You may complain to Datatilsynet or your local supervisory authority.

Time-record retention

The current product setting is 5–20 full calendar years after the year of the work record, defaulting to 5. It is a product setting, not a legal determination of how long a record must or may be retained. Automatic expiry is currently disabled. Changing the setting alone does not delete records. Earlier lawful deletion instructions and valid erasure requests are assessed separately; contact us rather than assuming scheduled deletion has taken place.

Newsletter, email and backup copies

Confirmed newsletter records remain while the subscription is active. A daily cleanup process removes unconfirmed records more than 30 days after the last confirmation message (or creation if none) and unsubscribed records more than 30 days after unsubscribe, when processing succeeds. Resend currently states that email and log data on its Free, Pro and Scale plans is retained for 30 days; its backup and account-termination retention are separate. Recipient mailbox copies are outside our direct control. Database backups include local recovery and release snapshots. Deletion from the active database is not immediate erasure of every backup. Retention of recovery copies is assessed according to recovery needs, applicable instructions and legal obligations; contact us about the copies relevant to an erasure request. We do not represent the normal backup rotation as a verified maximum for every retained snapshot.

Current security measures

The service uses HTTPS for browser-to-service traffic, framework-managed password hashing, email confirmation for password accounts, login lockout and request-rate controls. Membership and role checks restrict access to company data held in a shared database; supported operations record change histories. These measures reduce risk but do not guarantee that incidents or data loss cannot occur. This description does not claim end-to-end encryption, a separate database per customer or independent security certification.

Company and contact

Glimtheim AS, located in Norway. Norwegian organisation number: 835890112. D‑U‑N‑S® number: 348225941. Contact: support@attenta.io.

Effective 13 October 2026 — draft for legal review

Account deletion, optional phone-provider instructions and their data lifecycles updated 13 October 2026.

Back to Attenta