PlanToBill
Language

Privacy Policy

Version 2026-10-04.1. Effective 4 October 2026.

Who is responsible

Apexia IT j.d.o.o., Mala Rakovica, Ulica za Gaj 25, Samobor, Croatia, OIB 66215203143, operates PlanToBill. Contact [email protected] for privacy questions or requests. Apexia IT is the controller of account, authentication, service administration and security information. For personal data entered by a customer about its buyers, staff or other contacts, the customer ordinarily acts as controller and Apexia IT as processor under the DPA. A person whose details were entered by a customer should normally contact that customer; we will assist the responsible controller with requests.

Information and purposes

We receive account email, optional profile/contact details, language and user preferences, account activity, authorization settings, calendar and calculation content, support correspondence and submitted privacy requests. Authentication uses password hashes, session records, verification/reset tokens and, when enabled, encrypted MFA secrets and recovery-code hashes. User SMTP configuration includes server, sender and account identifiers and an encrypted password. Security and operational records can contain timestamps, IP addresses, user agents, internal identifiers and actions. Hashing an identifier reduces direct exposure but does not necessarily anonymize it.

We process information to provide accounts and requested features, send service messages, authenticate users, maintain security, investigate problems, answer requests, comply with obligations and establish or defend legal claims. Where the individual is our contracting customer, necessary service processing rests on Article 6(1)(b) GDPR. For a business customer's representatives, administration, support and security ordinarily rest on legitimate interests under Article 6(1)(f): operating and protecting the business service and communicating with authorized contacts. Legal obligations rely on Article 6(1)(c) where applicable. Required account information is necessary to create and secure an account; without it we cannot provide the account. Optional profile fields are optional. No advertising, Google Analytics, Meta Pixel or AdSense integration is included in this release. There is no advertising consent banner. We do not use these data for solely automated decisions with legal or similarly significant effects.

Recipients and international processing

Authorized Apexia IT personnel access data as needed for their duties. The external-services register identifies infrastructure providers and their roles. Primary data are hosted in Croatia. Backups are stored with Hetzner Online GmbH using S3 Object Storage in Germany for 180 days. This is a separate backup system, not a claim that application object storage uses an implemented S3 driver.

System registration, verification and reset emails use Apexia IT own mail infrastructure in Croatia. Invoice emails use the sending customer's own configured SMTP provider. That provider and recipients receive the addressed message and its attachments; their location and independent processing depend on the customer's choice. VIES checks transmit VAT country/number and, where supplied, company name and the issuer's VAT identifiers to the official EU VIES service. Responses can include validation, registered name/address and matching information.

Information may also be disclosed to authorities when legally required and to professional advisers where necessary and subject to appropriate safeguards. The confirmed primary and backup locations are within the EEA. Any additional transfer outside the EEA must be assessed and use an applicable GDPR Chapter V mechanism before processing is introduced; customer-selected mail routing can involve other countries. Obtain relevant details before choosing that provider.

Retention and protection

Account information is retained while needed to provide and administer the account. Closure requests receive a review of contractual obligations, legal holds, claims and applicable record-retention duties. We explain any data kept and the applicable reason; account closure is not an automatic deletion of all business records. Authentication sessions expire after 15 minutes of inactivity or at most eight hours; expired records and used/expired reset tokens are cleaned hourly. Expired email verification secrets are cleared on the same schedule. Unverified registrations without business or personal workspace data are removed after 30 days. Email-log message content and recipient details are removed after 90 days; minimal delivery metadata remains with the business record. Administrative security audit records are normally removed after 365 days. A documented legal hold can suspend those mail/audit removals and is subject to review. Invoice audit records follow the associated business record's lawful retention rather than an arbitrary global expiry. Service metric history is normally retained for 30 days. Container technical logs rotate within three files of up to 10 MB each, so their duration depends on traffic; operational reviews address unnecessary retained logs. Temporary processing uses memory or bounded temporary storage cleared when the container is recreated. Orphan files are reviewed separately from live records. Infrastructure backups expire after 180 days. Deleted data can remain in these restricted recovery copies until expiry; restoration must reapply the deletion record before restored data return to ordinary processing. No backup extension should be inferred merely from an account closure request.

Security measures include scoped authorization, protected sessions, password hashing, authenticated encryption of MFA/SMTP secrets, request validation and restrictions on uploaded files. Safeguards reduce risk but do not guarantee that every incident is impossible. Security reports go to [email protected].

Rights and requests

Subject to applicable conditions, individuals can request access, correction, erasure, restriction, portability and object to processing based on legitimate interests. Where any processing relies on consent, that consent may be withdrawn without affecting the lawfulness of earlier processing. These rights can be limited by legal duties and the rights of others. A data export is not a right to another customer's confidential information or authentication secrets.

Send a request to [email protected], identifying the relevant account and right, or use the profile Privacy Center to export account/calendar/calculation data as JSON or request account closure. Business documents and other people's data are not automatically included in that personal export. We may request proportionate information to verify identity; do not email passwords, MFA secrets or unnecessary identity documents. We respond within the GDPR timeframe, normally one month, and explain any permitted extension or refusal. Individuals may complain to the Croatian Personal Data Protection Agency (AZOP, https://azop.hr/) or another competent EU/EEA supervisory authority. Contacting us first is optional and does not restrict the right to complain.