PortföyGPT

Cookie Policy

Cookies and similar technologies (SDKs, device identifiers, local storage) used in PortföyGPT.

Cookies and Similar Technologies Policy

Effective date: 18 June 2026 Last updated: 18 June 2026

This policy explains the cookies and similar tracking technologies (software development kits — SDKs, device identifiers, local storage) used in the PortföyGPT mobile application. Legal basis: Electronic Communications Law No. 5809 and Turkish Personal Data Protection Law No. 6698 (KVKK).

Note: Because PortföyGPT is a mobile application, it primarily uses SDKs, device identifiers, and local storage rather than classic browser cookies. Both are addressed below as "cookies and similar technologies."


Cookies and similar technologies are small pieces of data saved to your device when you use a service, or identifiers stored on your device. They are used to maintain your session, remember your preferences, keep the service secure, and measure its usage.


2. Technologies We Use and Their Categories

CategoryTechnology / ProviderPurposeConsent required?
Strictly necessarySession token (Supabase authentication), secure storage, local settings (shared preferences)Keeping the session active, security, basic preferencesNo (required for the service)
FunctionalPush notification token (Firebase Cloud Messaging)Price alerts and informational notificationsNo / device notification permission
AnalyticsFirebase Analytics (Google)Understanding app usage on an aggregate/statistical basis, product improvementLegitimate interest (non-essential; right to object/manage preserved)
Performance/CrashFirebase Crashlytics & Performance (Google)Error diagnostics, stabilityLegitimate interest (non-essential; right to object/manage preserved)
Marketing / AdvertisingGoogle AdMob, advertising identifier (IDFA)Personalized advertisingYes (ATT permission on iOS)

3. Third-Party Technologies

The application uses the SDKs of the following third-party providers; these providers may process data under their own policies:

  • Supabase (authentication, database, server infrastructure, hosting)
  • Google / Firebase (Analytics, Crashlytics, Performance, Cloud Messaging)
  • Google AdMob (advertising)
  • RevenueCat (subscription management)

Note: The artificial intelligence portfolio analysis is performed via a server-side API call that does not place any SDK or cookie on your device; for this reason it does not appear in the device SDK list above. For data transferred to the AI service provider, see the Privacy Policy, Article 4.

For details on the data transferred to these providers, see the Privacy Policy, Article 4.


4. Advertising Identifier and ATT (iOS)

On iOS devices, before accessing your device's advertising identifier (IDFA) for personalized advertising, we request your App Tracking Transparency (ATT) permission:

  • If you grant permission: ads may be personalized based on your interests.
  • If you do not grant permission: ads are not personalized; your use of the Application is not affected.

5. How to Manage Your Preferences

  • Ad tracking (iOS): Settings → Privacy & Security → Tracking.
  • Advertising identifier (Android): Settings → Google → Ads.
  • Notifications: device notification settings or in-App settings.
  • Analytics and performance/crash: these measurement technologies are not essential to the operation of the service; they are processed on an aggregate/statistical basis and are not used to identify you. You can manage or object to this processing through the in-app privacy/tracking preferences or your device settings. Where in-app preference controls are provided, you can turn off analytics there; in any case, you may submit your objection requests regarding this processing via info@prismindmedia.com.

Strictly necessary technologies cannot be disabled; otherwise, the core functions of the Application may not work.


6. Changes and Contact

We may update this policy; the current version is always on this page. For questions: info@prismindmedia.com