A link can explain how someone found Skyflo. It cannot establish whether they returned to useful work. Answering that second question connects two kinds of information, so it needs its own choice.
Campaign outcomes adds that separate choice to Privacy choices on skyflo.ai. It starts off. An earlier Analytics answer, an advertising choice or a regional default does not turn it on. Product usage in Desktop remains a separate setting on each Mac.
What the Choice Permits
When you expressly turn on Campaign outcomes during a visit from a known campaign, Skyflo can record its fixed placement category and a new permission reference. It uses the current arrival, rather than an older attribution cookie or account history.
If you subsequently create and sign in to a new account, that permission can be linked to the account. Only future records from a signed-in installation separately sharing Product usage can contribute. Eligibility starts no earlier than the next UTC day after both permission and account link are recorded. Earlier accounts, visits and usage are not backfilled.
Campaign outcomes can be chosen while Google Analytics is off. Turning it on does not load an advertising pixel. Turning Analytics off alone does not withdraw a separately enabled Campaign outcomes choice.
What Counts as a Return
An observed engagement day requires a deliberate work action: a user approval or answer, or an applied phone command to queue or steer work. It must appear alongside a completed agent turn on the same Mac, mission reference and UTC day.
Authentication, passive activity, mission creation and background completion alone do not qualify. The paired records show an action and a completion that day. They do not prove that the action caused the completion or that the work achieved its objective. Direct Desktop submissions without a recorded approval or answer, and cloud work without a matching completion, can be missed.
The first observed qualifying week establishes the cohort. Week-one return means qualifying work again in the next complete Monday-to-Monday UTC week. Its denominator includes currently eligible, separately permitted accounts that qualified in the cohort week. Withdrawal and deletion remove live contributions. An unobserved return is not proof that someone stopped using Skyflo.
Reports use fixed placement and week cells. A published rate requires at least 20 people, 10 returners and 10 non-returners, with rounding and suppression. Internal activity is separate. Late deliveries can revise recent weeks, and withdrawal can change a previously reported result. These are limited observations, not a complete account of product engagement.
Changing Your Mind
Turn Campaign outcomes off, or choose Reject all, from Privacy choices. Skyflo stops Campaign outcomes activity in that browser and requests durable removal of the permission, its live links and mutable contributions. If the service cannot be reached, a necessary cancellation receipt remains for retry. An earlier delayed registration cannot reactivate a revoked permission.
Permissions expire within 90 days. Browser cancellation proofs last at most 91 days from the choice. Turning Product usage off removes that Mac's live contributions, and account deletion removes linked purpose state. This version creates no frozen campaign aggregates.
Campaign outcomes does not add emails, plain account identifiers, browser visitor identifiers, page addresses or free-form campaign strings to product-usage records. The results are not exported to advertising platforms or used for individual targeting.
The Privacy Notice describes the records, choices, retention and deletion in full. The website update records this change.