LincsLincs.

Lincs Cookies Policy

This Cookies Policy explains how Lincs ("we", "us", "our") uses cookies and similar technologies on the Lincs Platform (the "Platform"), including our mobile app and any web pages, web views, or websites we operate.

Because Lincs is primarily a mobile marketplace app, some tracking technologies may not be traditional "cookies" (which are mainly used on websites). We also use mobile identifiers, local storage, and SDKs (software development kits) for similar purposes.

This policy should be read together with our Privacy Policy.

1. What Are Cookies and Similar Technologies?

1.1 Cookies (Web)

Cookies are small text files stored on your device by a website or web view. They help websites remember your preferences and support features like login sessions.

1.2 Similar Technologies (Mobile + Web)

We may also use:

  • Local storage / app storage: stores settings and cached data within the app.
  • SDKs: third-party libraries that support analytics, crash reporting, payments, notifications, and verification.
  • Device identifiers: identifiers and tokens used for push notifications, analytics, and security.
  • Pixels / tags (web): scripts that measure usage and performance (only where applicable).

2. Types of Cookies/Technologies We Use

We group technologies by purpose. Not all will apply to every user, device, or Platform version.

2.1 Essential (Strictly Necessary) Cookies/Technologies

These are required for the Platform to work. You generally cannot disable them without affecting core functionality.

Used for:

  • authentication and session management,
  • security controls and fraud prevention,
  • maintaining booking flow states,
  • protecting account access and preventing unauthorized activity.

Examples in Lincs context:

  • keeping you logged in after you sign in,
  • preventing suspicious login attempts,
  • ensuring your booking state updates correctly (pending → accepted → completed).

2.2 Performance Cookies / Analytics / Crash Reporting

These help us understand how the Platform is used and improve stability and performance.

Used for:

  • usage analytics (e.g., which screens users visit most),
  • app performance monitoring,
  • crash reporting and diagnostics,
  • measuring load times and errors.

Examples in Lincs context:

  • detecting why the app crashes on a specific Android version,
  • measuring how long it takes to load artisan search results.

Where required by law or best practice, these may be enabled only after consent, especially for web cookies and non-essential tracking.

2.3 Functional Cookies / Preferences / Feature State

These support convenience and personalisation features.

Used for:

  • saving preferences (e.g., language, notification preferences),
  • remembering certain app settings,
  • keeping some temporary UI states (e.g., search filters, chat drafts),
  • supporting location-based services.

Examples in Lincs context:

  • remembering your selected country/state during signup,
  • restoring your last used filters for searching artisans,
  • keeping chat state so you can continue a conversation.

2.4 Marketing / Advertising (If Applicable)

We only use marketing cookies/trackers if we run marketing campaigns or personalisation that involves tracking.

Used for:

  • measuring ad performance,
  • re-engagement campaigns,
  • user behaviour tracking for personalisation (where applicable),
  • remarketing (web).

Examples in Uselincs context (if enabled):

  • tracking that a user installed after clicking an ad,
  • showing tailored promotions based on app usage.

We do not use marketing cookies at this time.

3. Third-Party Cookies and Technologies

Some functions are provided by third-party providers. These providers may set cookies (web) or use SDK-based tracking (mobile) according to their own policies.

3.1 Payment Processing

  • Payment initiation pages (web URLs) and payment confirmations.
  • Transaction references and status checks.

Examples: When you fund your wallet, a payment provider may set cookies in a browser page used for payment.

3.2 Analytics and Crash Reporting

  • Aggregated usage data and diagnostics.
  • Crash logs and performance metrics.

3.3 Verification / KYC Services (If Used)

  • Identity verification results and document processing.
  • Fraud prevention controls.

3.4 Push Notifications

Device push tokens (not cookies) to deliver booking and account alerts.

Third-Party List

  • Analytics: Lincs
  • Crash reporting: Lincs
  • Payments: Paystack
  • Verification/KYC: OBR
  • Push notifications: Resend

4. Local Storage / Cached Content (Mobile)

Because the Platform is mobile-first, we may store certain data on your device using secure storage, app storage, or caching.

This may include:

  • user preferences (theme, language),
  • offline data and cached API responses (to improve speed),
  • cached images/media (e.g., artisan profile photos),
  • session tokens (stored securely),
  • temporary chat state.

We aim to keep sensitive information in secure storage where supported by your device.

5. Device Identifiers (Mobile)

On mobile apps, "cookies" may be replaced by device-level identifiers and tokens.

We may use:

  • push notification tokens (to send booking updates),
  • device identifiers for security and fraud prevention,
  • analytics identifiers (where enabled) to understand usage patterns.

You can control some of these through:

  • device OS privacy settings,
  • app permissions,
  • in-app preferences (where provided).

6. Consent Mechanism (Cookie Banner and Controls)

6.1 Web Consent

Where required, we show a cookie banner that allows you to:

  • accept all cookies,
  • reject non-essential cookies,
  • choose categories (essential, performance, functional, marketing).

6.2 In-App Consent (Mobile)

For mobile tracking/analytics that is not strictly necessary, we may:

  • request your consent in an in-app prompt,
  • provide settings to enable/disable analytics or personalized features.

Granular Controls (Recommended)

  • Essential: Always on
  • Performance/Analytics: On/Off
  • Marketing/Personalization: On/Off

7. How to Manage or Clear Cookies / Tracking

7.1 In-App Settings (Recommended)

  • Disable non-essential analytics (where supported),
  • Reset consent preferences on the web,
  • Manage notification permissions.
  • Manage Availability

7.2 Browser Controls (Web)

If you access Lincs via a browser:

  • You can clear cookies via browser settings,
  • You can block certain cookies (note: essential cookies may break login and key functions).

7.3 Device-Level Controls (Mobile)

You can manage:

  • location permissions,
  • notification permissions,
  • ad tracking preferences (depending on OS).

8. Cookie/Identifier Lifespan and Retention

8.1 Session vs Persistent

  • Session cookies last only while your browser session is active (web).
  • Persistent cookies remain until they expire or you delete them.

8.2 Typical Retention (Examples)

  • Essential session tokens: until logout or token expiry.
  • Preferences storage: until changed/deleted by the user.
  • Analytics identifiers/events: retained for 3 months.
  • Crash logs: retained for 4 months.

We aim to keep data only as long as needed for the purposes described, consistent with our Privacy Policy.

9. Updates to This Cookies Policy

We may update this Cookies Policy to reflect:

  • new Platform features,
  • new tracking technologies,
  • changes in law or industry guidance,
  • adding/removing third-party providers.

When we make material changes, we will notify you via:

  • in-app notifications,
  • email (if available), and/or
  • posting an updated policy in the Platform.

10. Contact Us

For questions about cookies, tracking, or consent, contact:

  • Email: support@uselincs.com