This Privacy Policy explains how LOGIC FUSION, LLC (“we”) processes personal data when you use Authenticator: 2FA & OTP, TOTP mobile application for iOS devices (the “App”). The reference to the services available through the App is the “Services”.
This Privacy Policy (also the “Policy”) applies whenever you use the App or otherwise interact with us in connection with the Services.
We may update this Privacy Policy from time to time to reflect changes in our practices, technologies, or legal requirements. When we do, we will post the updated version and revise the “Last Updated” date. We encourage you to review this Policy periodically.

This Policy applies to information we process for our own purposes as controller or business. It does not govern Apple, DuckDuckGo, websites you visit, account providers whose 2FA entries you add, or other third parties acting independently. Their own notices apply.
For the purposes of applicable data protection laws, including the EU General Data Protection Regulation (GDPR), the data controller is:
Name: LOGIC FUSION, LLC
Address: 4713 Southern Breeze Dr, Naples, FL, US 34114, United States
Email: privacy@logicfusion.net

Category:
Authentication data
Examples:
TOTP setup secrets, generated codes, issuer and account labels, backup codes, imported/exported vault data.
How it arises:
Created, scanned or imported by you, ordinarily stored on-device in the iOS Keychain. Transmitted only if you enable backup/sync or export/share it.

Category:
Password vault data
Examples:
Service names, logins, passwords, website addresses, notes and category labels.
How it arises:
Created or imported by you (including import from browser CSV exports); stored on-device in the iOS Keychain. Transmitted only if you enable iCloud Sync or export it.

Category:
Camera, image and QR data
Examples:
Camera frames, text recognised from them, images and documents you select (including PDF), and QR-code content.
How it arises:
Processed when you add an account by scanning a QR code, by pointing the camera at a printed setup key (the text in view is recognised on-device to find the key), or by importing a QR code from your photo library or files. Camera frames and imported images are processed entirely on your device and are neither stored nor transmitted; only the decoded setup key enters your vault.

Category:
Backup/sync data
Examples:
Your vault entries (2FA accounts and password entries) stored as encrypted fields, together with each record's type, identifier and last-modified timestamp.
How it arises:
Processed only if you sign in with Apple and enable iCloud Sync. Records are written to a private CloudKit database inside your own Apple account: Apple encrypts the entry content and controls the keys, and LOGIC FUSION, LLC operates no server for this feature and cannot read your entries. The record type and the last-modified timestamp are stored unencrypted so that your devices can merge changes.

Category:
Subscription data
Examples:
Product identifier, subscription status, purchase and renewal dates, purchase amount and currency, transaction or receipt identifiers, storefront, trial eligibility, and pseudonymous subscriber and attribution identifiers generated by RevenueCat and AppsFlyer.
How it arises:
Purchases are made through Apple's in-app purchase system. Apple processes your payment; we never receive card or other payment-instrument details. Subscription status and receipts are validated and stored by RevenueCat. So that we can measure which marketing campaigns lead to subscriptions, the App provides RevenueCat with your AppsFlyer attribution identifier, and RevenueCat sends subscription events — including the plan, the amount and currency and the transaction identifier — to AppsFlyer.

Category:
Device and diagnostics
Examples:
App version, operating-system version, device model, language, crash traces, performance data, pseudonymous identifiers generated by our analytics tools, coarse network information, and records of in-app actions such as screens opened, an account being added, a code being scanned or sync being switched on.
How it arises:
Generated whenever the App operates. Events are sent to Amplitude and Firebase (Analytics, Crashlytics, Remote Config). They record that an action happened, never its content: no authentication secrets, passwords, QR contents, account labels, URLs, search terms or page content are included. We do not attach your name or Apple Account e-mail to this data.

Category:
Advertising and attribution
Examples:
IDFA (only with your permission), IDFV, AppsFlyer ID, campaign identifiers, IP-derived approximate location, and install, session, trial, subscription and purchase events.
How it arises:
Collected by AppsFlyer, our attribution provider, to measure and optimise our acquisition campaigns. Install, session, device and identifier data is collected by the AppsFlyer SDK in the App. Trial, subscription and purchase events reach AppsFlyer from RevenueCat, matched to your attribution identifier, which the App provides to RevenueCat for this purpose. IDFA is used only if you allow tracking in Apple's App Tracking Transparency prompt; if you decline, attribution continues without it.

Category:
Browser/Web View data
Examples:
Search terms, URLs, page content, IP address, cookies, local storage, browser and device characteristics, information you submit to sites, and any saved login or one-time code you choose to fill into a page.
How it arises:
Processed within the WebView and by DuckDuckGo, the websites you visit, their content hosts and network providers. Every tab is private: the App stores no browsing history, and page addresses and titles are not saved. A built-in blocklist of known advertising and tracking hosts is applied on your device. If you choose to fill a saved login or one-time code, the App inserts it into the page you are on, and the website receives it when you submit the form.

Category:
Communications
Examples:
Your e-mail address and the display name configured in your mail account, together with anything you choose to include: the message itself, attachments, screenshots and diagnostic details.
How it arises:
Provided when you contact our support by e-mail, send feedback or make a privacy request. The App opens an empty message in your own mail application and attaches nothing automatically — no logs, identifiers or device information are added by us. Your message travels through your e-mail provider and ours.

Category:
Apple Account data
Examples:
The Apple user identifier and e-mail address returned by Sign in with Apple.
How it arises:
Provided by Apple if you choose Sign in with Apple, which is required before iCloud Sync can be switched on. Both values are stored only in the Keychain on your device and are never transmitted to us — we operate no account server. Signing out removes them from the device. There is no separate company account, password or account-recovery process.

We do not intend to collect authentication secrets, live codes, QR contents, account labels, browser history or page content through advertising, analytics, crash reporting or support tools. Do not send such data to support. If the implemented App handles these categories differently, this Policy and the product must be revised before launch.
We may receive limited campaign attribution and aggregated performance information from advertising and analytics partners. We do not receive your name, email address or authentication data from those partners. On iOS, the App will not access IDFA or track you across other companies' apps or websites without the permission required by Apple's rules.

The App generates TOTP codes on your device. Subject to your chosen features and device settings, authentication data is stored using iOS security mechanisms. We do not use authentication data for advertising, profiling or analytics. We do not sell it.
If you enable optional backup/sync, your entries are synchronised through Apple iCloud into a private CloudKit database inside your own Apple account. The content of each entry is written to CloudKit encrypted fields, so Apple encrypts it and holds the keys; we add no encryption of our own. We operate no server for this feature and have no access to your iCloud data, so no content and no metadata about your entries is visible to us. Apple stores a record type and a last-modified timestamp unencrypted so that your devices can merge changes, which means Apple can see how many entries exist and when each changed, but not what they contain. Your entries are restored automatically on any device signed in to the same Apple account with the feature enabled. Switching the feature off stops synchronisation but leaves the copy in your iCloud; "Delete from iCloud" in the App removes that copy entirely.

The App includes a browser built with Apple's WebView technology and uses DuckDuckGo as the default search engine. When you use it:

• the browser runs every tab in a private session: cookies, cache, local storage and session information exist only while the tab is open and are discarded when you close it, and no browsing history is kept;
• DuckDuckGo may receive search terms and technical network information needed to return results and protect its service, under DuckDuckGo's own Privacy Policy;
• when you open a result or other URL, the visited site and its service providers may receive your IP address, browser/device characteristics, requested URL, cookies or identifiers, page activity and information you submit;
• websites may use trackers, analytics, advertising, fingerprinting, login services and embedded content that we do not control, although the App blocks connections to a built-in list of known advertising and tracking hosts; and
• the browser does not provide the same privacy and tracker-blocking protections as the standalone DuckDuckGo browser; it applies its own blocklist instead.

We do not receive or retain your search terms, URLs, browsing history, page content, form entries, cookies or website data. The tracker blocklist is stored in the App and applied entirely on your device, so no address you visit is sent anywhere for checking. The only browser-related information that reaches us is a record that the browser was opened and that a search was run — in both cases without the address or the query — and, if the App crashes, a diagnostic crash report. Because browsing data is never stored, there is nothing to clear afterwards.

• Provide the Services, including code generation, scanning, import/export, optional backup/sync, entitlement checks and support.
• Secure, maintain and troubleshoot the App; prevent abuse, fraud and unauthorized access.
• Process subscriptions and maintain purchase entitlements.
• Respond to support, feedback, legal and privacy requests.
• Understand App reliability and feature performance using AWS, Firebase and Amplitude, with data minimization and exclusion of authentication and browsing content.
• Measure, attribute and optimize acquisition campaigns through AppsFlyer, Google Ads, Meta and TikTok, subject to ATT permission and consent where required.
• Comply with law, enforce our Terms and establish, exercise or defend legal claims.

We do not use authentication data or browser content for advertising, attribution, profiling or training artificial-intelligence models. Advertising partners may process permitted device and campaign data for attribution, campaign optimization or targeted advertising where you have given required permission.

We use personal data only when the law allows us to and only for clear, specific reasons. For this, we rely on the following legal grounds:

To provide the service (Contract)
We use your personal data to make the App work properly on your device.

With your permission (Consent)
We use your personal data when you clearly agree to it — for example, when advertising identifiers are used, or when certain analytics or marketing tools are enabled.

For our legitimate business needs (Legitimate Interests)
We use your personal data to run and improve the App, keep it secure, understand how it’s used, and promote the service — but only when this does not unfairly impact your privacy rights.

To follow the law (Legal Obligations)
Sometimes we must use or share your personal data to meet legal, regulatory, or lawful government requirements.

We may disclose the limited information we hold:

• to service providers acting for us under contract, as listed below;
• to Apple for distribution, purchases, refunds, device/platform functions and App Store operations;
• at your direction, including when you export, share, back up, restore, search, browse or submit information to an external service;
• to professional advisers, auditors and insurers under duties of confidentiality;
• to authorities or other parties when reasonably necessary to comply with law, protect rights and safety, investigate abuse or respond to valid legal process; and
• in connection with a merger, financing, acquisition, reorganization or sale, subject to appropriate safeguards and notice where required.

We do not sell personal information for money. Certain disclosures of permitted identifiers and event data to advertising partners may be considered “sharing,” targeted advertising or a “sale” under some US state laws even when no money is exchanged. We provide the opt-out and consent controls described below. We do not knowingly use or disclose sensitive authentication data beyond providing and securing the requested service.

Provider / role:
Apple (App Store, StoreKit, iCloud/CloudKit, device services)
Data and purpose:
Distribution, purchases, receipts, entitlements, optional backup/sync, platform diagnostics.
Required completion:
Select actual Apple services; link policies; state regions/transfer basis where relevant.

Provider / role:
DuckDuckGo — independent third party (default search engine), not role a processor acting on our behalf
Data and purpose:
Your search query, IP address and technical request information, purpose received directly by DuckDuckGo when the search page loads in the browser, to return results and protect its service.
Required completion:
No SDK or account is involved: the App loads DuckDuckGo's public search URL in the WebView, exactly as it would load any other website.

Provider / role:
Visited websites and embedded providers
Data and purpose:
IP address, browser/device data, cookies, URLs, activity and submitted information.
Required completion:
Independent third parties; no exhaustive list possible.

Provider / role:
Amazon Web Services (AWS)
Data and purpose:
Hosting/infrastructure; IP address, limited device, usage, subscription and technical metadata; encrypted backup payload if Company sync is used.
Required completion:
Confirm AWS entity, regions, logs, retention and whether Company sync is used.

Provider / role:
Firebase (Google)
Data and purpose:
Hosting/storage/technical management; device identifiers and usage, diagnostic and crash data.
Required completion:
Confirm Firebase products, events, identifiers, retention and consent settings.

Provider / role:
Amplitude
Data and purpose:
Product analytics; pseudonymous usage, device/App information and IP address.
Required completion:
Confirm events, user properties, retention and EU consent configuration.

Provider / role:
AppsFlyer
Data and purpose:
Attribution and fraud detection; IDFA if permitted, other device identifiers, IP address, campaign and conversion events.
Required completion:
Confirm SDK configuration, event list, retention and data-sharing controls.

Provider / role:
Google Ads, Meta and TikTok
Data and purpose:
Campaign measurement, advertising and optimization; permitted advertising/device identifiers, campaign and selected conversion events.
Required completion:
Confirm which partners are active, ATT/consent flow, controller roles and opt-out mechanics.

Provider / role:
RevenueCat
Data and purpose:
Receipt validation/subscription management; receipt, transaction, entitlement, device/App and internal identifier data.
Required completion:
Confirm configuration, retention, region and policy link.

We retain personal information only as long as needed for the purposes described, including security, dispute resolution and legal obligations.

Data:
On-device vault
Retention rule:
Until you delete the entries, reset the App or delete the App, subject to your own device and iCloud backups.

Data:
Browser data
Retention rule:
Not retained: each tab runs in a private session and its cookies, cache and session data are discarded when the tab is closed. No browsing history is kept.

Data:
Encrypted backup/sync
Retention rule:
Retained in your own iCloud account until you remove it: switching sync off leaves the copy in place, "Delete from iCloud" in the App deletes it, and deleting your iCloud data or the App removes it as well. We hold no copy and set no retention period, because we operate no server for this feature. Apple's own retention applies to its backups.

Data:
Diagnostics/analytics
Retention rule:
90 days, or shorter where feasible.

Data:
Subscription records
Retention rule:
For the duration of your active subscription and up to 7 years afterward, as required for entitlement, accounting, tax, disputes and fraud prevention.

Data:
Support communications
Retention rule:
24 months after closure, unless longer retention is needed for a dispute or required by law.

Data:
Privacy requests
Retention rule:
24 months, to demonstrate compliance and prevent fraud.

Deleting the App may not delete data held by Apple, stored in iCloud/device backups, exported to Files, shared with another service, or independently retained by DuckDuckGo or visited websites.

We use administrative, technical and organizational measures designed for the nature and risk of the information, such as on-device protected storage, encryption in transit, access controls, minimized logging, vendor review, secure development and incident response. No method is completely secure. You are responsible for securing your device, Apple Account, exports and recovery materials.

We and our providers may process information outside your country. Where required for transfers from the EEA, UK or Switzerland, we use an adequacy decision, approved standard contractual clauses or another lawful safeguard. Contact privacy@logicfusion.net to request information about applicable safeguards.

App controls: you can turn iCloud Sync on or off, and delete the copy stored in iCloud, through Settings > iCloud Sync. You can connect and disconnect the VPN at any time from the VPN tab; while it is disconnected, none of your traffic is routed through our servers. You can set an app PIN and Face ID unlock through Settings > App PIN code, and sign out of your Apple Account through Settings > Account, which removes it from this device. "Start Over" on the lock screen erases the App's data on this device; the copy in your iCloud is not affected and can be restored by signing in again. Browsing data is not retained by the App, so there is nothing to clear. The App does not currently provide an in-app setting to switch analytics off.

Tracking: choose "Ask App Not to Track" in Apple's prompt or manage permission in iOS Settings > Privacy & Security > Tracking. If permission is denied, we will not access IDFA for advertising or marketing.

Camera: deny or revoke camera access in iOS Settings.

Browser data: there is nothing to clear. Every tab runs in a private session, so its cookies, cache and website data exist only while the tab is open and are discarded when you close it, and no browsing history is kept. Visited sites may provide separate controls over data they hold.

Subscription: manage or cancel through Apple Account subscription settings.

Depending on where you live, you may have rights to access, know, correct, delete, port or restrict personal information; object to certain processing; withdraw consent; opt out of sale, sharing, targeted advertising or qualifying profiling; and appeal a denied request. EEA/UK users may complain to their local supervisory authority. California residents may have the rights described above and the right to non-discrimination for exercising them.

Some rights have exceptions. Because much authentication and browser data remains only on your device or with independent third parties, we may not possess or be able to retrieve it. If we deny an appealable US state request, contact us with "Privacy Appeal" in the subject line.

California notice at collection: the categories collected, purposes and retention rules are described in Sections 2, 5 and 9. We do not sell personal information for money. Advertising disclosures described in Sections 5, 7 and 8 may constitute "sharing" or "sale" under California law; users can opt out by denying/revoking ATT permission. We do not offer financial incentives for personal information.

The Services are not directed to children under 13, and we do not knowingly collect personal information from them. If local law requires a higher minimum age or parental consent, that rule applies. If you believe a child provided information to us, contact us at privacy@logicfusion.net.

The App does not use personal information for solely automated decisions that produce legal or similarly significant effects. We do not use authentication data, browser content or support content to train artificial-intelligence models.

We may update this Policy to reflect changes in the Services, law or our practices. We will post the updated version and change the "Last updated" date. If a change is material, we will provide additional notice or obtain consent where required.

If you have any questions about this Policy, please feel free to contact us via email at privacy@logicfusion.net.