Legal

Privacy Policy

Version: 1

Effective date: 2027/01/01

1. Who We Are

This Privacy Policy explains how Smotics - Unipessoal, Lda ("we", "us" or "our") processes personal data in connection with the Orbitar SaaS platform.

Controller contact details:

  • Legal name: Smotics - Unipessoal, Lda
  • Tax identification number: 508871751
  • Registered office: Estrada da Garganta, Quinta Saude Rio Seco, 8005-130 Faro, Portugal
  • Email: geral@smotics.pt
  • Data protection contact: geral@smotics.pt

For data protection matters, contact Smotics at geral@smotics.pt.

This policy is designed to align with:

  • Regulation (EU) 2016/679 (GDPR)
  • Portuguese data protection law (Law no. 58/2019)
  • the Portuguese ePrivacy framework, including Law no. 41/2004, as amended, for cookies and electronic communications

This policy is intended for platform users and tenant representatives. It does not replace each tenant's own privacy notice addressed to its customers, employees, suppliers and other entities.

2. Scope and Roles Under the GDPR

Orbitar is a SaaS platform with logical separation between tenants. When your organisation asks us to create or administer your access, we process the necessary data on its behalf. The tenant acts as controller where it determines the purposes and means. Where the tenant acts as another organisation’s processor, Smotics acts as a sub-processor for the covered workflows. We process those data under the tenant’s documented instructions and the Data Processing Agreement (DPA).

Smotics is the controller for processing for its own purposes, including billing, legal obligations and security of the shared infrastructure. We distinguish this processing from support, account administration and features we operate on the tenant’s behalf. Section 4 identifies the applicable purposes and legal bases.

Optional integrations are provided by Smotics and activated for each customer according to the contracted service and authorised configuration. Before activation, Smotics informs the customer of the specific applicable conditions.

3. Categories of Data

3.1 Data we control directly

  • Professional contact, subscription, billing and correspondence data.
  • Events needed for infrastructure security, such as IP address, browser information, date, outcome of authentication attempts, and access and request metadata.
  • Minimal compliance records, such as the channel, date and outcome of a privacy request.

3.2 Data controlled by tenants (processed by us on their behalf)

Tenants may store personal data relating to their own entities, including for example:

  • customers/consumers
  • employees/candidates
  • suppliers/partners
  • other business contacts

The specific categories and purposes are defined by each tenant, not by us.

When a tenant uses AI or voice transcription features, processed data may also include:

  • messages, prompts, responses and conversation metadata with AI agents
  • documents, images, attachments or excerpts used as context for AI agents
  • embeddings, memories, notes or knowledge sources associated with agents, where configured by the tenant
  • audio and transcripts generated during voice transcription sessions
  • technical execution metadata, such as provider, model, token count, duration, errors and request identifiers

Data processed on the tenant’s behalf also include account and profile data, permissions, interface preferences and operational audit records the organisation configures or requests.

For voice, a live session may process transient audio. The library can store recorded or uploaded audio separately from transcripts. In audio-only mode, audio is stored and is sent for transcription only when an authorised user requests it.

Where necessary for the feature, special category data are processed on the lawful basis and under the Article 9 GDPR condition the tenant identifies. Protected mode replaces supported identifiers with pseudonyms before sending data to the provider. Content that can identify an individual remains subject to the GDPR even after this processing.

3.3 Google user data and OAuth

Orbitar offers two distinct optional OAuth uses for each provider, Google and Microsoft.

  • Google sign-in. With the openid and email scopes, Orbitar uses the stable identifier, email address and verification status, and issuer to link the Google identity to an existing user, authenticate that user and keep the account email aligned.
  • Microsoft sign-in. With the openid, email and profile scopes, Orbitar uses the identity identifier, issuer, Microsoft organisation identifier where applicable and available email address to link and authenticate an existing user.
  • Sending through Gmail. When an authorised person connects a mailbox, Orbitar additionally requests https://www.googleapis.com/auth/gmail.send. Orbitar uses this permission to send authorised messages through the connected mailbox.
  • Sending through Microsoft. When an authorised person connects a mailbox, Orbitar requests openid, email, offline_access and https://outlook.office.com/SMTP.Send to identify the mailbox and send authorised messages.

For sign-in, Orbitar stores the identity association, email address, issuer and connection and use dates in the relevant tenant. Sign-in does not retain the provider’s codes or tokens once the flow completes. On disconnection, Orbitar removes the local identity association and preserves an alternative means of signing in. An email address kept as part of the platform account follows the account retention rule.

For sending, Orbitar stores the connected mailbox, permissions, expiry information and necessary tokens, encrypted and restricted to the tenant’s sending service. Sending permissions are used for authorised sending. They are not used to read, list, modify or erase incoming messages, contacts, documents or calendars.

The temporary login handoff retains the hash of an opaque secret and the minimum identity data needed, without retaining provider tokens in that record. The handoff for connecting a sending mailbox retains encrypted temporary credentials. Both are single-use and valid for ten minutes; expiry prevents use even before physical removal by the cleanup routine. Disconnecting a mailbox removes local credentials and prevents reactivation after a restore. For Gmail, Orbitar also attempts to revoke authorisation with Google; the attempt does not prove the provider’s outcome. Microsoft authorisation can also be revoked in Microsoft Entra.

Users can disconnect an identity in their Orbitar profile. Global mailboxes are connected and disconnected by people with the applicable management permissions. Users may connect or disconnect their own mailbox in personal settings, limited to their account in the tenant and following the company’s instructions. Users can also review authorisations in their Google or Microsoft account. These technical authorisations have a distinct purpose. Section 4 describes the lawful bases and section 12 explains how to exercise rights.

Smotics does not sell data received from Google APIs or use them for advertising, commercial profiling or AI model training. Human access is limited to what is necessary in cases the applicable rules allow, such as authorised support, security or a legal requirement. Use and transfer of information received from Google APIs follows the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including its Limited Use requirements.

3.4 Biometrics and photographs for attendance and access control

When made available and enabled by the tenant, biometric management allows us to process, on its behalf, biometric representations (templates), person identifiers, modality and format, origin, dates, version status and synchronisation metadata for authorised terminals. Templates used to identify a person are a special category of personal data, even when encrypted; they are not anonymous data.

Central storage supports the tenant's distributed attendance system: where terminals are located at separate premises and workers perform duties at different locations, it allows a single biometric enrolment to be distributed only to authorised terminals, avoiding repeated collection. Use is optional and covers only the tenant’s workers. The tenant determines the people, premises and purposes covered. Smotics does not use these templates for its own purposes, advertising, AI model training or identification across tenants.

The central biometric archive contains only templates received from terminals, in accepted formats whose non-reversibility is documented by the manufacturer. They are stored encrypted and distributed only to authorised terminals within the same tenant. Orbitar does not generate templates from photographs or request terminals to do so. Receiving a template does not, by itself, establish how the manufacturer produced it.

Photographs processed by the equipment management module are exclusively for display and are separate from templates. A display photograph received from a terminal may be retained encrypted in that module and distributed to other authorised terminals within the same tenant. The entity's profile image may be used to replace the display photograph on terminals; photographs from terminals are not imported into the entity's profile image. Displaying a photograph neither authorises nor triggers, through Orbitar, template generation or facial recognition from that photograph.

A photograph accepted for display may be retained while necessary for that purpose, including delivery to authorised terminals temporarily offline, under the tenant's lawful instructions. This retention has its own purpose and lifecycle, is not unrestricted and does not defer deletion when due under the DPA and data subject rights. A photograph is not, merely by existing, special-category biometric data; that classification depends on the actual technical processing and purpose.

Use is subject to the controls and conditions described in the DPA. Templates are encrypted at rest and must be transmitted through protected channels. For templates, administrative interfaces and management APIs display metadata without making their biometric content, ciphertext or hashes available. Decryption by the service for synchronisation is distinct from reconstructing the original biometric characteristic; we do not claim that encryption makes access impossible for someone who obtains the keys and control of the infrastructure. The manufacturer’s declaration documents the template’s characteristics; it does not remove Smotics’ responsibilities for processing and software under its control.

The restriction on disclosure through management interfaces does not limit data subject rights or data return obligations; these are fulfilled through the secure procedure set out in the DPA. Retention based on necessity, deletion of revoked versions and handling of unavailable terminals follow the DPA, without a recovery window for revoked versions. We assist the tenant with rights requests, security and assessment of the processing, without replacing its notice to workers or its decisions as controller.

Importing from a terminal may retain an identity not yet linked to a person in the application, including a numeric identifier, name and, where supplied by the device and admitted by the integration, cards, templates, display photographs and an encrypted authentication password. Subsequent linking may merge identities and retain source versions needed for reconciliation. Receiving or retaining a template is not equivalent to approving its use or authorising delivery to any terminal; compatibility, purpose and authorised destinations within the same tenant remain subject to controls.

Before enabling workplace biometrics, the Customer documents the lawful basis, applicable special category condition, necessity of use and central storage, alternatives, and the data protection impact assessment. Regular use at multiple authorised sites is distinct from an actual transfer. The Customer initiates template erasure in time to destroy the templates upon transfer to another workplace or termination of employment. The Customer confirms removal on each terminal and arranges any necessary intervention on site. Smotics erases operational copies under its control when carrying out the instruction and provides support on request.

3.5 Optional WhatsApp integration

When the Customer activates the WhatsApp Business Platform integration, we process on its behalf phone numbers, contact names and identifiers, account and channel identifiers, messages and replies, menu selections, timestamps, delivery/read statuses and technical metadata. Data comes from the people communicating, the tenant and the WhatsApp service. A contact may have no Orbitar account or association with a person in the platform; this does not make their data anonymous. Authorising the WhatsApp account connection is not a Meta sign-in to Orbitar.

Processing enables receiving and responding to communications, carrying out tenant-authorised operations and retaining the related history under section 9. When the tenant authorises Coexistence with the WhatsApp Business app, contacts and conversations predating the connection may be imported. The operator is informed about this import and the service's sharing options.

The assistant is identified as automated, with a link to the tenant's applicable privacy information and a human contact route. When the tenant configures an authorised AI agent, necessary content from the active session may be forwarded to the applicable AI providers, including when responding to free text, with information provided to the person before the first forwarding. Imported history is not used as AI context in this integration; dialogues are not extracted into persistent memory or published as shared knowledge. Ending a session and disabling persistent memory do not delete retained history. The agent may also consult knowledge sources previously configured and authorised for the functionality; this does not add dialogues to those sources. The human contact route is the phone number or email provided by the tenant, not an automatic transfer to an operator in the chat.

The connection uses authorisation credentials stored in encrypted form to communicate with the service. Disconnecting removes local authorisation and suspends communication, but does not itself delete history or prove revocation or deletion in Meta systems. The content processed depends on supported message types: the current integration does not download incoming multimedia attachments to process them as images, audio or documents.

This information about processing by Smotics complements the tenant's notice to the people communicating with it, including those who do not use the platform directly. Use of the channel does not, by itself, constitute consent to marketing.

The channel distinguishes support and operational messages from campaigns and promotions. Where these communications are authorised, the tenant must provide the applicable means to object. For automated support, the telephone number or email address monitored by the tenant is displayed in the initial message and on a request for human contact. The notice precedes the first transmission to AI, including for free text. Where applicable, the tenant’s notice also covers data obtained indirectly through Coexistence.

The initial notice and an effective human contact precede the first forwarding to AI, including when the first message is free text. Marketing objections prevent subsequent sends, including queued messages and retries. Channel opt-in is distinct from the legal authorisation for marketing. Imported history is excluded from the context sent to AI and dialogues, including the active session, are excluded from persistent memory. Technical logs are effectively deleted within 30 days of local creation or receipt, without restarting the period on disconnection; business history follows the company’s own retention criteria.

3.6 Optional Citizen Card reading

When the tenant enables the feature, the browser asks Smotics-Connect, installed on the workstation, for the selected fields from the Portuguese Citizen Card. The selection may include identity fields, such as a name or identifiers, and/or address fields, depending on the tenant's configuration and purpose. The browser displays the data for review. The authorised user chooses whether to apply the data to the entity record. Saved fields are processed as tenant data.

The tenant ensures information to the individual, a lawful basis and limitation of collection and storage to what is necessary, in accordance with its role and the applicable instructions. The tenant obtains and documents consent or authorisation where applicable. Selective reading of fields is distinct from making a copy of the card. A PIN or CAN required for a read grants access to the card and does not record consent to further processing. CNPD guidance on the Portuguese Citizen Card (https://www.cnpd.pt/cidadaos/areas-tematicas/reproducao-cartao-cidadao/).

Reading and preview are transient. The individual can choose manual completion of the same record. Where address data are selected, the official SDK can request the address PIN at the workstation and query the Citizen Card’s central address service. Reproducing the card requires a separate basis under Article 5 of Portuguese Law No. 7/2007.

Smotics processes on the company’s behalf the local operations it determines or performs through Smotics-Connect, in addition to hosting the saved fields. Where the company acts as another organisation’s processor, Smotics acts as a sub-processor for the covered operations, under the applicable instructions and authorisations. Smotics-Connect does not retain card data, PIN or CAN. PIN/CAN provide technical access and do not constitute consent for subsequent processing. The official SDK’s address query is a separate communication from the workstation. Production diagnostics in Orbitar and Smotics-Connect exclude PIN/CAN, the full card response and rejected fields. They may identify the operation and technical error. Only selected, reviewed and confirmed fields are saved; manual entry remains available.

3.7 AI and voice

Before each agent is activated, Smotics and the company define its purpose, accessible data and sources, authorised tools and automatic operations, operations requiring confirmation and responsibility for human review. An authorised person decides before effects on individuals occur. Administrative automation remains limited to approved instructions and permissions. Pseudonymisation does not prevent all identification through free text. The AI interaction notice is distinct from detectable, machine-readable marking of synthetic outputs and the duties of those publishing them, where applicable.

Before recording, using or uploading audio and before sending it for transcription, the company informs participants and ensures the authorisations required for the mode and communication concerned. Technical microphone permission does not replace those conditions. The pre-capture notice identifies the mode, provider and retained data. If a required authorisation is missing, the user stops the operation. Audio-only mode sends audio for transcription only on an authorised request.

4. Purposes and Legal Bases

Where Smotics acts as controller, it uses the bases set out below. Sections 7 and 8 identify recipient categories and transfer mechanisms. Section 9 gives the retention periods and criteria.

  • Professional contacts and tenant relationship. We process contact data necessary to administer the business relationship, communicate and answer requests based on our legitimate interest in providing and administering the service, subject to the right to object. Contractual necessity applies only to a contract with the individual or steps requested by that individual before entering a contract.
  • Billing and legal duties. We use the identity and billing data needed to issue invoices and meet applicable tax, accounting and compliance obligations. A lack of mandatory data may prevent us from issuing an invoice or providing the contracted service.
  • Security of shared infrastructure. We process access events, authentication attempts, IP addresses, browser information and request metadata to prevent unauthorised access and investigate incidents, based on our legitimate interest in protecting the service. Some technical data are generated when the service is used.
  • Direct correspondence with Smotics. We process contact details and necessary content to respond, follow up and, where applicable, defend legal rights. The basis is our legitimate interest in those purposes or the legal obligation applicable to the request. Without sufficient contact details or context we may be unable to respond.
  • Features that depend on choice. Where an operation requires consent, we identify the purpose and the choice at collection. Individuals can withdraw consent through the mechanism in section 12.

On behalf of the tenant, we process data needed for provisioning, authentication, permissions, preferences, auditing and support requested by the organisation. The necessary account data may be required for access. The tenant determines the lawful basis. OAuth connections, preferences and optional features are separate choices. For accounts using external authentication, the tenant can provide another way to sign in.

For usage accounting we keep only the data needed, such as token and SMS counts. Smotics does not reuse tenant data for product improvement, model training or metrics collection for those purposes. Agents may prepare information and recommendations. A competent person with authority to review and change the outcome makes final decisions about individuals.

5. Cookies and Similar Technologies

We use technologies strictly necessary to provide the functions requested, including maintaining the authenticated session and protecting requests against CSRF. These technologies qualify for the statutory consent exemption. Blocking the session cookie prevents the authenticated session from being maintained. Blocking CSRF protection may prevent protected requests from being submitted.

  • orbitar_sessionid. Smotics uses it to maintain the authenticated session. It normally lasts 14 days and is renewed during use. The session ends on logout.
  • orbitar_csrftoken. Smotics uses it to validate protected requests. The browser retains it for up to 364 days after the last issue.
  • orbitar_device. Smotics uses it to recognise the browser on authenticated requests, associate it with device settings and link push notifications to the device when enabled. It lasts one year from issue or the last authenticated renewal. The browser retains it after logout and Orbitar reuses the valid value at the next sign-in.
  • Interface preferences. Orbitar may store choices such as theme, sidebar or editor state in the browser until replaced or cleared. Preferences synced to the account follow section 9.
  • Push notifications. Orbitar requests browser permission. If the individual permits it, Smotics and Firebase Cloud Messaging use a token and installation identifiers for delivery until disabled or the applicable expiry. Section 7 explains Firebase’s retention. The individual can decline and keep using Orbitar or change the choice in browser permissions.

Technologies requiring consent are activated after an individual makes a choice, which they can change. Interface preferences and the identifiers described are not used for behavioural advertising.

OAuth storage in the temporary window uses sessionStorage to correlate the response with the initiated operation and follows that window’s session. The service worker retains application resources and the unavailable page in Cache Storage; older caches for the same scope are replaced on update. The diagnostics queue uses IndexedDB to send errors and removes records after successful delivery; failed delivery retains them for retry, without an automatic local deadline. Users can clear these data in browser settings.

Diagnostics serve exclusively to investigate faults and provide support. They may include error messages and technical context, URL, stack and authenticated context identifiers, subject to minimisation and access controls. We do not analyse usage habits or collect product metrics. The device identifier maintains the same browser’s authenticated configuration across sessions, including when push is disabled; its one-year duration avoids recreating that association at each sign-in. It does not grant account access and is not used to track browsing on other sites. Diagnostics stored on the server are deleted manually after resolution. Recognised secrets, such as passwords, reusable tokens and authentication headers, are masked in logging paths. Filtering does not classify all free text; operators limit content to what is needed to investigate the failure.

Push notifications display the message text. Smotics ensures that the text sent does not include sensitive data; sensitive details are consulted only inside the application with the applicable authentication and permissions. Logout ends the push association with the account in that session while preserving the device cookie. The application removes push identifiers that are no longer needed when it detects permission withdrawal. The normal touchOffice flow neither requests nor registers user push. Messages already delivered or in transit may remain visible in the browser; users should dismiss them on shared workstations. The Orbitar association, delivery token and Firebase Installation ID have separate lifecycles. Token deletion does not prove Installation ID deletion: Firebase’s period of up to 180 days concerns removal of associated data after a request to delete that ID.

Notifications may be associated with a user account or with a device authorised by the company. In the first case, logout ends the association with the session being closed. Device subscriptions remain active independently of the user and may receive notifications with no signed-in session, for example on an entrance computer displaying access-control alerts. Logout does not disable these subscriptions or delete identifiers needed for their delivery. The company manages the device’s purpose and authorisation. These notifications do not grant access to a user account or restricted user data. Subscription deactivation and withdrawal of technical browser permission have their own effects, distinct from logout. Weekly maintenance deletes device records whose last login was at least 90 days ago, together with dependent associations. This cutoff can also end autonomous device subscriptions and is separate from the cookie’s one-year validity.

6. Sources of Personal Data

Data come from the individual, tenant administrators, systems logging security events and usage, connected Google or Microsoft accounts, the Citizen Card where optional reading is used, and contacts, correspondents and the WhatsApp service where the tenant activates the channel.

When we collect data directly as controller, we provide information at collection. When we receive data from another source, we inform the individual within a reasonable period of up to one month. Where applicable, we provide it earlier if the first communication with the individual or first disclosure to another recipient takes place sooner. For processing on the tenant’s behalf, the tenant provides applicable notices to workers, contacts and other individuals, including correspondents without accounts and people whose historical data are imported.

7. Recipients and Sub-processors

We may disclose data to trusted providers strictly to the extent necessary to operate the service, such as:

  • hosting/infrastructure providers
  • email and notification providers
  • monitoring/logging/security providers
  • backup and disaster recovery providers
  • AI gateway/model providers, including Requesty.ai for routing through European infrastructure and OpenAI when contracted or authorised by the tenant
  • voice transcription providers, such as AssemblyAI and Deepgram, using configured European endpoints

All sub-processors are bound by contractual confidentiality and data protection obligations.

Current sub-processors:

  • PTISP. Hosting, infrastructure, email, entire-machine backups through the Acronis platform and monitoring. Data processed — Data hosted on the platform, technical data, backups, logs and data necessary for sending email. Storage region — Europe. Jurisdiction and remote access follow the instruments applicable to the service.
  • Firebase Cloud Messaging. Web push notifications. Data processed — Firebase installation tokens/identifiers, technical device/browser identifiers and the minimum technical notification content necessary for delivery. Region and transfers — Google/Firebase service subject to applicable data processing terms; international transfers with applicable safeguards may occur.
  • rsync.net. Logical database backups and an external file mirror. Data processed — Data in logical backups and mirrored files and technical storage metadata. Region and transfers — Location configured in Zurich, Switzerland.
  • Requesty.ai. AI gateway/models. Data processed — Prompts, responses, attachments or excerpts sent to models, technical execution and usage metadata. Region and transfers — European endpoint and model allowlist for region eu for requests and inference, including embeddings and alternatives.
  • OpenAI. AI models for agents and assisted features. Data processed — Prompts, responses, attachments or excerpts sent to models, technical execution and usage metadata. Region and transfers — Optional provider, used only when configured/authorised by the tenant; may involve transfer outside the EEA, including to the United States, with applicable safeguards.
  • AssemblyAI. Voice transcription. Data processed — Audio, transcripts and session metadata, depending on the selected mode. Region and transfers — Connection to the configured regional endpoint. Processing and retention depend on the account and mode.
  • Deepgram. Voice transcription. Data processed — Audio, transcripts and session metadata, depending on the selected mode. Region and transfers — Connection to the configured regional endpoint. Processing and retention depend on the account and mode.
  • ClickSend Pty Ltd (Australia, ABN 76 165 918 525). SMS notification delivery. Data processed — Sender, destination number and message text. Region and transfers — Delivery chain and destinations depend on the applicable account and route.

The detailed legal designation of sub-processors is included in the DPA. The list may be updated when relevant sub-processors are added, replaced or removed. Additions and replacements of sub-processors are notified to customers in advance, with an opportunity to object, under the DPA.

Regarding FCM, the platform uses the service to deliver push notifications to subscribed browsers/devices. Firebase indicates that FCM uses Firebase Installation IDs to determine which devices should receive messages and retains those identifiers until deletion is requested by the Firebase customer, after which they are removed from active and backup systems within 180 days. Functional notification content must be limited to what is necessary to alert the user and direct them to the platform.

For AI and transcription features configured for European processing, the platform uses European providers and configurations designed to support compliance with the GDPR, the European Union Artificial Intelligence Act and other applicable European legislation. This compliance also depends on service configuration, tenant instructions and the actual use by authorised users.

Some tenants may choose AI providers involving the processing of or access to data outside the EEA, including OpenAI. In those cases, use of that provider must result from a contractual configuration, authorisation or instruction by the tenant, and international transfers are handled under the following section.

When the Customer activates the WhatsApp integration, the account and number belong to the Customer, which contracts the WhatsApp service directly and authorises Smotics to connect it. WhatsApp/Meta receives and processes the data needed for communication under its applicable service terms. This relationship is distinct from Smotics engaging sub-processors: data protection roles are determined by the actual processing and contracts. Where Smotics engages further processing, the DPA's authorisation, information and responsibility requirements apply.

For optional OAuth workflows, Google and Microsoft receive data needed for sign-in or authorised sending, depending on the workflow in section 3.3. These uses are distinct from Firebase Cloud Messaging. For billing and legal obligations, we may also provide necessary data to billing and accounting providers and competent authorities. Where the official Citizen Card SDK queries the address, it uses the central address service from the workstation.

8. International Transfers

Where an operation involves a transfer outside the European Economic Area (EEA), we apply the relevant adequacy decision or another applicable safeguard, such as standard contractual clauses and supplementary measures where needed. The United Kingdom and Switzerland are third countries covered by European Commission adequacy decisions (https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en). Section 7 and the provider inventory identify the workflows. You can request information or a copy of applicable safeguards at geral@smotics.pt.

The rsync.net logical backups and file mirror are located in Zurich without contracted geographic replication. The provider’s account and billing data may flow to and from the United States separately from backup contents. A storage location or regional endpoint identifies one step in a workflow. The receiving entity, support access and onward transfers are assessed separately.

On the Requesty route configured by Smotics, requests and inference use the European endpoint and the allowlist of models with region eu, including embeddings and alternatives. Direct OpenAI connection may involve processing outside the EEA, including in the United States, and carries no guarantee of processing exclusively in Europe. Smotics confines each workflow to the applicable instructions, destinations and safeguards.

Connecting WhatsApp may involve transfers outside the EEA. The WhatsApp transfer terms (https://www.whatsapp.com/legal/business-data-transfer-addendum) identify applicable mechanisms for the service, including the EU–U.S. Data Privacy Framework where the transfer is covered. Each party ensures the safeguards for workflows under its responsibility. Authorised AI providers are subject to separate arrangements.

9. Retention

We retain data for the stated purpose or for the period required by law.

  • Accounts and preferences: while the account is in use and, where applicable, for an additional period required by law. Masking removes preferences saved in the account. Local browser state follows section 5.
  • Access, security and API: weekly cleanup removes access records that are at least 365 days old, authentication attempts that are at least 90 days old, and API records that are at least 30 days old, measured from the event or attempt as applicable.
  • Usage accounting: weekly cleanup removes periods and ledger entries that are at least 365 days old and accounting job logs that are at least 30 days old, measured from creation. We retain official invoices and covered supporting records and documents for the applicable tax period, generally the following 10 calendar years.
  • Support correspondence: we retain email while dealing with the request and until the next annual review after resolution. At that review we delete resolved correspondence unless information remains necessary for a related ongoing matter, a legal obligation or defence of a right. In those cases we retain only what is needed while the reason applies. For support on the tenant’s behalf, we follow its documented instructions. For Smotics-Connect support, emails, diagnostics, attachments and relevant copies are deleted when no longer needed and no later than 30 days after diagnosis. Mixed cases separate those contents; the general annual review does not extend that deadline.
  • Operational audit requested by the tenant: we retain records while needed for traceability and audit according to the tenant’s criteria. We carry out applicable erasures under its documented instructions.
  • AI: technical records needed for security and troubleshooting follow the workflow’s criteria and the specific limits in this Policy and the DPA. Content, memory and authorised sources follow the tenant’s instructions. Usage accounting and product improvement are distinct purposes. Smotics does not reuse tenant data for the latter.
  • Voice: live audio is transient unless the selected mode stores a recording. In the library, audio and transcripts can be stored separately under the tenant’s criteria without a shared automatic retention period. Authorised deletion covers audio, transcript versions, segments and applicable derivatives.
  • Backups and business data: backups follow each medium’s cycle described in the retention, deletion and backups technical summary. Business data follow the tenant’s instructions and the contractual terms.

Only the tenant’s designated legal or data protection representatives can mask records in the BackOffice. The action is irreversible. When the user account and entity record are linked, it covers both, regardless of where it is initiated. It also covers contacts on the entity record.

Masking removes covered identifying data from operational records, deactivates the records and revokes account access. Internal record identifiers and historical references are preserved. Invoices, signed documents, supporting records and other documents already issued retain their original contents, including any names or addresses they contain, and follow their own access and retention rules.

If a tenant ends the service, active data is returned or deleted according to the applicable instructions and the DPA. Access to residual copies is restricted until expiry in the cycle applicable to each medium, unless retention is required by law.

When erasure is due, we delete the covered data. Anonymisation substitutes for erasure only when effective and appropriate to the purpose; pseudonymisation or field masking does not prove anonymisation of the entire history.

ZKTeco operational events become eligible for cleanup after 90 days: from completion where processing and associated effects are complete; from classification for ignored events without an associated attendance record; and from original local receipt for other events that remain unfinished. Retries and duplicate reimports do not restart these periods. Deletion occurs during periodic maintenance, not necessarily at the exact expiry time. This rule does not change the separate retention of business attendance records, minimum receipts needed to prevent duplication or reapply deletions, transient copies, commands, backups or other services.

Imported identities never linked to a person become eligible for local cleanup more than 90 days after their first creation; where the linked person has been deleted, covered residual data become eligible more than 90 days after that deletion. If a never-linked identity still supports templates retained for the authorised purpose, those templates and minimum identity and provenance support are preserved; covered passwords, cards, photographs and non-biometric source versions are removed by cleanup and do not benefit from that exception. A currently linked identity does not expire solely because of its age. Ending biometric processing and deleting the person trigger central template erasure without waiting for these 90 days; age-based local cleanup does not, by itself, instruct terminals to delete people.

For the biometric templates described in section 3.4, the specific DPA rules prevail: deletion of content when no longer necessary, deletion of revoked versions without a recovery window and no biometric content in logs or history. Preserving business records or merely concealing identity does not justify retaining the template. Display photographs follow the separate lifecycle described in section 3.4 and the DPA: retention depends on necessity for that purpose, including pending authorised deliveries, and ends when deletion is due. Log or history retention does not justify keeping copies of those photographs.

For the WhatsApp integration, messages and imported history are retained under documented tenant instructions defining the purpose, necessity criteria, responsible person and review frequency. There is no universal automatic retention period for all conversations. Reviews are carried out by designated responsible persons, with decisions recorded and required erasures executed; setting the next review date does not amount to automatic history deletion. Retention ends when no longer necessary, through application of those instructions or following an applicable request; the absence of a request or an ongoing contract does not justify unlimited retention. Smotics provides effective deletion and assists the tenant with data subject rights.

Technical logs and AI execution detail for this integration, including copies of messages in those records, are removed 30 days after local creation/receipt, or earlier where required. This is a specific operational period, not a statutory period or a change to the end-of-service deletion rules. Minimum evidence of operations and accounting follows its own necessity criteria, without retaining the original text for that reason. Temporarily disconnecting the channel does not restart retention periods; termination of the service and backups are governed by the DPA.

For business contacts, presentation and acceptance receipts, privacy requests and identifiers used for our own accounting, we retain only what the purpose, applicable obligation or defence of rights requires. We review necessity and remove or reduce data when the ground ceases. Totals used for billing follow fiscal obligations; operational detail processed for the tenant follows its own lifecycle.

An individual’s right to portability of personal data, where applicable, is distinct from a tenant’s provider-switching process and does not grant access to third parties’ business data.

Local logical captures are scheduled at 05:00 and 17:00 and retain completed generations from the five most recent local dates with completed captures. Local full pgBackRest bases are scheduled at 04:00, with WAL archiving and a recovery objective covering the previous 24 hours. Off-site synchronisation of logical backups and application files, including attachments and persistent media, to rsync.net in Zurich is scheduled at 06:00; the mirror follows local rotation when synchronisation completes successfully. Entire-machine backups through Acronis on PTISP infrastructure in Europe use an always-incremental method, are scheduled at 07:30 and 19:30 with a possible start delay of up to 30 minutes, and retain 90 recovery points — approximately 45 days with two completed daily runs, not a fixed retention period. Times follow Europe/Lisbon, including seasonal clock changes. Rotation rules and the recovery window are not absolute maximum deletion periods; the cycles and conditions described in the retention, deletion and backups technical summary apply.

The date for complete deletion is agreed in writing with the Customer, taking account of the actual cycles of all media, including manual copies. Smotics confirms by email operational deletion of active data and the delivery copy and, separately, complete deletion after the covered residual copies expire or are removed. Legally required retention is identified with its own ground, scope and period. A rotation or removal failure that threatens the agreed date requires intervention and communication to the Customer; five published dump dates do not mean a maximum retention of five days.

A restored copy remains isolated while information or intervention needed to confirm and reapply due deletions, masking and revocations is missing, including sessions, OAuth, queues and synchronisation. Only verified tenants may reopen where technical isolation permits. Clearing operational fields does not anonymise the entire history or alter the original content of issued documents.

10. Security Measures

We apply appropriate technical and organisational measures, including:

  • encryption in transit (TLS)
  • tenant isolation controls (separate schemas and access boundaries)
  • role-based access controls
  • least-privilege administrative access
  • audit logs and monitoring of security events
  • backup and restore procedures
  • internal confidentiality obligations and confidentiality agreements for authorised personnel
  • technical records and usage controls for AI and transcription features, including tool limitation, call traceability and abuse protection

No system can be guaranteed to be 100 per cent secure, but we continuously improve security controls based on risk.

11. Support Access by Our Team

Authorised personnel may access tenant data only when necessary for legitimate operational reasons, such as:

  • support requested by the tenant
  • incident investigation
  • maintenance/security tasks

Such access is restricted, logged and subject to confidentiality commitments.

12. Data Subject Rights

You may exercise the rights of access, rectification, erasure, restriction and portability where applicable. For data Smotics processes as controller, send your request to geral@smotics.pt. Where Smotics acts on the tenant’s behalf, contact the organisation that provided your notice. If we receive the request, we refer it to the tenant and provide assistance. We may request proportionate information to confirm identity. You can complain to your supervisory authority, including the CNPD (https://www.cnpd.pt/) in Portugal.

Right to object. On grounds relating to your situation, you can object to processing based on legitimate interests under Article 21 GDPR. You can object to direct marketing at any time. Use geral@smotics.pt for processing by Smotics or the means indicated in the tenant’s notice or communication, depending on the controller.

Withdrawal of consent. Where processing relies on consent, you can withdraw it through the mechanism by which you gave it, through browser permissions for push or through the controller contact in the notice. For processing by Smotics you can also email geral@smotics.pt. Withdrawal does not affect the lawfulness of prior processing.

On the first direct interaction with an AI agent, the interface identifies it as AI and advises reviewing its responses and generated documents. On WhatsApp, the notice and an effective human contact precede the first transmission of content to AI.

13. Tenant Responsibilities

The tenant determines and documents the applicable purposes, lawful bases, retention criteria and notices. Where it acts on behalf of another organisation, it ensures that it is authorised to engage Smotics and refers instructions and data subject requests to the relevant controller. For optional features it defines authorised data, tools, destinations and safeguards and obtains consent where necessary. A person with authority to review and change the outcome makes the final decision about individuals.

14. Changes to the Policy

When this Policy changes materially, we publish the new version and date and inform individuals through the applicable channels. Orbitar may request acknowledgement of the new version to record that the notice was presented. Acknowledgement is separate from contractual acceptance and consent for specific purposes.

15. Contact

For privacy questions:

  • Email: geral@smotics.pt
  • Postal address: Estrada da Garganta, Quinta Saude Rio Seco, 8005-130 Faro, Portugal

For complaints in the EU/EEA in Portugal:

  • Comissão Nacional de Proteção de Dados (CNPD)

SHA-256 (Markdown): 5b67c2f0f502c711f8dd4cde50e9920d2245788cad104a3fd69d8eb0f7b4abfb

↑