Cookie & Tracking Policy

Effective Date: March 11, 2026 Last Updated: April 10, 2026 Authoritative Language: English. Any translation is provided for convenience only. If a translated version conflicts with the English version, the English version controls.

1. Scope

This Cookie & Tracking Policy explains how Finqt LLC-FZ uses cookies and similar technologies in the finqt app and any connected service surfaces we operate.

Because finqt is primarily an app-based service, many of the technologies described here are app equivalents rather than traditional browser cookies. These can include local storage, secure tokens, keychain entries, push tokens, cached content, consent records, diagnostic identifiers, and similar technologies.

2. Technologies We May Use

Depending on the feature, platform, and consent state, we may use:

• session identifiers and authentication tokens
• secure storage and keychain entries
• local storage, caches, and preference records
• push-notification tokens and related routing identifiers
• device or app identifiers needed for security, restore, diagnostics, or functionality
• software libraries or SDK components used to support analytics, diagnostics, AI, or notifications
• web cookies, pixels, or similar tools on any related web surfaces we may operate

In practice, these technologies can appear as secure session tokens, purchase-restore records, app cache entries, push-routing tokens, consent-state flags, image-upload workflow references, and temporary files needed to complete requested features.

3. Categories of Technologies

3.1 Strictly necessary technologies

These technologies are used to:

• authenticate users
• maintain account sessions
• restore purchases and paid entitlements
• route push notifications and similar system events
• secure accounts, detect abuse, and support core functionality

These technologies are generally required for the Services to work.

3.2 Preference technologies

These technologies help us remember:

• language and localization preferences
• display and experience choices
• watchlist, bookmark, and similar saved settings
• consent choices and privacy settings

3.3 Analytics and diagnostics technologies

These technologies may help us understand:

• which screens or features are used
• app crashes, failures, and load-time issues
• aggregate reliability and performance trends

Where required by law, we ask for consent before using optional analytics or diagnostic technologies that are not strictly necessary.

3.4 AI and operational records

Certain feature flows may store or reference operational records needed to:

• maintain AI conversation context
• manage credit deductions and quota checks
• store temporary workflow state for uploaded files or generated outputs
• support fraud prevention, moderation, and troubleshooting

These records may not look like a traditional cookie, but they can still store or reference information associated with your device, session, account, or a particular workflow.

3.5 Offline content and app cache technologies

To improve resilience and app usability, the Services may store offline-capable materials and recently retrieved content, including certain legal documents, settings, and non-sensitive app resources. These cached materials help the app continue to function when connectivity is limited or unavailable.

Cached materials may remain on the device until refreshed, cleared by the app, removed by you, or overwritten by the operating system.

3.6 Advertising and attribution technologies

The iOS app may request Apple's App Tracking Transparency permission before enabling advertising attribution or more relevant sponsored content where available. Any such processing depends on your permission status, consent choices, and the disclosures active when you use the feature.

If we enable or expand advertising, attribution, or campaign-measurement technologies in a way that requires additional notice or consent, we will update this Policy and provide any controls required by law or platform rules.

4. Typical Duration of Storage

Different technologies may persist for different periods depending on their purpose.

For example:

• session tokens may persist until logout, session expiry, or revocation
• secure authentication or restore-related records may persist while needed for account security or entitlement validation
• local caches may persist until refreshed, cleared, or overwritten
• consent records may persist for as long as necessary to honor and document your choices
• diagnostic and operational records may be retained according to our security, reliability, and legal-retention needs

Storage duration can also depend on whether you log out, revoke permissions, clear app data, rotate devices, delete your account, reinstall the app, or allow the operating system to purge cached content.

We do not guarantee that every item is stored for the same duration across every platform or environment.

5. Third-Party Technologies

Third parties that power parts of the Services may also use their own cookies or similar technologies, subject to their own policies. Depending on the feature, those third parties may include:

• platform and app-store providers
• AI providers
• market-data providers
• hosting, diagnostics, analytics, or communication providers

If you click through to an external site, exchange, or article, that third party may place its own cookies or tracking technologies on your device. We do not control those third-party technologies.

6. How to Manage Your Choices

You may be able to control technologies through:

• device settings
• app settings and consent controls we provide
• browser privacy controls on any related web surfaces
• notification, camera, photo-library, or similar device-permission settings
• Apple platform privacy controls, if relevant to the feature in question

If you want to reduce the amount of locally stored content, you may also be able to log out, uninstall and reinstall the app, revoke permissions, disable notifications, or use operating-system settings that clear app storage. Some actions may reduce functionality or require reauthentication.

Blocking or disabling certain technologies may reduce functionality or prevent some features from working correctly.

7. Do Not Track and Similar Signals

Different browsers, devices, and platforms support different privacy signals. We honor the controls we are required to honor under applicable law and the controls we explicitly make available. Unless we state otherwise in-product, we do not promise that every browser-based or device-based signal will be recognized across every surface.

Because the Services are primarily app-based, some browser-oriented signals may not map neatly to native-app storage or push-notification technologies. Platform privacy settings, consent choices, and permission controls are often more relevant for native-app use.

8. Updates

We may update this Cookie & Tracking Policy as our Services, providers, product design, or legal obligations change. The latest version will be posted with the updated effective date.

9. Contact

If you have questions about this Policy:

Email: [email protected]

Finqt LLC-FZ Meydan Free Zone Dubai, United Arab Emirates