Cockies Policy

This Cookie Policy explains how Abbas Studio (“we,” “us,” “our”) uses cookies, similar tracking technologies (including localStorage, sessionStorage, and scripts), and advertising/analytics identifiers when you visit https://financeguru.me/ (“Website”).

Read this together with our Privacy Policy: https://financeguru.me/privacy-policy

If you continue to use the Website after seeing a consent banner (where required), your chosen preferences will be honored as described here.

2. What Are Cookies?

Cookies are small text files stored on your device by your browser. They help a site recognize a device, remember preferences, maintain sessions, and measure usage.

Related Technologies We May Use:

1. LocalStorage / sessionStorage: Key/value storage inside your browser (not transmitted automatically to servers).
2. IndexedDB / Cache Storage (future possibility): For performance and offline optimization.
3. Web Workers / Service Workers: For faster tool execution (not used for tracking; disclosure for transparency).
4. Web Beacons / Pixels: Small tags used (primarily by third parties) to measure ad impressions or conversions.
5. Script-Based Fingerprinting (We Avoid): We do not intentionally use intrusive fingerprinting methods.

3. Why We Use These Technologies

Primary purposes:

1. Essential Functionality – Enable core tool operations & security.
2. Preferences – Remember last used tool modes, theme (light/dark), or UI language (future state).
3. Performance & Reliability – Load balancing, caching, error measurement.
4. Analytics – Understand anonymous aggregated usage to improve tools (e.g., which converter is popular).
5. Advertising – Support monetization via contextual or (consented) personalized ads (e.g., Google AdSense).
6. Abuse Prevention – Rate limiting, bot detection, fraud mitigation.
7. Debugging – Error reproduction and minimal statistical logging (non-sensitive).

We avoid combining data to build persistent personally identifiable profiles unless explicitly consented to (where legally required).

4. Categories of Cookies We May Set or Allow

5. Detailed Cookie & Storage Inventory (Illustrative)

Replace or update this table with actual cookie names once finalized.

(If you use a Consent Management Platform (CMP), auto-generate & link the real-time list.)

Note: Some third-party services dynamically set additional cookies. Use your CMP to capture and disclose them automatically.

6. LocalStorage & SessionStorage Usage

We may store:

1. UI preferences (theme, collapse/expand states)
2. Temporary tool inputs (client-side only, not transmitted unless required)
3. Recent history (e.g., last 3 tools used for quick navigation) Data stays in your browser until cleared manually or programmatically removed.

We do NOT intentionally store sensitive personal data in localStorage.

7. Consent Management (EEA/UK & Similar Jurisdictions)

Visitors from regions requiring consent will see an initial banner / popup offering:

1. Accept All
2. Reject Non-Essential
3. Customize (granular toggles: Analytics, Ads, Experiments)

Features:

1. Prior Blocking: Analytics/ads scripts blocked until consent is given.
2. Record Keeping: consent_state cookie logs categories accepted + timestamp.
3. Withdrawal: Users can revisit “Cookie Settings” link (footer) to modify choices anytime.
4. Proof: Keep anonymized consent logs (if implemented) for audit (timestamp, category selections, hashed IP if required).

8. Changing or Withdrawing Consent

You can:

1. Click “Cookie Settings” (footer link) to adjust toggles.
2. Clear cookies/storage via browser settings (will reset preferences & banner reappearance).
3. Use industry opt-out pages (for ad personalization):
4. https://adssettings.google.com/
5. https://optout.aboutads.info/
6. https://www.youronlinechoices.com/ (EU)
7. https://optout.networkadvertising.org/

Withdrawal does not retroactively invalidate prior lawful processing.

9. Managing Cookies in Your Browser

Common instructions (subject to change per browser version):

1. Chrome: Settings > Privacy & Security > Cookies
2. Firefox: Settings > Privacy & Security > Cookies and Site Data
3. Edge: Settings > Cookies & Site Permissions
4. Safari (macOS): Preferences > Privacy
5. Mobile Browsers: Use in-app site settings or clear data function

Blocking all cookies may impair tool reliability or cause repeated consent banners.

10. Advertising Cookies (Google AdSense)

AdSense may use:

1. Frequency capping cookies
2. Fraud detection identifiers
3. Personalization cookies (if you consent)
4. Non-personalized contextual ads where personalization rejected or unavailable

More info: https://policies.google.com/technologies/ads

You can disable personalized ads via Google Ad settings even after initial consent.

We do not control the full lifecycle of third-party advertising cookies; refer to their policies.

11. Analytics Technologies

If implemented (e.g., Google Analytics with IP anonymization):

1. Purpose: Understand aggregated tool adoption (e.g., which converters are popular)
2. Personalization Disabled: Ensure signals are aggregated & anonymized where feasible
3. Controls: Consent gating in EEA/UK
4. Retention: Configured (e.g., 14 months) – adjust to actual configuration in GA

You may install browser plug-ins such as Google Analytics Opt-Out Add-on for further control.

12. Security & Anti-Abuse

Security cookies / tokens:

1. Distinguish legitimate traffic from bots
2. Protect against brute force, injection, or scraping patterns These are minimal and essential; refusal may impede access.

13. A/B Testing & Experiments (If Used)

We may gradually deploy new layouts or performance optimizations. Variant assignment cookies (ab_variant_*) ensure consistent experience during a test window. These are non-essential and require consent in EEA/UK unless strictly functional.

(If you do not use experiments yet, remove or mark as “planned.”)

14. Do We Use Fingerprinting?

We avoid invasive fingerprinting techniques (e.g., canvas fingerprinting) for tracking individuals. Performance diagnostics may collect ephemeral metrics (screen size, device type, anonymized). None used to build unique persistent identity profiles.

15. Legal Bases (EEA/UK)

1. Essential Cookies: Legitimate interest (site functionality & security).
2. Preference / Functional: Consent (where required) or legitimate interest if strictly necessary.
3. Analytics: Consent (opt-in toggle).
4. Advertising / Personalization: Consent (explicit).
5. Security / Fraud Prevention: Legitimate interest (protect service integrity).

16. California (CCPA/CPRA) & “Do Not Sell or Share”

We do not “sell” personal information for monetary value. Some ad personalization may be considered “sharing” under CPRA definitions. You can opt out by:

1. Rejecting advertising category in the cookie settings panel
2. Configuring browser global privacy control (GPC) signal (if we detect it, we treat it as opt-out)
3. Using AdChoices / Google Ad settings links

17. International Transfers

Third-party analytics or ad providers may process cookie-derived data on servers in other jurisdictions (e.g., United States, EU). Safeguards (e.g., Standard Contractual Clauses) are governed by the providers’ policies; see their documentation for details.

18. Data Retention

Cookie / storage lifetimes vary:

1. Session cookies: Deleted when browser closes
2. Preference entries: 30–365 days (renewed upon use)
3. Analytics: Provider-defined (e.g., GA retention 14 months unless reset)
4. Advertising IDs: Up to 13 months (regional difference for EU)
5. Consent logs: Up to the longest required legal evidence period (e.g., 24 months)

On expiry, cookies self-lapse; localStorage persists until cleared.

19. Third-Party Services That May Set Cookies (Examples)

(Replace with exact list once finalized.)

1. Google AdSense (ads)
2. Google Analytics (analytics)
3. CDN / Security provider (protective tokens)
4. Font or asset CDNs (may include caching headers, no tracking cookie, but list for transparency)
5. Performance monitoring (if added: e.g., Sentry/LogRocket – disclose if implemented)

Each third party has its own privacy & cookie policies; consult them for specifics.

20. Minimization Practices

We strive to:

1. Avoid setting non-essential cookies before consent (EEA/UK)
2. Use localStorage instead of cookies for purely local non-tracking preferences
3. Group script loading behind a consent manager
4. Periodically audit cookie inventory and remove stale or unused entries

21. Updating This Policy

We may revise this Cookie Policy for:

1. Regulatory changes
2. Introduction of new technologies (e.g., API-based personalization)
3. Tool architecture modifications

“Last Updated” date indicates the latest revision. Material changes may trigger a renewed consent banner.

22. How to Contact Us

Questions or concerns: Email: admin@financeguru.me

Website: https://financeguru.me/

Subject suggestions: “Cookie Inquiry” / “Consent Withdrawal” / “Analytics Clarification”

23. Quick Summary (Plain Language)

1. We use essential cookies to make tools work and stay secure.
2. Analytics & ads are optional and need your consent in certain regions.
3. You can change your choices anytime via a “Cookie Settings” link or clearing browser data.
4. LocalStorage holds convenience preferences (theme, last tool) locally on your device.

24. Implementation Checklist (Developer Notes – Remove or Comment Out if Publishing Raw)

1. Integrate a Consent Management Platform (CMP) supporting IAB TCF (if serving EU).
2. Block analytics/ad scripts until consent captured.
3. Provide a “Re-open Cookie Settings” footer link.
4. Maintain a function to flush non-essential cookies when user withdraws consent.
5. Update the “Detailed Cookie Inventory” table automatically from CMP export if possible.
6. Respect GPC (Global Privacy Control) signals (treat as advertising opt-out for CA + certain frameworks).

25. Structured Data (Optional JSON-LD)

Add this to the Cookie Policy page (not mandatory but can aid clarity):

26. Disclaimer

This Cookie Policy is informational and does not constitute legal advice. Consult qualified legal counsel to tailor obligations for your jurisdiction and technical stack.