Privacy Policy

This Policy applies to opus.mk, studio.opus.mk, studio websites on opus.mk subdomains, the OPUS Studio mobile app (OPUS Beauty Studio in the App Store), and related features, communications, and support (together, the “Service”). It explains how OPUS processes personal data under the Law on Personal Data Protection of the Republic of North Macedonia.

OPUS is a business name operated by Borko Petrevski in Prilep, North Macedonia, pending formal company registration. Where OPUS is the controller, Borko Petrevski operating under the OPUS name is responsible; the privacy contact is hello@opus.mk. This Policy does not represent OPUS as an already registered company. Where other mandatory laws apply, including the GDPR, we also respect the relevant rights and obligations.

Email

hello@opus.mk

Phone

+389 77 826 333

Use of the Service is also governed by our Terms of Use.

OPUS is the controller when it processes data for opus.mk visitors, business accounts, sign-in, security, support, and platform operations. This means OPUS decides the purposes and means of that processing.

When a studio uses OPUS to manage clients and appointments, the studio is the controller of that client data and OPUS processes it to provide the platform. The studio decides why it collects the data, how long it needs it, and which team members may access it.

If your request concerns a particular appointment, note, or client profile, contact the studio first. OPUS will assist the studio where needed and lawfully permitted.

Depending on how you use the Service, we may process the following categories:

• Account and sign-in data: name, email, phone when provided, profile image, studio membership, role, and sign-in security records.
• Studio and team data: business name, contact details, address and coordinates, services, prices, working hours, availability, photos, description, and team-member profiles.
• Location data: device coordinates when you expressly choose to calculate a route to the studio and grant permission in your browser.
• Client and appointment data: name, email, phone when provided, selected service, team member, date and time, appointment status, cancellation reason, and a note entered by the client or an authorised team member.
• Communications: support messages, contact-form submissions, and records showing whether a transactional email was sent or failed.
• Technical and security data: IP address and user agent when recorded for security or audit, request time, system events, cookies, and local browser preferences.
• With analytics consent: platform usage, page visits, and events linked to the signed-in business user's account ID, name, email, and role in PostHog. With advertising consent: Meta Pixel receives marketing and registration page visits, a new-studio event, URLs, cookie and ad-click identifiers, and technical information such as IP address and browser.
• Content you upload: photos, descriptions, public studio information, and other information you voluntarily enter.

A studio may also manually enter information it already holds about a client or team member. In that case, the studio is responsible for informing the person and having a valid legal basis.

If you use the OPUS Studio mobile app or push alerts in the studio web dashboard, we process an installation identifier, push token or browser subscription, linked studio account, personal preferences and provider acceptance or failure records. Each phone or browser is connected only when you choose to enable it and grant notification permission. Client details are hidden in previews by default; if you enable that option, a client name, service and appointment time may appear on your lock screen.

From version 1.0.3, the OPUS Studio mobile app uses Sentry for crash reports and technical performance diagnostics. It does not include PostHog, advertising analytics or session recording. Account, authentication, appointment, security and optional push-notification data are processed to provide the Service. Expo EAS Update can deliver compatible maintenance updates and fixes using technical app, installation, version and device information. Web pages opened from the app follow their own cookie preferences.

We use Sentry, provided by Functional Software, Inc., to diagnose software failures and maintain the reliability of the mobile app. This includes JavaScript and native crash reports, app hangs, startup and screen-loading durations, slow or frozen frame counts, and technical release health. It is operational diagnostics, not advertising or session replay.

Reports can include a randomly generated installation or session identifier, app and build version, update channel and update identifier, operating-system version, device model and memory information, a coarse region inferred from the connection, crash time, exception type, technical stack traces and sampled timing measurements. Our app does not intentionally send your OPUS account identity, name, email, phone, client records, appointment notes, sign-in codes, authentication or push tokens, request bodies or query parameters to Sentry. JavaScript diagnostic reports use a strict field filter and replace free-form error messages; native breadcrumb and network capture are disabled and provider-side scrubbing is enabled.

Session replay, screenshots, view hierarchies, console logs, touch/gesture recording and advertising tracking are disabled. Diagnostics do not record the contents of the app screens. We sample production performance traces to limit data and processing overhead; crash reports and release-health counts help us detect incidents affecting stability.

OPUS relies on its legitimate interest in detecting and fixing software failures, protecting service availability and avoiding repeated disruptions, balanced against your privacy rights. This is distinct from the consent used for optional website analytics or advertising. Accepting the Terms does not constitute blanket consent to data processing. You can ask questions or object to legitimate-interest processing at hello@opus.mk; we assess each request under applicable law.

The OPUS mobile Sentry project is configured in Sentry’s EU region. Sentry and its authorised subprocessors may also process limited service data internationally under their processing arrangements and applicable transfer safeguards. Raw diagnostic events follow the project’s service-plan retention and are automatically removed when that period ends. Relevant, limited incident records may be retained separately where needed for security, a legal obligation or a legal claim. Diagnostic caches on your phone are limited and are removed with the app; signing out does not erase already received diagnostic records.

More about Sentry’s processing arrangements: Sentry Trust Center.

OPUS does not ask for health, biometric, or other special-category data for ordinary booking. Do not put a diagnosis, medical history, or other sensitive information in free-text notes unless it is genuinely needed to provide the service safely and the studio has an appropriate legal basis and safeguards.

• To provide the Service: create an account, sign in, manage a studio, check availability, create and manage an appointment, and send service messages.
• For security and integrity: verify email, prevent misuse and overlapping bookings, control access, keep audit records, and resolve incidents.
• For support and communication: respond to a question, contact request, complaint, or rights request.
• For maintenance and improvement: diagnose errors, maintain reliability and capacity, and improve the booking flow without advertising profiling.
• With your consent: understand platform usage through PostHog and measure, optimise, and build audiences for OPUS ads through Meta Pixel. Meta may associate events with your account under its own terms and privacy policy.
• For legal obligations: respond to a valid authority request, protect legal rights, and keep records that must be retained.

Depending on the purpose, processing relies on one or more of the following bases:

• performance of a contract or steps requested before a contract, such as an account, appointment, or pre-service response;
• a legal obligation, such as when a record must be kept or disclosed;
• a legitimate interest in operating a secure, reliable, and useful Service, preventing misuse, and protecting legal claims where your rights do not override that interest; and
• consent for optional analytics, advertising measurement, and marketing communications where applicable. You can withdraw cookie consent through Cookie settings.

Where OPUS processes client data on a studio’s instructions, the studio determines the legal basis for collecting it as controller.

We share data only as needed for the purposes described here:

• The studio and its authorised team members: so they can view and fulfil the appointment and manage their client records.
• Vercel: for hosting and delivering the web applications when the Service is deployed there.
• Convex: for the database, storage, server functions, and sign-in infrastructure.
• Cloudflare Turnstile: for sign-in anti-abuse checks using technical browser or device and network information. This is a security check, not advertising.
• Resend and/or Sender: for one-time codes and transactional email, only when the relevant provider is configured.
• Twilio: for optional transactional appointment SMS, only when the studio and provider enable the feature; it receives the phone number and message content.
• Polar or another provider identified at checkout: for web subscriptions, invoices and payment status. Card details are entered with the provider, not in the mobile app; OPUS receives the subscription and transaction information needed to manage access.
• Meta and OpenAI: only for the Instagram assistant when a studio connects and enables that feature; the necessary messages and booking context are processed to respond and arrange a confirmed appointment. This is separate from the optional Meta Pixel and does not give access to unrelated studios.
• Formspree: when you submit the contact form on opus.mk.
• PostHog: for platform analytics, only with analytics consent. Meta: for OPUS advertising measurement, optimisation, and audiences, only with advertising consent. We do not send names, emails, phone numbers, or customer appointment content as Meta Pixel event parameters.
• Mapbox: when address search, a map, or directions are used and the feature is configured; it may receive the studio and device coordinates to calculate a route.
• Professional advisers, a competent authority, or a court where legally required or necessary to protect rights, security, and users.
• Expo and Apple APNs or Google FCM: for OPUS Studio mobile push when configured and you connect your phone. Browser push uses your browser’s push service. These services receive device routing data and notification content; client details are included only when you enable previews containing them.
• Sentry (Functional Software, Inc.): for mobile crash reporting, release health and sampled technical performance diagnostics. The mobile project uses Sentry’s EU region and excludes session replay and advertising tracking.

We do not sell or rent customer records. The sharing with Meta described above is optional and depends on your advertising consent. If the Service is reorganised, financed, or transferred, data may transfer with appropriate notice and safeguards.

Some infrastructure providers may process data outside North Macedonia. Where applicable law requires extra protection for such a transfer, we use a permitted mechanism and appropriate contractual or organisational safeguards. You can ask about the mechanism used for a particular provider at hello@opus.mk.

We keep data only for as long as it is needed for the purpose for which it was collected. The period depends on the type of data, account activity, the studio’s instructions, security risk, and legal obligations.

• Account and business data: while the account is active and then for a reasonable period for closure, export, disputes, or legal obligations.
• Appointments and client records: according to the studio’s needs and instructions, unless a longer period is needed for a legal obligation, security, or a legal claim.
• One-time codes: only for the short period needed for verification; codes are stored in hashed form and expire.
• Contact and support: until we respond and then for as long as reasonably needed to follow up on the request.
• Security, delivery, and audit records: for as long as needed for protection, diagnosis, evidence of actions, and legal obligations.

When a record is deleted, it may first be removed from active use. Limited data may remain in security or audit records and backups until their normal rotation, or be retained where law requires it.

OPUS Studio keeps necessary sign-in data and device notification choices in secure phone storage. The web dashboard keeps a local identifier for a connected browser. The push worker does not cache private studio pages. You can disable or disconnect alerts in your personal preferences and withdraw notification permission on your device. Signing out revokes that installation’s notification registration.

Necessary technologies support sign-in, security, and your preferences. Analytics and advertising technologies are separate and remain off until you accept them:

• Necessary session and security cookies on studio.opus.mk so you can sign in and remain securely signed in.
• opus_consent_v1 remembers your choice for up to 180 days across opus.mk and studio.opus.mk. A local storage signal informs other open tabs when your choice changes.
• PostHog: analytics cookies beginning with ph_ and local storage, only with analytics consent. Cookie expiry is configured to 180 days; local storage remains until consent is withdrawn or storage is cleared. On the opus.mk marketing website, we may record sessions with analytics consent to understand how you use the site. Input field values are masked. Web dashboard recording also requires analytics consent and masks text. These website tools are not included in the mobile app.
• Meta Pixel: _fbp and, when an ad-click identifier is present, _fbc, typically lasting up to 90 days and renewed with use. It loads only after advertising consent on OPUS marketing and registration pages. We do not load it on studios' public booking websites or private dashboard pages.
• The opus_locale cookie, set when you choose another language, which remembers that choice for up to one year.
• Local storage for your light or dark theme and certain interface preferences. These values stay on your device until you clear them.

Choose Necessary only, Accept all, or save separate analytics and advertising choices. Cookie settings are available in the opus.mk footer and studio web dashboard. Withdrawal stops future optional tracking; it does not undo prior processing. You can also clear browser storage. Blocking necessary cookies may prevent sign-in.

We use technical and organisational measures appropriate to the risk, including access control by studio and role, hashed one-time codes, attempt limits, encryption in transit, and audit records for significant actions. Access is limited to people and providers who need it for their work.

No system is completely secure. If you believe an account or personal data has been compromised, contact hello@opus.mk immediately.

Depending on the circumstances and applicable law, you may have the right to:

• be informed and obtain access to your personal data;
• correct inaccurate or complete incomplete data;
• request erasure or restriction of processing;
• receive data in a portable format where the legal conditions apply;
• object to processing based on legitimate interests;
• withdraw consent at any time without affecting earlier lawful processing; and
• not be subject to a decision based solely on automated processing that produces legal or similarly significant effects.

Send a request to hello@opus.mk. We may ask for reasonable proof of identity and the studio context so we do not disclose data to the wrong person. Some rights may be limited where law permits or requires retention.

In the mobile app, you can file an authenticated request through Settings → Delete account, including if you no longer have studio access. Requests are processed within 30 days. We remove or anonymise the personal account and related data that have no required lawful retention; studio records, ownership and subscriptions are reviewed as part of processing. Studio-controlled client records are handled under the studio’s lawful obligations and instructions. Uninstalling or signing out does not delete the account or diagnostic data already received.

You may also submit a request to the Agency for Personal Data Protection.

OPUS business accounts are intended for adults. The Service is not intended for a child to create a business account independently. Where a service is booked for a minor, a parent, guardian, or the studio should make the booking and ensure an appropriate legal basis for the data.

OPUS does not use data from the current booking flow to make a decision based solely on automated processing that produces legal or similarly significant effects for you. One-time codes, confirmations, and reminders are transactional messages. We do not send marketing without a separate lawful basis and a way to opt out.

We may update this Policy when the Service, providers, or law changes. We will change the date at the top and, where a change is material, provide additional notice through the Service or by email when appropriate.

For a privacy question, request, or complaint, email hello@opus.mk or call +389 77 826 333. If the matter concerns a particular studio’s data, include the studio name and enough detail to locate the request without sending unnecessary sensitive information.