Who operates Lure
Lure is operated by Shahhin Sarlak of 108/7-11 Smith Street, Ryde NSW 2112, Australia. Questions, access requests, correction requests and privacy complaints can be sent to shahhinsarlak@gmail.com.
Age assurance
Lure accounts are for people aged 16 or older. After authentication and before any social content loads, a new web account without an existing age decision can self attest by selecting “I am 16+”. An expired previous web declaration can be renewed in the same way. Lure records the eligibility result, declaration method, policy version, relevant timestamps and a protected account derived reference. This declaration is not identity verification. Lure does not collect your date of birth, an identity document or a selfie for it.
On iOS, the Lure app can ask Apple for a Declared Age Range. Apple can describe the range as self declared, guardian declared or confirmed. Lure accepts any of those sources only when the lower bound is at least 16. This does not mean that Apple has verified your identity.
The app sends the shared bounds and declaration source with App Attest integrity data and an App Store signed AppTransaction. App Attest helps Lure check the app and device key but does not cryptographically prove the age range itself. The app temporarily processes the App Store device verification identifier and signed device verification values to confirm that the AppTransaction belongs to the current device. Lure verifies these signals again on the backend before recording a result.
For the Apple flow, Lure stores the eligibility result, declaration method, relevant timestamps, policy version, App Attest public key and counter and protected references made from Apple identifiers. This can include a protected reference made from the device verification identifier. Lure does not store the raw AppTransaction or device verification identifier, your date of birth, an identity document or a selfie. Short lived one time challenges are kept only long enough to prevent replay.
If the range is under 16, overlaps 16, lacks useful bounds, is declined or cannot be submitted securely, social content remains locked. A web declaration cannot overwrite an existing ineligible result, manual review or conflicting Apple decision. Android users without an existing eligible result can complete assurance in the iOS app or request manual review. You can contact support, delete your account or sign out while access is locked.
Apple can notify Lure when relevant consent is withdrawn. Lure verifies the signed notification and first stores a protected revocation marker. If an account is bound, its assurance moves to manual review and social operations are blocked on the next backend check. The mobile app checks eligible accounts regularly and when it returns to the foreground.
Information Lure handles
Account and profile
Amazon Cognito handles authentication. Lure receives an account identifier, authentication claims and your email address where needed for account access. Profile information can include your handle, display name, biography, approved profile image, visibility choices and Ko-fi page.
Content and social activity
Lure handles audio, titles, captions, categories, comments, approved GIF references, likes, saves, follows, blocks, notifications, shares, listening events and Deep playback positions. Block records are private. Lure does not tell another account who blocked them or reveal block direction.
Safety and support
Reports, support messages, moderation cases, appeals and audit records may include the content involved, the selected reason, your statement, action history and a protected account reference. Lure does not show internal moderation scores or retained safety identifiers to users.
Tips and technical records
If a creator connects Ko-fi, Lure stores the page URL and a private webhook token. Verified tip records can include amount, currency, supporter name, transaction reference and time. Lure does not process the payment or store card or bank details. Service logs can include request, device, error, security and network information.
How information is used
- Authenticate accounts and enforce the minimum age.
- Host, review, publish and deliver approved audio and profile images.
- Operate profiles, comments, social connections, search and playback.
- Apply blocks in both directions and remove affected activity from views.
- Prevent fraud, abuse, unsafe content and rights infringement.
- Review reports, respond to support cases and decide appeals.
- Maintain security, diagnose faults and meet record keeping duties.
Lure does not sell personal information. Lure does not currently use personal information for cross company advertising tracking.
Moderation before publication
Audio and related text are checked before publication using AWS Transcribe, Transcribe toxicity features and Amazon Bedrock Guardrails. Profile images are checked with Amazon Rekognition. Metadata and visible text can also be checked with Bedrock Guardrails. Content remains in quarantine while checks run.
Approved content can be published. Rejected content stays unavailable. Uncertain results receive human review. Creators can see a reason safe status and can request an appeal without seeing internal scores. Lure remains fail closed if required Apple integrity checks or AWS production configuration is absent.
Who receives information
- Amazon Web Services for Cognito, databases, storage, delivery, moderation, logging and server functions.
- Apple for Declared Age Range, App Attest, AppTransaction and consent withdrawal notifications.
- GIPHY when you choose a GIF.
- Ko-fi when you visit a creator page or connect a verified webhook.
- Apple or a push delivery provider when notifications are enabled in a supported client.
- Advisers, regulators, courts or authorities where reasonably necessary or required by law.
Approved profile and content information is visible to authenticated eligible Lure users. The public web start page does not fetch user generated content for signed out visitors.
Overseas processing
Primary Lure application resources are configured in the AWS Sydney region. Providers and their subprocessors may process support, security, delivery, age assurance or service information outside Australia, including in the United States and other locations where they operate. Processing locations can change with provider infrastructure. Protections in another country may differ from those in Australia.
Retention and deletion
| Record | Retention |
|---|---|
| Account, profile and user content after deletion request | Deleted or deidentified within 30 days unless a permitted hold applies |
| Post deletion authorization marker | Cognito subject and deleted status only, scheduled for automatic removal after 24 hours |
| Apple assurance challenges | Five minute validity, then automatic removal after a short safety margin |
| Apple assurance key and active app binding | While needed for account integrity, then removed with account deletion |
| Protected Apple consent revocation marker | Retained without the account or raw Apple identifier while needed to prevent a withdrawn transaction being reused |
| Web age self attestation | Up to 365 days unless replaced or removed with account deletion |
| Safety reports, moderation records and appeals | 24 months, or longer under a documented legal hold |
| Financial tip records | 7 years |
| Service logs | 90 days |
| Rolling backups | 35 days |
| Upload quarantine | Usually 7 days |
| Temporary moderation artifacts | Usually 30 days |
A legal hold can pause scheduled deletion for a relevant safety, support or financial record. Aggregated or deidentified statistics may be kept where they no longer identify a person.
Your choices and requests
You can edit profile information, change visibility settings, remove your own content, manage blocked accounts and request permanent deletion in Profile Settings. Account deletion requires a recent sign in, a new confirmation and provides a receipt that can be used to check progress after sign out.
Email shahhinsarlak@gmail.com to request access, correction or deletion, to make a privacy complaint or to appeal a moderation or age decision. Lure may need to verify your identity without asking for more information than is reasonably necessary.
If the Australian Privacy Act 1988 applies and a complaint is not resolved, you may contact the Office of the Australian Information Commissioner at oaic.gov.au.
Security, incidents and changes
Lure uses HTTPS, managed access controls, encryption at rest and private server side authorization checks. No system is completely secure. Where law requires it, affected people and the relevant regulator will be notified of an eligible data breach.
This policy may change as Lure, its providers or legal obligations change. The updated date will change and material changes will receive additional notice where required.