Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Add privacy manifest #334

Merged
merged 5 commits into from
Feb 12, 2024
Merged

fix: Add privacy manifest #334

merged 5 commits into from
Feb 12, 2024

Conversation

keelerm84
Copy link
Member

No description provided.

@keelerm84 keelerm84 requested a review from a team February 8, 2024 15:02
@keelerm84 keelerm84 merged commit 154fde7 into v9 Feb 12, 2024
4 checks passed
@keelerm84 keelerm84 deleted the privacy-manifest branch February 12, 2024 19:38
keelerm84 pushed a commit that referenced this pull request Feb 22, 2024
🤖 I have created a release *beep* *boop*
---


##
[9.4.0](9.3.0...9.4.0)
(2024-02-21)


### Features

* Add new identify method with time out support
([#344](#344))
([34ba8ab](34ba8ab))
* Implement shedding identity queue
([#343](#343))
([393a28c](393a28c))
* Introduce variation method with generic return types
([#342](#342))
([7ff2ffb](7ff2ffb))


### Bug Fixes

* Add privacy manifest
([#334](#334))
([154fde7](154fde7))
* Ensure anonymous context is valid
([#338](#338))
([65406cc](65406cc))
* Replace simple logger with os_log statements
([#340](#340))
([7ba4397](7ba4397))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: LaunchDarklyReleaseBot <LaunchDarklyReleaseBot@launchdarkly.com>
@choulepoka
Copy link

Is there a way to stop the tracking of users? Because tracking is a big deal in the Apple world, if the LD sdk tracks, when we have to request user's permission, and if the user says no, we gotta stop tracking.

Is there a way to do that without crippling the LD integration? @keelerm84

@keelerm84
Copy link
Member Author

Is there a way to stop the tracking of users? Because tracking is a big deal in the Apple world, if the LD sdk tracks, when we have to request user's permission, and if the user says no, we gotta stop tracking.

Is there a way to do that without crippling the LD integration? @keelerm84

My apologies for the delay in getting back to your question!

It is my understanding that the type of data our SDK uses does not require user interaction for approval. We are not tracking users for advertisement purposes; rather, any identifier is consumer provided and sent to our servers for the purpose of flag evaluation and experimentation.

@choulepoka
Copy link

@keelerm84 If that is truly the case, then the following values should be false:

  • NSPrivacyTracking
  • NSPrivacyCollectedDataTypeTracking

Otherwise, you are basically declaring to Apple that the LaunchDarkly Framework is tracking for the purpose of App Tracking Transparency.

@keelerm84
Copy link
Member Author

@choulepoka Yes, you are correct. We had the type tracking field set incorrectly. This is being adjusted in #366 and should be out in the next patch release (9.6.2).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants