Privacy Policy

• Account details such as name, email address and password hash.
• affLIFT username and verification status where provided.
• Basic security/account state such as email verification, admin flags and optional two-factor setup status.
• Upload metadata such as source type, source name, source URL, notes and review status.

Uploaded lander ZIPs are stored privately until reviewed. We may extract metadata, screenshots, file lists, tech-stack information and security findings. Security findings may include filenames, matched risk categories and short pattern labels so admins can decide whether a file should be approved, rejected or sanitised.

• To provide login, membership checks, library access, downloads and package building.
• To review uploads and protect members from unsafe or hijacked landers.
• To troubleshoot bugs, failed imports, missing screenshots and operational issues.
• To prevent abuse, excessive usage or malicious uploads.

When you download a lander, build a package, or follow an outbound link (for example an affLIFT or partner link via our /go/ redirect), we record the event so we can understand which tools and links members use, attribute referrals, and detect abuse.

These analytics events may include your account (when signed in), the lander or destination involved, the placement you clicked from, and technical request details: your IP address, browser user-agent and referring page. Outbound-link clicks are recorded even for signed-out visitors.

This data is used only for product analytics, referral attribution and abuse prevention. It is never sold. Analytics events are retained for up to 12 months and then automatically deleted, and the IP address and user-agent tied to your events are cleared when you delete your account.

Member uploads are not intentionally published to the shared library until they have been reviewed and approved. Operational credentials and secrets are not stored in the public repository. We do not sell member data.

Library records, source metadata, screenshots and scan results may be kept while they are useful for operating the service. Uploaded files may be removed, archived or retained privately for audit/review.

If an account is deleted, personal account fields such as email address and affLIFT username are anonymised before the account record is soft-deleted. Verification and security events may be retained in an audit trail so we can evidence access decisions, investigate abuse and protect the shared library without keeping the deleted username or email on the active account record.

If you need an account, upload or retained audit entry reviewed, contact support@afflift.tools.

We use private storage for uploaded ZIPs, review statuses for unapproved landers, password hashing and standard Laravel protections. No system is perfect, so please avoid uploading secrets, private credentials, customer data or anything unrelated to lander review.