How Projection Model handles personal data.

1. Scope And Effective Date

This Privacy Policy explains how Rigs on Move collects, uses, stores, shares, protects, and deletes personal data in connection with Projection Model, the public website, public signup, pricing and contact-sales forms, company workspaces, platform administration, support, billing, security, email, analytics, privacy request workflows, and related services.

Effective version 2026-05-30. This policy should be read together with the Terms and Conditions, Cookie Policy, Data Processing Addendum, and Subprocessors page. If a signed customer agreement includes a different privacy or data protection term, that signed agreement controls for that customer to the extent of the conflict.

Projection Model is a business-to-business SaaS platform for rig move planning. It is not designed for children, consumer social networking, advertising profiling, healthcare delivery, biometric identification, credit scoring, background checks, or processing sensitive personal data unless Rigs on Move expressly agrees in writing.

2. Roles: Controller And Processor

Rigs on Move acts as controller for personal data used to operate the platform relationship, including website visits, signup, account creation, platform administration, authentication, security, billing, PayPal subscription records, sales leads, support tickets, transactional email, analytics consent, legal acceptance records, privacy request records, and compliance records.

For customer-owned tenant planning records entered into a company workspace, Rigs on Move generally acts as processor on behalf of the customer company. The customer company is the controller for that tenant planning data and decides what data to enter, who may access it, how long it is needed, and whether it is suitable for its business purposes.

Some records can have mixed roles. For example, a support ticket may contain customer-provided tenant context, but Rigs on Move also uses the ticket for its own support, security, legal, and service-quality records. In those cases, each party is responsible for the obligations that apply to its role.

3. Personal Data We Collect

Account and company data may include company name, company code, user display name, username, work email, active status, group membership, permissions, password hash, password history records, MFA enablement status, encrypted MFA secret, password-change state, created and updated timestamps, and administrator actions.

Authentication and security data may include session records, hashed session tokens, MFA challenge records, password reset token hashes, login attempt results, login throttle and lockout records, hashed IP values, same-origin validation signals, audit events, security metadata, and records of password reset, logout, MFA, permission, admin, and platform actions.

Commercial and billing data may include selected plan, billing interval, subscription status, trial start and end dates, current billing period, plan price references, PayPal subscription identifiers, PayPal customer identifiers, PayPal webhook event IDs, webhook event types, webhook processing status, and raw PayPal webhook payloads needed to reconcile subscription status.

Sales, support, and privacy data may include contact name, work email, company name, requested plan, lead notes, support category, support subject, support message, privacy request type, privacy request status, due date, response notes, platform notes, support ticket sync status, Zammad ticket identifiers, Zammad ticket links, and related audit metadata.

Tenant planning records may include clients, salespeople, rig types, contract types, team types, equipment types, manpower positions, rigs, notes, current cycle dates, average stay days, average move days, release days, resource quantities, release rules, company equipment capacity, company manpower capacity, projection runs, generated moves, resource demand, shortages, coverage decisions, manual move overrides, idle resource reports, Moves vs Idle reports, exports, and inactive dependency warnings.

Website and technical data may include cookie consent preference, essential authentication cookies, public analytics events if analytics is enabled and consented to, browser and request metadata needed for security, operational logs, error logs, and device or network information available through normal web requests.

4. Sources Of Personal Data

We collect data directly from users when they sign up, log in, configure MFA, create records, run projections, export data, submit contact-sales forms, submit support tickets, request password resets, accept legal terms, or submit privacy requests.

We receive data from customer administrators when they create company users, assign permissions, update company details, configure subscription information, submit company privacy requests, or export and delete tenant data.

We receive billing and subscription data from PayPal when a customer approves, updates, pays, cancels, suspends, or fails a subscription payment. We may receive support-ticket status from Zammad if the support bridge is configured. We may receive email delivery responses from the transactional email provider.

5. Why We Use Personal Data

We use personal data to provide the SaaS service, create and administer workspaces, authenticate users, enforce permissions, process password resets, operate MFA, secure sessions, detect failed login patterns, prevent abuse, process subscriptions, reconcile PayPal billing events, send transactional emails, provide support, respond to privacy requests, maintain audit logs, and operate exports and deletion workflows.

We use tenant planning data to display, calculate, save, rebuild, and export planning records and projection results for the customer company. Projection outputs are generated from the customer's own data, assumptions, capacities, rules, and overrides.

We use sales lead and contact data to respond to pricing, custom plan, and enterprise inquiries. We use support data to answer operational questions, investigate issues, sync support tickets where configured, and maintain a record of requested actions.

We use security, audit, observability, and retention records to protect the platform, investigate suspected misuse, maintain service reliability, comply with law, enforce legal terms, prove legal acceptance, and resolve disputes.

6. Legal Bases Where GDPR Or Similar Law Applies

Where GDPR, UK GDPR, or similar law applies, we generally process account, workspace, subscription, support, and service records because processing is necessary to perform a contract with the customer or to take steps requested before entering a contract.

We process security records, audit logs, bot protection records, abuse-prevention records, operational logs, support quality records, and limited product improvement data based on legitimate interests in securing, maintaining, improving, and enforcing the service, except where those interests are overridden by individual rights.

We process billing, tax, legal acceptance, dispute, compliance, and regulatory records where necessary to comply with legal obligations or establish, exercise, or defend legal claims. We process optional public analytics only where enabled and where the visitor has chosen Allow Analytics through the cookie banner.

For tenant planning records, the customer company determines the legal basis for personal data it enters into its workspace. Rigs on Move processes those records as processor according to the customer company's instructions, the DPA, and the product workflows.

7. Cookies And Public Analytics

Projection Model uses essential cookies for company sessions, platform sessions, MFA challenges, and cookie consent. Session cookies are httpOnly, SameSite, and secure in production. Essential cookies are needed for authentication, security, and app operation.

The public website may use self-hosted Umami analytics only when public analytics are enabled and the visitor chooses Allow Analytics. The app is configured so Umami is cookieless and does not load inside authenticated tenant app pages in this version.

We do not use advertising IDs, retargeting pixels, cross-site behavioral advertising cookies, or third-party ad networks in this version. If those tools are added later, Rigs on Move must update the Cookie Policy and consent controls before they load.

8. Payment Data

Paid subscriptions are processed through PayPal. Projection Model does not store payment card numbers, card security codes, bank account numbers, or full PayPal credentials.

Projection Model stores subscription identifiers, plan mappings, status, billing interval, period dates, PayPal customer identifiers where provided, webhook event metadata, and webhook payloads needed to keep subscription status accurate and to resolve billing questions.

PayPal processes payment data under PayPal's own terms and privacy notices. Customers should review PayPal's notices before approving a PayPal subscription.

9. Transactional Email

Projection Model sends transactional email through Namecheap Private Email powered by Open-Xchange using Nodemailer and React Email inside the application. Transactional email may include password reset emails, security notices, and sales notification messages.

Email delivery logs store message type, provider, status, subject where needed, sent time, error text where needed, recipient domain, and a hashed recipient value. We avoid storing full recipient addresses in delivery logs where a hash is sufficient.

Email content sent through the email provider is processed by that provider for delivery, abuse prevention, reliability, and related email-service purposes.

10. Support, Zammad, And Ticket Records

Projection Model may create local SupportTicket mirror records for company support, sales, and privacy requests. The local mirror stores company scope, requester name, requester email, category, subject, message, linked sales lead or privacy request, sync status, and Zammad ticket identifiers or links where available.

If the Zammad support bridge is configured, full ticket conversations, email workflow, attachments, internal support notes, and ticket state may be handled in the separate Zammad support stack. Projection Model stores only the mirror and deep-link information needed for scoping, audit, retry, and operational visibility.

Users should not include unnecessary sensitive personal data, payment card numbers, health data, government identity numbers, passwords, MFA secrets, or confidential third-party data in support tickets or free-text notes.

11. Bot Protection And Abuse Prevention

Public signup, contact-sales, login, and password reset request flows may use self-hosted ALTCHA proof-of-work challenges. ALTCHA challenge records include action, challenge hash, signature hash, expiry, used timestamp, and related verification data.

Bot protection records are used to prevent automated abuse, spam, credential attacks, and fraudulent signups. They are not used for advertising or cross-site tracking.

Expired or used ALTCHA challenges are deleted during retention cleanup and may also be deleted when new challenges are created.

12. How We Share Personal Data

We share personal data with service providers that help us operate the service, including hosting and infrastructure providers, PayPal for subscription billing, Namecheap Private Email powered by Open-Xchange for transactional email, Zammad or the active support stack where configured, and self-hosted Umami infrastructure where analytics is enabled.

We may disclose data to customer administrators and authorized users according to the customer's permissions. We may disclose data to professional advisors, auditors, legal representatives, insurers, acquirers, affiliates, and authorities where needed for legal, security, corporate, compliance, or dispute purposes.

We do not sell personal data. We do not share personal data with advertising networks for cross-site behavioral advertising in this version.

13. International Transfers And Hosting Locations

Projection Model may be hosted on the infrastructure selected by Rigs on Move, such as Contabo or another active hosting provider. Support, email, payment, analytics, and backup systems may operate in different countries depending on provider configuration and deployment choices.

Where Saudi PDPL, GDPR, UK GDPR, or another transfer rule applies, Rigs on Move will use available safeguards appropriate to the transfer, such as customer instructions, contractual safeguards, provider terms, transfer assessments, or other mechanisms recognized by applicable law.

Customers should not enter data into the service if their own contracts or laws prohibit processing in the hosting or subprocessor locations used for the service, unless they have agreed a written deployment or data-residency arrangement with Rigs on Move.

14. Security Measures

Projection Model includes tenant scoping, database-backed permissions, same-company relationship checks, PostgreSQL row-level security for tenant business tables, hashed opaque session tokens, httpOnly session cookies, password policy enforcement, password history checks, login throttling, lockout, MFA-ready account security, encrypted MFA secrets, audit logging, same-origin request validation, ALTCHA bot protection, and structured operational logging.

Sensitive runtime secrets, SMTP credentials, PayPal credentials, Zammad API tokens, database passwords, security peppers, and MFA encryption keys are expected to be injected through environment variables or a production secret manager, not edited into the application or committed to source control.

No online service is perfectly secure. Customers must maintain secure devices, current browsers, careful user permission assignments, MFA where available, strong passwords, secure email accounts, safe export handling, and internal controls for downloaded files.

15. Breach And Incident Handling

Rigs on Move maintains audit and operational records to help detect, investigate, contain, and document suspected security incidents. If a personal data breach affects data for which Rigs on Move is controller, Rigs on Move will assess notification obligations under applicable law.

If a breach affects tenant planning records processed for a customer as processor, Rigs on Move will notify the customer without undue delay after becoming aware of the breach, using available admin, support, or contractual contact channels, so the customer can assess its own notification obligations.

Customers must promptly notify Rigs on Move of suspected account compromise, unauthorized access, incorrect permissions, exposed exports, or other security issues involving the service.

16. Retention

We keep personal data only as long as reasonably needed for the purposes described in this policy, the Terms and Conditions, customer instructions, legal requirements, security needs, billing reconciliation, dispute resolution, backup schedules, audit requirements, and product operation.

Current retention cleanup deletes expired company sessions, platform sessions, consumed or expired MFA challenges, consumed or expired ALTCHA challenges, and consumed or expired password reset tokens. It deletes non-converted or non-closed sales leads older than 365 days.

Current retention cleanup anonymizes older login attempts and audit logs after 730 days by removing or replacing identifying fields, and anonymizes older email delivery logs after 90 days by removing subject, error text, recipient domain, and identifiable recipient hash values.

Legal acceptance records, billing records, privacy request records, support ticket mirrors, tenant exports, backup records, and tenant planning data may be retained longer where needed for contract performance, legal compliance, security, dispute resolution, customer administration, or backup integrity. Deleted data may remain in backups until those backups expire or are overwritten.

17. Customer Controls

Company administrators can manage users, groups, permissions, active status, audit review, privacy requests, support requests, exports, and company-level records according to their assigned permissions.

Platform owners can manage companies, subscriptions, custom limits, sales leads, privacy request workflows, support ticket sync retries, operational status, company exports, and deletion workflows.

Customers should use exports before deleting data or ending a subscription. Customers are responsible for securely storing, transmitting, and deleting downloaded exports outside the service.

18. Privacy Rights

Depending on where you live and which law applies, you may have rights to request access, correction, deletion, restriction, portability, objection, withdrawal of consent for consent-based processing, and information about how personal data is processed.

Authenticated company users and company administrators may submit privacy requests through the in-product support or privacy request workflow where available. Other requesters may contact Rigs on Move through support. Rigs on Move targets a one-month response window for GDPR-style requests, subject to identity verification, request complexity, legal limits, and customer-controller instructions.

For tenant planning data controlled by a customer company, Rigs on Move may need to direct the request to the customer company or act on the customer's verified instruction. Some rights are not absolute; Rigs on Move or the customer may retain data where required for security, legal claims, billing, audit, compliance, or other lawful reasons.

19. Privacy Requests And Identity Verification

We may ask for information needed to verify identity, locate the correct company workspace, confirm authority, and protect other people from improper disclosure. We will not provide exports or deletion actions until we can reasonably verify the requester and scope.

When a company admin requests full company export or company deletion, Rigs on Move may verify the admin's authority, confirm the company code, and recommend exporting tenant data before deletion.

Privacy request records may retain requester name, requester email, request type, status, due date, response notes, platform notes, completion date, linked user, linked company, support-ticket reference, and audit metadata.

20. Automated Processing And Projection Outputs

Projection Model calculates rig move schedules, daily demand, shortages, coverage statuses, idle resources, Moves vs Idle, and related reports from customer-entered assumptions and resource data.

These calculations do not by themselves create legal or similarly significant effects for individuals. The customer remains responsible for reviewing all results and deciding whether and how to use them in operations, staffing, equipment allocation, client commitments, or other business decisions.

Rigs on Move does not use tenant planning data for advertising profiling or employee scoring.

21. Data Quality And Sensitive Data

Customers are responsible for ensuring tenant planning records are accurate, complete, up to date, lawful, and limited to what is necessary for rig move planning and related administration.

Users should not enter passwords, MFA secrets, payment card data, health data, biometric data, government identity numbers, criminal records, children's data, or other sensitive personal data into free-text notes, support messages, rig notes, sales lead notes, or planning records unless Rigs on Move has expressly agreed in writing to support that data type.

If sensitive data is accidentally submitted, customers should notify Rigs on Move promptly and should use available deletion or correction workflows where appropriate.

22. Changes To This Policy

Rigs on Move may update this Privacy Policy to reflect product changes, provider changes, legal changes, security changes, or operational changes. The effective version at the top of the page identifies the current public version.

Material changes may be communicated through the service, email, public legal pages, support channels, or other reasonable notice. Continued use after the effective date means the updated policy applies to future processing.

Historical legal acceptance records may preserve the document type, version, timestamp, user, company, and hashed IP value associated with acceptance of legal terms.

23. Contact

For privacy, security, support, billing, export, deletion, or data protection questions, contact Rigs on Move through the support channel, in-product privacy workflow, or contact method made available in the service.

When contacting us, include enough information to identify the relevant company workspace, user account, request type, and desired action. Do not send passwords, MFA codes, payment card numbers, or unnecessary sensitive data.

If a data protection officer or formal representative is appointed for a jurisdiction, Rigs on Move will make the relevant contact path available through the service, legal pages, customer agreement, or privacy workflow.