Logic Gates Privacy Policy
Version: 1.2.0
Last updated: 2026-11-12
This Privacy Policy covers Logic Gates across releases. Feature availability and information handling can differ by release; the relevant sections identify those differences. A planned feature described here applies only when it is available in your release. This scope does not remove obligations for older releases. This notice describes information handling; acknowledging it does not grant consent for an optional purpose. Updates do not retroactively authorize processing or change how information was handled before their effective date. Previous versions of this document remain publicly available in its revision history.
1. Who is responsible and what this notice covers
Logic Gates (bundle identifier com.logicgates) is developed by Aleksander Jałtuszyk, based in Poland. For privacy questions or requests, contact alekgameshelp2@gmail.com.
Aleksander Jałtuszyk is the controller for handling support correspondence and deciding to deliver the app’s legal documents through the hosted service described below. Providers also process information for their own purposes under their applicable notices. This is separate from circuit data that remains on your device.
This notice describes the digital-circuit app for iPad and iPhone, local projects, user-directed file import and export, online legal-document checks and any correspondence you choose to send to the developer. Features available to you depend on your installed build; older builds may lack file actions, Trash or online legal refreshes. Visiting the product or legal website in a browser is also covered by the website’s separate Privacy Policy, linked from its legal hub.
2. Local circuits, file imports and sharing
Logic Gates stores circuits, projects, folders, Trash, workspace tabs, preferences and recovery saves in the app’s container on your device. Simulation, circuit inspection, truth tables and Karnaugh-map calculations run locally. The app does not automatically send these projects or results to the developer.
The current app has no accounts, advertising, analytics or tracking SDKs, automatic cloud synchronization, developer-hosted project uploads, app telemetry or payment processing. It does not send an editor usage history, app-specific device identifier, circuit content or simulation results to the developer unless you choose to share content with the developer yourself, for example in a support email. It does make the limited legal-document requests described in section 4. No advertising or analytics consent is requested because those activities are not part of the current app.
Local storage supports the functionality you request, such as reopening your workspace, remembering preferences and recovering work. It is not used to build an advertising profile. Touch and Apple Pencil interactions control the editor on your device; they are not sent to the developer as behavioral telemetry.
Where your build offers file actions, a native .logicgates export contains the selected circuit and the circuit definitions it needs, including their names, labels, components and connections. It is not a complete workspace backup: it excludes app preferences, Trash, recovery saves, legal-acceptance records and live simulation state. Review names, labels and included definitions before sharing, because they can contain information you entered yourself. The file is readable project data, not a password-protected archive.
Export opens the system share sheet. You choose whether to save the file, send it to someone or use another available action. A destination such as iCloud Drive, an email app or another file provider may upload, retain or otherwise process the file under its own terms, settings and privacy notice, including outside your country. The developer does not receive a copy merely because you export it. Choosing the developer as a recipient is covered by the support section below.
Import reads a file you choose through the system file picker and, if supported and valid, adds independent local circuit copies rather than replacing existing projects. A file provider may retrieve that chosen file from its own online storage. Importing does not give the developer access to that service or create ongoing synchronization with the source file. The original file remains separate from the imported copy.
3. Trash, recovery and deletion
In builds with Trash, deleting a project or folder moves it into local Trash, including a deleted folder’s contents. Trash has no automatic expiry. Items remain there until you restore them, permanently delete them through the app or remove the app’s local data. The app can prevent deletion while another retained circuit depends on the item. Restoring a circuit can also restore required definitions from Trash.
Local recovery data can include earlier catalog saves, previous project states, legacy saved data and copies preserved when a saved file cannot be read. Permanently deleting an item from current Trash may still leave an earlier copy in local recovery data. Earlier builds without Trash can also retain deleted projects in recovery saves. Recovery copies are not a separate cloud service and are not a guarantee that work can always be recovered.
To remove the app’s local data from an iPad or iPhone, use the system’s Delete App action. Offload App can retain documents and data, so it is not equivalent to deletion. Deleting the app also removes local preferences and any local legal-acceptance record. The developer cannot remotely retrieve, restore or erase circuits that remain only on your device.
Device backups, including any copies of app data, follow Apple’s services and your device/backup settings. They are separate from the app’s recovery saves. Removing a project or deleting the app does not necessarily remove earlier device backups; manage those through the relevant Apple or computer-backup controls. Restoring a device backup may restore old app data.
Exported files, original files used for import, and copies held by recipients or file providers are separate from the app’s container. Deleting a project, clearing its Trash entry or deleting the app does not delete those copies. Manage them through the relevant Files location, provider or recipient; the developer cannot remotely recall a file you shared.
4. Online legal documents and local acknowledgement
The app checks for current terms and privacy documents through a minimal HTTPS GET request to the legal manifest on alekjaltuszyk.xyz. Automatic checks run on startup and when returning to the foreground, subject to rate limits; you can also request a manual refresh. These checks can occur before you accept the terms. They do not send cookies, app account identifiers, circuit content, analytics events or acceptance receipts.
The host, GitHub Pages, receives your IP address and ordinary request metadata, such as the requested URL, request time and protocol headers needed to serve the response. GitHub logs IP addresses for security and may retain service/security logs under its own retention criteria. The developer does not use these requests to track your editor activity. There is no promise that retrieving the documents is anonymous or that the host keeps no logs. See GitHub’s Privacy Statement for its processing, retention and international-transfer information. Processing may take place outside your country, including outside the EEA; applicable safeguards depend on the provider and arrangement. You can contact the developer about safeguards for this delivery service.
Complete verified documents are cached locally. When offline or a check fails, the app uses the last verified copy or its bundled fallback. It cannot detect a remote change until a successful online check. The cached copy identifies the version available on that device; it may differ from the newest website copy.
First-run onboarding requires agreement to the Terms of Use and acknowledgement that the Privacy Policy has been read before entering the editor. A changed document prompts a new review and acknowledgement or agreement as appropriate. The app keeps the accepted document versions, content digests and acceptance time locally. That record is not sent to the developer. Downloading a document never accepts it for you.
Acknowledging this notice is not consent to optional data collection, and it does not turn on tracking, telemetry or project uploads. If you do not agree to the terms, do not continue into the editor. You can stop using and delete the app. Resetting its local acceptance record does not transmit that record or delete existing projects. The document cache and acceptance record remain on the device until replaced or the app’s local data is removed, subject to the backup limitations in section 3.
5. Contacting support is your choice
The contact action opens an email draft addressed to alekgameshelp2@gmail.com. Opening a draft does not automatically send it or attach your circuits. You choose whether to send the message, what to write and which attachments to include.
If you send an email, the developer receives your sender address, message, any attachments you include and ordinary email metadata. This information is used to answer your request, investigate a reported problem and follow up when needed. Please share only information necessary for the request. A small example circuit or sanitized screenshot is usually more useful than a complete private workspace. Do not include sensitive information or someone else’s personal data unless necessary and lawful.
Support correspondence is handled in the developer’s Gmail mailbox. Google and your own email provider process email under their applicable terms and privacy notices. They may process it outside your country, including outside the EEA. Google’s Privacy Policy and data-transfer information describe its processing and transfer frameworks, including adequacy arrangements and standard contractual clauses where applicable. You may contact the developer for information about the safeguards applicable to your correspondence. The developer does not sell support correspondence or use it for advertising.
Correspondence is kept only as long as reasonably needed to resolve and follow up on the request, and where necessary to meet a legal duty or establish, exercise or defend a legal claim. The period depends on the request and applicable requirements; there is no promise of immediate erasure from providers’ backup systems. You may request deletion of correspondence using the contact address above. Any applicable reason for retaining specific information will be explained.
6. Legal bases and your rights
Where the GDPR applies, handling ordinary support correspondence relies on the developer’s legitimate interests in answering requests and troubleshooting (Article 6(1)(f)). The limited online legal-document delivery relies on legitimate interests in providing current legal information and maintaining secure delivery, with requests minimized as described above. Providers’ own processing and legal bases are described in their notices. Specific retention may be required by law (Article 6(1)(c)). Please avoid sending special-category personal data; the app does not request it for support.
Providing support information is voluntary and is not required to use the local editor. Without enough information about a reported problem, the developer may be unable to investigate it. Sending a support request does not authorize unrelated marketing or a new use of its contents. If another applicable law requires consent for particular processing, that requirement remains separate from accepting the app’s terms.
Subject to applicable conditions, you may request access, correction, erasure, restriction or portability of personal data held by the developer, and object to processing based on legitimate interests. Email the address above. Only proportionate information needed to verify and handle the request will be sought. The developer cannot provide data held solely in your device’s app container.
Requests are handled within the deadlines required by applicable law. Under the EU GDPR, the usual deadline is one month; if a permitted extension is necessary, you will be informed within that first month of the reason and extension. Requests are normally free of charge, subject to the exceptions provided by law. Rights available under other applicable privacy laws are not limited by this notice. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing.
You may complain to your local data-protection authority, including Poland’s President of the Personal Data Protection Office (UODO). You do not need to contact the developer first.
7. Children, external services and security
Logic Gates is intended for learners aged 13 and older and is not currently marketed specifically to children under 13. The app does not collect dates of birth, verify ages or create child profiles. The local-storage model does not change with age. Parents or guardians should send support requests on behalf of children who cannot give valid consent themselves. No advertising, profiling or optional collection is enabled by an age assumption.
An email can still contain a child’s personal information even though the app has no accounts. A store age rating or agreement to the terms does not replace parental consent where it is legally required. If the developer learns that a child’s information was received without a lawful basis, that information will be deleted, except for a narrowly permitted response or other handling allowed by law. It will not be retained for routine follow-up simply because it arrived in a support mailbox. Teenagers may also have special protections under applicable law; turning 13 does not remove them.
Opening an external website or using an email app involves that service’s own processing. Apple may separately process store, device or backup information under its own terms and settings; this is distinct from app telemetry sent to the developer. Local app data benefits from the device’s operating-system protections, but no storage, backup or email system can be guaranteed completely secure.
8. Changes and contact
Future changes to data handling will be described before they take effect, with additional notice or consent where required. Builds with online legal refreshes can retrieve changed documents and request a new review; older builds with only bundled documents need an app update to display new text inside the app. Posting or acknowledging a new notice does not authorize an unrelated new purpose. The published document masthead identifies its version and update date; offline copies identify the cached or bundled version actually available on that device.
Privacy and support contact: Aleksander Jałtuszyk — alekgameshelp2@gmail.com.