VaskLogg privacy

Publisher and controller

VaskLogg is an app under the Kot Maurycy brand. Publisher: driwa.pl Łukasz Driwa, ul. Maurycego Beniowskiego 4A, lok. 9, 80-388 Gdańsk, Polska, NIP 5842685188, CEIDG, tel. +48 505 369 535. Support and data protection matters: app@kotmaurycy.pl. The previous address, kontakt@kotmaurycy.pl, remains active for users of earlier versions.

The publisher is the controller of data received through support enquiries and data processed for its own accounting, handling of rights, security and protection of legal claims within the scope described below. The user or business using the app determines the purposes and rules for using customer and team member data in the local archive. The app does not give the publisher remote access to that archive or automatically send it to the publisher.

Archive on your device

Jobs, client details, photos, notes, work time, templates, logo and drafts are stored on your device. The app also keeps the previous valid save and information used to recover interrupted photo saves. It does not send the archive to the publisher. There is no VaskLogg account, advertising or third-party analytics module. The publisher has no remote access to your archive and cannot recover it for you. Service prices, payments and refunds, rates, team settlements, correction history and saved statements also stay on your device and in backups or exports you create. Team financial data is excluded from cleaning reports and shared job files. You must select it separately when preparing a statement for your accountant.

Accounting and team records

Business details, internal staff references, actual hours, confirmed net pay or subcontractor invoice amounts, payments and correction history stay on your device and in your backups. Accounting exports may contain confidential staff data. Choose recipients carefully. An individual statement filters records to that person. VaskLogg does not require personal tax identifiers, bank account numbers or health records. Exported files have no separate password; protect copies outside the app yourself.

Team schedule

Schedules store people, agreed hours, availability, instructions, shared versions and reviewed work locally and in full backups. Do not record medical reasons for absence or unnecessary staff data. The recipient receives a selected period for one person. The app file may contain the necessary jobs; you explicitly choose whether to include instructions in a PDF or message. Review them before sharing. Files have no separate password, do not confirm identity or delivery, and can be forwarded. An update does not remove earlier copies.

Camera, photos and calendar

The camera documents a selected visit. The system photo picker gives the app only the images you select. Photo import removes GPS metadata; library originals remain unchanged. Event import requires full iOS calendar access, but only the selected event is copied to the archive, without guests, attachments or private notes. You confirm calendar export in Apple’s event editor. You can change permissions in iPhone Settings and plan work manually without granting them. We do not collect background location or record audio.

Files, messages and collaboration

You choose the recipient and sharing service. Reports include client-facing information and selected photos. A photo ZIP contains only your selection; filenames do not automatically add the client’s name or address. A job file or message contains instructions for one visit, with the client’s phone number optional. Private client notes are not automatically included; check what you write in instructions. The job owner must review returned work. A full backup also contains private notes and drafts. New full backups are encrypted with your chosen password. Reports and other export files have no separate password or remote revocation. Recipients can keep their own copy. Sharing does not confirm delivery. Device system backups may include the archive, depending on Apple settings.

File protection and deletion

The archive and photos use iOS file protection requiring an unlocked device. Free space is checked locally without sending the result. Temporary exports older than 2 days are removed on app launch; an interrupted ZIP is not a completed file and is cleaned up on the next launch. You can also remove temporary files in VaskLogg settings. The archive remains until you delete it. Deleting the app removes local data; iOS offloading may retain it. Delete your own exports, calendar entries and cloud backups separately. Deleting data does not cancel a subscription. We do not guarantee the security of an unlocked phone or services you choose for sharing.

Apple and purchases

StoreKit retrieves Apple’s offers and verifies Pro access on the device. Apple handles payment; we do not receive your card number or work archive. Apple may provide the publisher with sales and subscription reports, including a subscriber identifier and country or region, and diagnostics depending on your Apple sharing settings. We do not link these to client archives. Settlement data is used for accounting and required settlements, and available technical reports for fixing faults. Apple’s privacy policy explains its processing. We do not carry out our own profiling or automated decisions with legal effects.

Optional local diagnostics

Diagnostics are off by default. You can enable them in Settings → Privacy and help. The app stores locally up to 200 technical events from the past 7 days and up to 7 daily summaries from Apple MetricKit: CPU time, peak memory, disk writes and hang count. It excludes photos, names, addresses, contact details, amounts, customer IDs, job content, file paths and raw crash reports. The file is limited to 128 KB, protected by iOS and excluded from app backups. We use no diagnostics server or third-party SDK. Exports contain app and OS versions and relative event ages, with no device identifier. Enabling diagnostics or exporting a file does not send it to the publisher; you choose the recipient in the system share sheet. Files you voluntarily send to support are handled under the support rules below. Turning diagnostics off deletes the app’s local file and stops recording. Apple system diagnostics are managed separately in iOS settings.

Support and lawful bases

When you send a support request, we receive your email address, your name or first name if visible in the message, its content and the attachments you choose. Optional attachments may include a screen preview and information about the app and iOS versions, screens used, performance, crashes or other diagnostic events. Merely using the app, enabling diagnostics or preparing a support request does not send this information to the publisher.

Provide only the information needed for the matter. Before sending, remove or obscure customer and team member details. Do not send a full archive, passwords, access codes, health information or unnecessary third-party data. An ordinary support request does not require a screen preview or diagnostic file.

We process data necessary to perform our contract with you or take steps at your request before entering into a contract under Article 6(1)(b) GDPR. Article 6(1)(c) GDPR is the basis for complying with legal obligations, including applicable complaint-handling, tax and accounting obligations. For other necessary processing, we rely on Article 6(1)(f) GDPR: our legitimate interests are responding to enquiries, communicating with people representing business customers, identifying the cause of a reported error, protecting app security, and establishing, exercising or defending legal claims.

Providing contact details and a description is voluntary, but without them we may be unable to reply or investigate the matter. Support requests are not used to send marketing.

Screen previews in support reports

After you separately enable the preview feature, the app may prepare a single image of a supported screen when you choose to report a problem. It does not record the screen, create an image history or send anything in the background. Areas marked as private in the app are obscured before the image is saved. If a preview is unavailable, you can send a description alone. Always review the image before sending it: you can obscure further areas, remove the image or choose not to attach it. Automatic obscuring does not replace your own review of the content.

The preview is saved locally, separately from the job backup. It expires after 24 hours; the app deletes an expired image the next time it launches or the draft is resumed. Turning off the preview feature deletes the local image.

The draft description remains locally until it is replaced by a new report or VaskLogg receives a 'sent' result from the system mail app. Merely opening the mail app, saving the message as a draft, cancelling or unsuccessfully attempting to send it does not delete the draft in VaskLogg. When another mail app is used, VaskLogg does not receive the sending result, so the draft may remain until replaced.

Optional technical information includes the app and iOS versions and the screen name. If diagnostics were enabled beforehand, it may also include up to three recent screen names. It does not include job content, customer details or a device identifier. The mail app receives only the attachments you select. Our support team receives them only after you send the message.

The shake gesture is disabled by default and does not itself create a preview. Passing a message to the mail app or receiving a 'sent' result does not confirm delivery. You manage copies and attachments saved separately in Mail or Files within those apps.

Support data retention

We retain ordinary support correspondence until the matter is closed and for no more than a further 12 months. We delete unnecessary attachments sooner. If particular data is necessary to document a complaint, proceedings or a claim, we retain only what is needed until the matter is concluded and the applicable limitation period has expired. This does not justify keeping all support requests for the longest possible period.

These rules cover active email and working copies under the publisher's control. Technical disaster-recovery backups are used to restore data after a failure, rather than for day-to-day handling or new purposes. Deleted data may remain in them until the backups are replaced through the retention cycle. SEOHOST's public documentation describes a standard backup service covering the previous 60 days for the entire service, including email. This does not mean that every version of a file can be recovered or that every trace is deleted immediately. When the agreement with SEOHOST ends, active data is subject to deletion without delay, subject to statutory exceptions; under the agreement, the final backup is deleted no later than six months after that agreement ends. This is a separate period from the ordinary retention of correspondence. When restoring data, we take earlier deletion instructions into account.

We retain tax and accounting documents for the periods required by the applicable legislation. For tax records, this is generally five years from the end of the year in which the tax payment deadline fell; an applicable suspension or interruption of the limitation period may extend it. Accounting documents may have a separately calculated retention period. After the relevant period, we delete the data or permanently anonymise it.

You or your business determine how long to retain the local archive. The publisher cannot remotely delete copies held by users or their recipients.

Recipients and external services

The publisher handles support manually. Hosting and email are provided by SEOHOST sp. z o.o., based in Poznań, which processes data on our instructions under a data processing agreement. The agreement's annex identifies the infrastructure providers DATASPACE P.S.A., EXEA S.A. and OVH sp. z o.o., which have their registered offices in Poland, and the support system provider Quality Unit s. r. o., whose registered office is in Slovakia, within the scope of their tasks for SEOHOST. This does not mean that every support request is automatically sent in full to each of these entities. The agreement provides for notification of changes to subprocessors and an opportunity to object. We limit access to what is needed for the particular task.

Data may also be received by authorised people actually involved in the work, necessary IT providers, accountants and advisers, and authorities legally entitled to receive it. We regulate our relationships with service providers processing data on our behalf in accordance with Article 28 GDPR. We handle correspondence on the publisher's computer, including through Apple Mail.

The app does not automatically send the archive to the publisher, advertising systems or AI training systems. Apple and the services you choose for email, export or file storage operate under their own terms and may also process data outside the EEA. Apple's practices are described in its privacy policy. For services covered by our data processing agreement, a transfer to a third country requires documented instructions and an appropriate basis under Chapter V GDPR, such as an applicable adequacy decision or standard contractual clauses. Information about the relevant recipients and safeguards used, including how to obtain a copy of those safeguards, is available by contacting the publisher.

This policy concerns VaskLogg. The kotmaurycy.pl website has a separate policy covering its form and analytics and advertising tools. Those tools are not analytics modules in the iOS app; the standalone product pages at /apps/vasklogg/ do not currently contain them.

Your rights and contact

For data processed by the publisher, you can exercise your rights of access and to obtain a copy, rectification, erasure or restriction of processing, and — where the legal conditions are met — data portability. You can object to processing based on legitimate interests on grounds relating to your particular situation. If particular processing is based on consent, you can withdraw that consent without affecting the lawfulness of earlier processing. These rights are not unconditional; we assess requests under the applicable legislation. We verify identity only to a reasonable and necessary extent, without collecting excessive data.

We respond without undue delay, generally within one month of receiving a request. If the law permits an extension because of the complexity or number of requests, we will inform you of the extension and its reason within that month. You can complain to the President of the Polish Personal Data Protection Office (UODO) or another competent authority, such as Datatilsynet in Norway or Denmark, or IMY in Sweden. Contacting us first is not a condition for making a complaint.

If UK data protection law applies to a particular matter, you also retain the applicable rights under the UK GDPR and the Data Protection Act 2018, and the right to complain to the ICO. You can send a data protection complaint to the publisher's email or postal address. You do not have to use a form or identify a legal provision. Under the UK complaints procedure, we acknowledge the complaint within 30 days, investigate it appropriately, keep you informed of progress and communicate the outcome without undue delay. This process is separate from a request to exercise your rights and does not extend the response period for that request.

Send requests concerning an archive maintained by a cleaning business to that business. The publisher cannot remotely correct or delete its local data. Separately, you can manage copies, permissions and sharing in Apple's settings and in the services to which you have sent files.