Privacy Policy
Effective date · 17 October 2026 · 2026-10-17-v6
1. Controller and contact
The controller for Offset Pilot account and service personal data is INŽETEH, inženiring in tehnično svetovanje, Sergey Tolstyakov s.p., Maistrova ulica 16, 1241 Kamnik, Slovenia. Business registration number: 7405014000. Slovenian tax number: 32300433 (not an EU VAT identification number). Telephone: +38669634858. General email: info@offsetpilot.com; support, complaints and privacy: support@offsetpilot.com.
For privacy requests, contact support@offsetpilot.com. This policy describes the service at offsetpilot.com; separately hosted payment and identity-provider pages have their own notices.
2. Data we process and where it comes from
- Account and authentication: email, account identifier, authentication methods, sessions and security records from registration, sign-in and the authentication provider. Supabase Auth supports password and email-code authentication and optional Google sign-in. Google sign-in provides identifying account information; administrator two-factor authentication also involves authenticator enrolment and verification data.
- Projects: saved project names, offset data, tool descriptions, libraries and preferences supplied by you.
- Billing and access: Stripe customer, checkout, subscription, invoice, payment and refund identifiers, amounts, currency, refund and subscription-cancellation status, plus promotional access expiry and grant/revocation records. Withdrawal statements include the consumer name, purchase reference, receipt status and original submission time. Repeat-purchase/withdrawal counts, review notes, administrative audit and time-limited purchase restrictions are used for human abuse review. We exchange purchase identifiers, refund instructions and subscription-cancellation instructions with Stripe to process an approved refund operation and verify its outcome. Administrator confirmations, processing attempts and completion or interruption records are retained as necessary evidence of the action. Receipt of a consumer withdrawal notice is recorded separately from refund completion. Stripe sends relevant payment events to us. Card details are entered on Stripe-hosted pages and are not entered in the editor.
- Billing profile: billing name (full name or first and last name), optional company, country, address lines, city, postal code, region and optional VAT ID supplied in My account. We may send saved details to Stripe to assist Checkout. From a verified completed Checkout, we receive billing information, the company field and tax IDs provided there. If you select “Update my billing details after checkout”, we use those confirmed details to update your profile once for that purchase, without overwriting a later manual edit. We do not update the profile from an abandoned or unsuccessful purchase. Your login email remains separate.
- Communications and requests: account and service emails, delivery status, support correspondence, privacy/deletion requests and confirmations, and identity-verification information needed to handle them.
- Security and technical information: request/error details, IP addresses, timestamps, technical identifiers and administrative action records needed to protect and operate the service.
- Contract evidence: registration and purchase acceptance times, document versions, selected plan and price and immutable copies of the purchase terms and paid invoice confirmation, the customer billing details recorded for the purchase, the optional profile-update choice and a minimal record of profile synchronisation.
OFS import and editing are performed in your browser. Saving to your account transmits project data to the service. Server-side export transmits the project when you request an export. Browser-local drafts and settings may remain on your device until cleared. Avoid unnecessary personal or confidential information in project names and descriptions.
3. Purposes and legal bases
Account creation, requested project storage, subscriptions and essential service communications rely on performance of our contract or pre-contractual steps at your request (Article 6(1)(b) GDPR). Necessary business contact details where you represent another contracting party rely on legitimate interests in administering that business relationship (Article 6(1)(f)).
Tax and accounting records and handling statutory privacy or consumer requests rely on legal obligations (Article 6(1)(c)). Necessary security monitoring, human review of documented purchase/refund abuse, troubleshooting and evidence needed to establish, exercise or defend legal claims rely on legitimate interests (Article 6(1)(f)), subject to necessity and balancing against your rights. These bases do not authorise unrelated marketing.
The optional Checkout profile-update setting is an instruction to reuse confirmed billing details for future purchases, not marketing consent or a condition of purchase. Clearing it does not prevent processing or retaining information necessary to complete and document that purchase. Acceptance of Terms or acknowledgement of this policy is not marketing consent. Where processing is based on consent, it can be withdrawn without affecting prior lawful processing. Required account and billing information is needed to provide the relevant functionality; if it is not supplied, we may be unable to create the account, complete the purchase or handle the request. We do not use personal data for automated decisions producing legal or similarly significant effects; access rules reflect subscription or promotional status. Repetition indicators do not automatically reject withdrawal or impose purchase restrictions. A human administrator decides any restriction on future purchases, and you may ask support to review it.
4. Recipients and international processing
We use Cloudflare for hosting and database storage, Supabase for authentication, Brevo for transactional emails, Stripe for payments and subscription management, and Google when you choose Google sign-in. Necessary data is shared for the relevant purpose. Authorised personnel and advisers may access information needed for support, security, accounting or legal obligations; competent authorities may receive information where required by law.
Service providers act as processors for processing carried out on our instructions, subject to applicable contractual terms. Payment and identity providers also act as independent controllers for their own fraud prevention, regulatory obligations and account services. Provider groups include entities outside the EEA, including in the United States and Singapore; using the service does not imply that all data stays in Slovenia or the EEA.
Transfers outside the EEA must have a lawful basis under Chapter V GDPR, such as an applicable adequacy decision or standard contractual clauses with appropriate supplementary safeguards. You may ask us for information about the safeguards applicable to your data and a copy, with necessary confidential information redacted. Provider notices: Cloudflare, Supabase, Brevo, Stripe and Google.
5. Retention and account deletion
Active account data and saved projects are retained to provide the account until you delete them or the account, subject to legitimate security or legal needs. Deleted account projects, trash, libraries, billing profile and settings are removed from active service storage when deletion completes. Clearing server data does not clear files or drafts held on your device.
Delete my account requires explicit confirmation and either verification of the current password or, for eligible accounts without a password, a time-limited code sent to the account email. Google sign-in alone does not automatically authorise deletion. Successful processing cancels current subscriptions immediately, ends paid access, removes active account content and deletes the Supabase login. If processing fails, a request is retained for manual follow-up and you are notified; a pending request is not confirmation of completion. Deletion does not automatically refund payments.
Relevant statutory financial records are generally kept for 10 years after the end of the year concerned under Slovenian rules. Contract and acceptance evidence is kept for the contract duration and for applicable claim limitation periods, disputes and legal holds where necessary. Support and privacy-request records are kept while the matter is handled and as necessary to demonstrate compliance or resolve related claims. Security and delivery records are retained for the period necessary to investigate incidents, prevent abuse or resolve delivery problems, then removed or anonymised when no longer justified. Restriction matching uses the account identifier and a hash of the normalised email; the hash remains personal data and is not treated as anonymous. Restrictions expire after their stated duration, no longer than 365 days, unless separately reviewed and renewed. This future-purchase restriction matching does not use browser fingerprinting or payment-card details. The separate one-time trial eligibility check is described below. Necessary review and restriction evidence is retained only under the claim/compliance criteria above. These purposes do not justify retaining unrelated project content.
Provider backups and logs follow their applicable retention and rotation arrangements. Removal from active storage may precede expiry of backup copies; any retained copies remain subject to purpose, access and retention restrictions. A legal hold may extend retention only for relevant records. Contact us for retention information about a specific record or request deletion of data not subject to an overriding lawful retention obligation.
6. Your rights and complaints
Subject to legal conditions, you may request access and a copy, rectification, erasure, restriction and data portability. Where portability applies, relevant data is provided in a structured, commonly used, machine-readable format. You may object to legitimate-interest processing; we stop unless compelling overriding grounds or legal claims justify continuation. You may withdraw consent where consent is the basis.
You can edit current Billing details in My account. Your personal-data export includes your billing profile and recorded contract billing details. Updating the profile does not rewrite an existing contract or invoice; contact support for any rectification required in historical records, subject to applicable legal record-keeping requirements.
Send requests to support@offsetpilot.com. We may proportionately verify identity before releasing or changing data. We normally respond within one month of receiving a request. Where legally permitted, complexity or the number of requests may justify up to two additional months; we inform you within the first month and explain why. Requests are normally free, subject to the GDPR rules on manifestly unfounded or excessive requests.
You may complain to the Slovenian Information Commissioner (Informacijski pooblaščenec), www.ip-rs.si, gp.ip@ip-rs.si, or the competent authority where you live, work or where the alleged infringement occurred. You do not have to contact us before complaining.
7. Cookies and browser storage
Your selected SL/EN language is stored in a functional cookie and browser preference, and recorded for the purchase to provide the corresponding contract documents and confirmation. English is the default. The editor uses authentication cookies for requested sign-in functionality and browser storage for preferences, local drafts and editor state. Session duration depends on the authentication provider and session renewal; local preferences and drafts remain until replaced or cleared. You can sign out and clear browser storage, which may remove local drafts and require signing in again.
The editor does not currently include advertising or optional analytics tracking. If non-essential tracking is introduced, any legally required consent will be obtained before it runs. Stripe-hosted checkout and portal pages and Google sign-in are separate provider services with their own cookie and privacy information.
8. Contract records and policy updates
Registration records include email, acceptance time/method and the Terms and Privacy versions; after email confirmation they are linked to the account identifier. Purchase records include document versions and full copies delivered as a PDF, acceptance, plan, price, Stripe identifiers, recorded customer billing details, the profile-update choice and paid invoice confirmation. They support contract fulfilment, disputes and legal compliance under the retention criteria above. Existing purchase copies are not replaced by later edits.
Material changes are communicated appropriately, including directly where required. A new policy does not expand processing permissions retroactively or replace consent where consent is required. The effective date and version appear above.
Trial subscription records
For a card-linked Pro Editor Promo trial, we retain the trial contract, recorded acceptance, trial start and end, first scheduled charge and recurring plan, Stripe customer and subscription references, cancellation or withdrawal statements, and confirmation and reminder delivery records to perform the contract and meet legal obligations. Stripe stores the linked card; Offset Pilot does not store full card numbers or security codes. Existing retention periods and privacy rights apply to these records.
One-time trial eligibility
To enforce the once-per-account and payment-card trial and prevent repeat registrations from resetting eligibility, we retain hashed account identifiers, hashed normalised email identifiers and a hash of the Stripe card fingerprint, together with trial contract and subscription references, environment and recording date. No full card number, CVV or cardholder name is stored for this check. These are pseudonymised personal records, not anonymous data. The purpose is offer administration and prevention of repeated trial use; the basis is our legitimate interest in enforcing the disclosed offer, subject to your applicable objection and other privacy rights. Minimal eligibility markers may remain after account deletion while this one-time offer operates. We review their necessity and remove them when no longer required, unless another legal retention obligation applies. Stripe wallet tokens and replacement cards may have different identifiers, so matching is not a universal identification of a person. Matching prevents a repeated trial, not an otherwise permitted paid purchase or a lawful refund. Contact support for review of an incorrect match. Your personal-data export includes eligibility records associated with your account or email.
