Free trial
Legal

Privacy policy

Translation. The French version prevails.

Who is responsible?

For the data entered in a customer workspace (contacts, worksites, post, e-mails, invoices, accounting entries, hours, absences, documents, photos), the customer business is the controller; Jomax Group SA processes it on the customer's behalf as a processor (art. 9 FADP). For account and billing data, Bulkit group purchase orders (Jomax Group SA is the seller; the supplier receives the company name and delivery address), the website audience measurement, support requests and the platform's e-mails, Jomax Group SA, Route Principale 101, 1642 Sorens, Switzerland, UID CHE-255.349.938, is the controller. Contact for any data protection question: info@jomax.ch or by post to the address above.

What data?

  • Account data: name, e-mail, job title, language, password (stored only as an irreversible hash), date and version of the terms accepted.
  • Data the customer enters in the apps: contacts, addresses, tasks, photos, plans, scanned post, e-mails (messages of mailboxes connected by IMAP are copied into Teixa), quotes and invoices, accounting entries, hours and absences, documents, expense claims, messages. The name typed by a client who accepts a quote online is recorded with the date and time.
  • Employee data in Time & team: hours, absences, AHV number (visible to administrators only) and, if the business enters them, sick and accident absences and medical certificates. These are sensitive data (art. 5 let. c FADP): a manager only sees "absent", without the reason; only administrators and the person concerned see the reason and can enter, change or delete such an absence.
  • Teamwork and recovery of mistakes (only between the customer business's own staff, never with its clients or partners): comments and mentions (@) on a record, the person responsible for a record and the people following it, personal notifications and whether they have been read, presence on a record (who is viewing it right now), change history (the state of a record before each change or deletion, with the author and the date) and the recycle bin (Corbeille) of deleted items. Purpose: let the business's team work together and put a mistake right (restore a version or a deleted item). As for its other data, the customer business is the controller and Jomax Group SA its processor. This is data already held in the workspace (no new category of data) and no additional provider is involved. Mentions and assignments are also announced by e-mail (see e-mail sending below); each person can switch this off in "My account". Comments, notifications and the change history are encrypted with the business's own key.
  • Team communication and organisation (between the company's internal staff only, never with clients or partners): team chats (team and worksite channels, groups and direct messages; a direct message is visible only to its participants, admins included), reactions and read indicators ("Seen by"), which each person can turn off; personal notification settings; approval requests and their history (who asked, who approved or declined, when, with which comment); announced absences and stand-in (dates, stand-in, note); to-dos and follow-ups; automatic reminders; team calendar (the reason for an absence is visible only to admins and the person concerned); workload per person (open items only: no login times or activity, no monitoring of behaviour within the meaning of art. 26 ArGV 3). Notifications on the phone: if a person turns them on, their browser's push service (Apple, Google, Mozilla or Microsoft) receives the device's technical address and an empty message, with no content; the text shown ("2 new notifications") is then read inside Teixa. No new category of data; this data is encrypted with the company's own key, included in the full export and deleted with the workspace.
  • Support requests ("Report a problem"): message, page and version of the app, language, the browser's latest technical errors and, if the user adds one, a screenshot. No password, cookie or form content.
  • Log of e-mails sent by the platform: date, type, recipients, subject and delivery status.
  • Technical data: session cookie, server logs.
  • Anonymous audience measurement of the public website: see below.

Cookie and browser storage

Teixa sets a single cookie, bt_sid, and only after login or sign-up: it keeps the session open (30 days at most, removed at logout). It is strictly necessary; without it, login is impossible. The app also keeps in the browser's local storage the chosen language, drafts of long forms, entries made offline and waiting to be sent, and the last pages opened; the service worker keeps a copy of the app's files so that it opens offline. This data stays on the device and can be cleared in the browser's settings. No advertising or tracking cookie is used.

Audience measurement of the public website

Visits to the public pages (home, terms, privacy, imprint) and openings of the app are counted by Teixa's own server. No cookie is set, no tracking script is loaded, no third-party service is called.

  • Recorded for each visit: the day (without the time), the page, the domain name of the site the link came from (not the full address), the campaign parameters utm_source, utm_medium and utm_campaign if they are in the link, the device type (mobile, tablet or computer), the country only if the network infrastructure passes it on, and an anonymous identifier. At sign-up, an anonymous event is added, linked to the landing page of the same visitor on the same day; neither the name nor the e-mail is in it.
  • Not recorded: the IP address and the browser's user agent. They are only used, in memory, to compute the anonymous identifier (truncated SHA-256 hash combined with a random salt).
  • The salt is replaced every day and the old one deleted: a visitor's identifier cannot be linked to the next day's. The count therefore gives visitors per day, not visitors followed over several days.
  • Browsers that send "Do Not Track" (DNT: 1) or "Global Privacy Control" (Sec-GPC: 1) are not counted. Known bots are not counted either.
  • Retention: 13 months for the detailed rows; then they are replaced by monthly totals without identifier, and deleted.

Purpose: to know how much the website is visited, without profiling and without disclosure to third parties.

Where is it hosted?

The data is hosted in a data centre in the European Union (Netherlands) by Railway Corporation (a US company; Western Europe region, Amsterdam). Each customer business has a separate space at database level. The operator's staff access a workspace's data only for operations, security, backups or a support request from the customer.

Backups

A full copy of the platform (database and files) is downloaded every day to a computer of the operator in Switzerland, whose disk is encrypted. Once a week, an encrypted copy (AES-256) is placed in iCloud Drive (Apple); only the operator holds the key, Apple receives unreadable data only. Daily copies are kept for 30 days, then one copy per month for 12 months; older copies are erased. Data deleted from Teixa is therefore gone from every backup 12 months later at the latest. Backups are used only to restore the service after an incident.

Service providers and disclosure abroad

These providers process data on the operator's behalf, only for the function stated. For the data in customer workspaces they are sub-processors (art. 9 para. 3 FADP), authorised by the customer in the data processing annex; the operator binds them to equivalent data protection obligations and is responsible for their compliance.

  • Hosting and database: Railway Corporation, United States, with servers in the Netherlands (EU). The data stays stored in the EU.
  • Platform e-mails (sign-up confirmation, password reset, notifications, task reminders, technical alerts): the operator's Google Workspace (Google Ireland Limited, Ireland; Google LLC, United States). A copy of the e-mails sent stays in the operator's sent mailbox. E-mails sent from a customer's own mailbox go through the mail server it has configured.
  • Artificial intelligence: Anthropic (Anthropic Ireland, Limited, Ireland, or Anthropic PBC, United States; processing in the United States), Claude model, for these functions:
    • reading documents dropped in: scanned post, receipts, card statements and vouchers, expense claims, filed documents (title, summary, keywords), quotes and orders to take over, forms filled in from a document, Bulkit supplier invoices. The file is sent when a user drops it into these functions;
    • assistance started by a button: quote drafts, reminder texts, sales analyses (with client names and amounts), accounting analyses and questions, entering hours from a text, correcting a dictated text ("Correct with AI" button), HR summary (overtime and holidays; pseudonymised data: employees are designated by a code, without name, and no sickness or accident data is sent);
    • Bulkit: classifying a member company's activity from the purpose published in the commercial register (admission is always decided by a person).
    Anthropic acts as a processor, bound by its data processing agreement: it processes this data only to produce the requested answer. Only the data needed for the function is sent; under its commercial terms, Anthropic does not use this data to train its models and deletes the data received and the answers within 30 days, unless the law requires otherwise or the content is flagged as breaching its usage policy (then kept for 2 years at most). Fields read from a document are filled in automatically and remain editable; drafts and analyses are only used if a user decides so. No automated individual decision within the meaning of art. 21 FADP is taken. Reading a document to fill in a form is never offered on the absence and employee forms. An administrator can switch off all AI for the business in the settings: nothing is then sent to Anthropic.
  • Voice dictation: the microphone button of the forms uses the user's browser speech recognition (for example Google for Chrome, Apple for Safari), under that provider's terms; Teixa only receives the resulting text, never the recording.
  • Off-site backup: Apple (iCloud Drive), only encrypted copies to which Apple has no key (see "Backups").
  • Payment of the Teixa subscription and of Bulkit group purchases: Stripe Payments Europe Ltd., Ireland, only when online payment is enabled. For the subscription, Teixa sends the company name, its e-mail address, its language and the chosen plan; the billing address and any VAT number are entered at Stripe. Card data is entered at Stripe, never at Teixa. For this subscription billing data, the operator is the controller (performance of the contract, art. 31 para. 2 let. a FADP).
  • Worksite maps (swisstopo, Federal Office of Topography, Switzerland): to place a worksite on the map, Teixa's server sends its address (street, number, town) to swisstopo's geocoding service, without a name or other data. The grey base map is loaded by Teixa's server: the browser does not contact swisstopo.
  • Device location ("Nearest site"): your location is read only when you tap "Nearest site". It is compared with the sites on your device and is never sent to or stored by Teixa.
  • Commercial register (Zefix) and the federal UID register: only the name or number searched for, when a business is looked up or checked.

Fonts, libraries (maps, PDF, 3D, QR) and the text recognition (OCR) engine with its language files are hosted by Teixa itself: loading them contacts no third party. External images of a received e-mail are only loaded if the user asks for it for that message.

Disclosure abroad (art. 16 FADP): the EU and Ireland provide adequate protection according to the Federal Council. For the United States: Google LLC and Stripe, LLC participate in the Swiss-U.S. Data Privacy Framework (official list of the US Department of Commerce), recognised as adequate by the Federal Council since 15 September 2024; Railway and Anthropic are bound by their data processing agreement, which incorporates the EU standard contractual clauses with the adaptations to Swiss law (competence of the FDPIC). A copy of these safeguards can be requested at the address above.

Retention

A workspace's data is kept for the duration of the subscription, then for 30 days after cancellation, before permanent and automatic deletion (data and files, including support requests and the e-mail log). A trial workspace without a subscription is considered cancelled 60 days after the end of the trial. In both cases, the workspace's administrators receive an e-mail stating the deletion date. Backups are erased 12 months later at the latest (see "Backups"). The customer's legal retention duties (e.g. 10 years for accounting records and vouchers, art. 958f CO; 5 years for working-time records, art. 73 OLT 1) remain its own: it exports its data before cancelling (full export in the settings, export of the journal, general ledger and audit trail in accounting). Server technical logs: 30 days at most (the host's retention period). Changes to the accounting (audit trail) are kept as long as the workspace. Teamwork: presence on a record is erased after 1 day; the change history is kept for 12 months and items in the recycle bin for 90 days, then they are erased automatically together with their files; comments and notifications are kept as long as the workspace. All of this data is included in the full export and deleted with the workspace. Chat messages: 24 months by default (the admin can choose 6, 12 or 24 months, or no limit), then erased automatically.

Your rights

You can ask for access to your data (art. 25 FADP), its correction or deletion, the handing over of your data in a common format (art. 28 FADP), or object to a processing, at info@jomax.ch. The answer is given within 30 days; proof of identity may be requested. A workspace's administrators can export all data at any time from the settings and, at the request of a person concerned, erase an item from the change history or the recycle bin for good before the end of its retention period. For the data in a customer workspace (for example if you are an employee or a client of a business that uses Teixa), the request goes first to that business; the operator assists it and forwards to it without delay any request received directly. You can also contact the Federal Data Protection and Information Commissioner (FDPIC) or, in the EU, the supervisory authority of your country.

Security and data breaches

Passwords stored as a hash (scrypt), sessions stored as a fingerprint, encrypted connections (HTTPS), separation of businesses in the database (row-level security), passwords of connected mailboxes encrypted (AES-256-GCM, key outside the database), backups. A security breach likely to result in a high risk for the persons concerned is reported to the FDPIC as soon as possible (art. 24 FADP); the customer business concerned is informed without delay, so that it can meet its own obligations.

Changes

The version in force is published on this page, with its date.

Version of 30 October 2026 · See also the terms of use and the imprint.