Skip to content
← Back to home
Terms of ServicePrivacy Policy

Effective 13 October 2026 · Version 2026-10-13

Privacy Policy

This notice describes the current Pulse Modus website and hosted application. It distinguishes account and security information from records controlled by your organisation, and explains the experimental tools separately.

Your data at a glance

  • Account and security information supports verified, individual access. Customer workspace records have separate organisation permissions.
  • No advertising trackers or marketing cookies are currently installed by Pulse Modus. Browser storage supports language, sign-in and recovery.
  • You can request access, correction or deletion through our contact address. Revoking access does not itself erase retained records.

Optional hosted AI

For Cloudflare AI, read the separate feature notice dated 20 October 2026. It describes the additional provider and data flow for this optional feature. Optional AI data notice

On this page

  1. Who is responsible
  2. Information handled by the service
  3. Where information comes from
  4. Purposes and legal grounds
  5. Who can receive information
  6. Processing locations and international transfers
  7. How long information is kept
  8. Cookies and browser storage
  9. Experimental AI and bill/photo processing
  10. Security and your choices
  11. Requests and your rights
  12. Children and sensitive information
  13. Changes to this notice
hello@pulsemodus.com

1. Who is responsible

RIVIERA PULSE DOO is responsible for the account, website security and support processing it determines. Its registered details appear below. Our privacy contact is hello@pulsemodus.com.

An organisation using a workspace determines why its property, owner, contractor and work records are used and who may access them. For those customer-controlled records, it normally acts as the data controller and we provide processing under its instructions. If Riviera Pulse itself determines the use of records for its own property services, it has its own controller responsibilities. The role depends on the actual use, not only the name of an account.

Ask the responsible organisation about its own notices, reasons for collection, invitations and retention decisions. We can help identify it after verifying that you are entitled to the information. A required customer data-processing agreement and operational arrangement must be settled before real customer use; this notice is not that agreement.

2. Information handled by the service

Passwords and authentication material are handled through the configured authentication system. Do not share them with support. We do not ask you to put payment card details into Pulse Modus. Recurring payments are inactive.

Swipe or scroll sideways to read the full table. With a keyboard, focus the table and use the arrow keys.

InformationExamplesWhy it is handled
Account and accessEmail, account identifier, verification state, sign-in/session records, role and invitation or employee grants; authenticator enrolment for executive access.Create and verify accounts, control access, recover accounts and protect the service.
Workspace recordsProperty descriptions, requests, notes, contact or participant identifiers, scope versions, amounts, decisions, assignments, visits and completion evidence.Provide the coordination and recordkeeping functions authorised by the organisation.
Files and bill informationPhotos, uploaded files and their metadata; bill fields and source text; extracted values when a permitted tool is used.Provide the selected evidence or bill workflow, subject to its permission and transport settings.
Technical and security informationNetwork/IP information available to hosting, browser/request details, timestamps, errors, rate-limit and audit records.Deliver pages, detect abuse, investigate faults and protect accounts and records.
Support and legal acceptanceInformation you send to support; the terms/privacy versions acknowledged by an account and acceptance time.Answer requests and keep a record of the applicable account agreement.

3. Where information comes from

You provide information by creating an account, submitting a form, uploading permitted material or contacting us. Your organisation and authorised participants can supply records and invite you. The application creates timestamps, access and action records as you use it. Hosting and authentication providers receive technical information needed to deliver their functions.

If optional external sign-in is made available and you choose it, the identity provider supplies the permitted identity information needed to verify your account. The available choices are shown on the sign-in screen. We do not claim that every provider supported in code is currently enabled.

4. Purposes and legal grounds

Account provision and requested support use information needed to perform the service agreement or take steps you request before it. Security, abuse prevention and fault investigation serve our legitimate interest in a safe, reliable service, subject to the rights and interests of the people affected. We also retain or disclose information where a legal obligation requires it.

An organisation must establish the lawful basis for its customer workspace processing. Accepting these terms does not give it permission to collect every kind of personal data. Where consent is genuinely needed for a separate optional activity, it must be specific and can be withdrawn without changing earlier lawful processing.

We do not use the terms checkbox as marketing consent. Pulse Modus currently has no advertising or newsletter signup workflow, and we do not sell personal data.

5. Who can receive information

Permitted organisation members and deliberately accepted participants receive only information allowed by their roles and grants. A guest invitation, a published view and an employee experimental grant have different boundaries. Private files are available through permission-checked access; a download or copied record may then be held independently by its recipient.

We use these providers for the current configuration:

Swipe or scroll sideways to read the full table. With a keyboard, focus the table and use the arrow keys.

ProviderFunctionInformation involved
SupabaseAccount authentication, database and private file storage.Account/authentication data and the permitted records/files stored for the application.
RenderHost the application in Frankfurt, Germany.Requests, technical/security information and data processed by the application while handling permitted requests.
ResendDeliver account verification and recovery email.Recipient email, message content needed for the account step and delivery metadata.
Google WorkspaceSupport mailbox for hello@pulsemodus.com.Support messages and attachments you choose to send.
  • Authorised personnel may access information necessary to respond to a support or security issue. Do not submit unnecessary customer information in a support message.
  • We may disclose information to meet a valid legal requirement, protect rights or investigate misuse, limited to what is necessary and lawfully permitted.
  • Additional outbound workspace messages are not implied by account email delivery. Use the actual active controls and notices for any permitted delivery workflow.

6. Processing locations and international transfers

The application host is in Frankfurt. That does not mean all authentication, email, support, provider administration, subprocessors or backups remain in Germany or the European Economic Area. Our providers operate internationally, and applicable provider arrangements determine their handling.

A complete customer-specific transfer and processing arrangement is required before admitting real customer data. We do not claim that a Frankfurt host alone establishes compliance, that all providers process only within the EU, or that a particular transfer safeguard has been agreed for your organisation. Contact us for the available provider information and the arrangement applicable to your workspace.

7. How long information is kept

Retention depends on the purpose: an active account or grant, an unresolved security or support issue, the organisation’s need for a decision and work history, and any applicable legal obligation or dispute. Files follow the authorised record and cleanup rules; temporary uploads can expire. Provider logs and backups have their own settings and lifecycle.

There is currently no single published automatic deletion period for all account, workspace and backup data. Full account/organisation erasure and deletion propagation through backups are handled as verified requests and require operational review. We will explain what can be removed, what must be kept and why in response to your request. Access revocation and orphan-file cleanup are not complete erasure.

When data no longer has a justified purpose, it should be deleted or appropriately de-identified, subject to applicable obligations. Contact us or the responsible organisation to request a retention review. Do not use the prototype as your only copy of records you must retain.

8. Cookies and browser storage

Pulse Modus currently uses functional storage rather than advertising tracking. The public pages do not install advertising cookies or third-party analytics scripts. Providers may keep server-side security and operational records as described above.

Browser recovery can contain notes or identifiers. Use a trusted device. Closing a screen or signing out does not guarantee that every browser-restored draft or downloaded file is erased. Clear site data and your own downloads when appropriate. Blocking functional storage can break language preference, sign-in or recovery; it does not erase server records.

If non-essential analytics or marketing technologies are introduced, we will update this notice and provide the required choice before activating them. Terms acceptance does not provide that choice.

Swipe or scroll sideways to read the full table. With a keyboard, focus the table and use the arrow keys.

StoragePurposeDuration or clearing
Language cookie (pulse_language)Remember English or Montenegrin interface preference.Up to one year; change language or clear site data.
Secure account session cookieKeep the authenticated session available to the server.Time-limited by the session and provider expiry; cleared by sign-out.
Recovery or optional sign-in flow cookieBind a short-lived password-recovery or external sign-in step to this browser.Short-lived; recovery context is limited to ten minutes and the external sign-in flow to five minutes.
Tab session storageKeep unsent or uncertain action-recovery details, selected workspace preferences and permitted draft state needed to continue safely.Generally lasts for the browser tab/session until the application or you clear it; browser restore behavior may differ.

9. Experimental AI and bill/photo processing

Approved employee tools are separately gated. Their input and extracted text are processed only through the permitted tool path; an experimental grant does not permit access to customer workspaces.

Photo OCR and PDF text extraction can run in the browser using bundled assets. Extracted text may then be sent to the permitted Pulse Modus API for analysis. Local draft tools use supplied or permission-filtered source text and produce editable suggestions. In the current hosted configuration, hosted model processing and bill-original transport are disabled.

A local browser extraction step is not a promise that no data leaves the device: read the tool’s active notice before submitting. Do not include personal or confidential information in experiments unless separately authorised. We do not use these tools to make solely automated approvals, assign authority or initiate payments.

10. Security and your choices

The service uses HTTPS, time-limited sessions, server and database permission checks, account verification, bounded grants and additional executive authentication. Private file access is permission-checked and can expire or be revoked. These controls reduce risk; no internet service can guarantee absolute security.

Use strong individual credentials, protect your email account, keep devices current and sign out on shared devices. Report a suspected breach to hello@pulsemodus.com. Do not send passwords, authenticator QR codes or one-time codes.

Any required personal-data incident notification will be assessed under the law that applies to the incident. This notice does not promise a notification deadline that overrides that assessment or claim an independent security certification.

11. Requests and your rights

Depending on the applicable law and processing basis, you may request access and a copy, correction, deletion, restriction, a portable copy where applicable, or object to processing. You may withdraw a specific consent where consent is the basis. Rights can have lawful limits, including protecting other people and retaining records required by law or for legal claims.

Write to hello@pulsemodus.com with the account email and the type of request. Do not send an identity document initially. We may ask for proportionate information to verify identity and authority. We will respond within the applicable legal period and explain any permitted limitation. For customer workspace records we may need to refer the request to, or act with, the responsible organisation.

There is no current one-click account or whole-workspace erasure tool. Asking to close an account or revoke access is separate from requesting deletion of retained data. You may complain to Montenegro’s Agency for Personal Data Protection and Free Access to Information (AZLP), or another competent supervisory authority where applicable.

12. Children and sensitive information

The account service is intended for adults aged 18 or over, not children. Do not use it to collect children’s information or sensitive personal data without a separately established lawful and necessary workflow. If you believe such information has been submitted inappropriately, contact us so we can assess it with the responsible organisation.

13. Changes to this notice

The effective date and version are shown on this page. We will revise the notice when the service’s handling changes and provide appropriate information about material changes. A privacy acknowledgement records that the notice was presented; it does not waive your rights or authorise unrelated processing.

Service operator

RIVIERA PULSE DOO
DRUŠTVO SA OGRANIČENOM ODGOVORNOŠĆU "RIVIERA PULSE" TIVAT

PC RAČICA, TRG DARA PETKOVIĆA 8, Tivat, Montenegro

Company registration: 5-0137516/001
Tax identification number (PIB): 04407679

Registered company address. Client meetings are arranged directly; this is not a public reception office.

Provider privacy information and data protection authority

  • Supabase
  • Render
  • Resend
  • Google Workspace
  • AZLP — Montenegro

Questions about these documents?

Contact us for account help, privacy requests or questions about the service.

hello@pulsemodus.com
Create your accountSign in