Cookie preferences
Natifly uses necessary browser storage for core features such as sign-in, security, private account workflows, and remembering this choice. Optional Google Analytics cookies are used only if you allow analytics.
Supports essential site, security, account, booking, and consent-preference functions. These are not switched on or off by the analytics choice.
Measures sanitized page categories and a small allowlist of product interactions. The Google Analytics tag stays blocked until you allow analytics.
Google advertising consent signals remain denied by this control. Analytics does not determine qualified creator views or creator earnings. Read the Cookie Notice and Privacy Notice.
Trust Center
Natifly is designed so public travel discovery can coexist with private account and trip information. This page explains the customer-facing protections and status meanings that matter when you use the platform.
Identity and visibility
A creator can publish a username, display name, profile image, headline, biography, location context, home airport, and website when their profile is public. Private-profile identity and private avatar delivery are not exposed as public creator content.
Login, security, membership, private trip, booking, support, and account-management records are authenticated experiences. Public pages are not a shortcut into those records.
Creator content
Public stories use media that belongs to a published, publicly viewable post. Draft, private, or otherwise non-publishable creator media is not used to fill public cards or discovery surfaces.
Natifly aims to use real creator stories, real engagement, real saved items, and real account activity. Empty and low-activity states should be presented honestly rather than filled with fabricated users, stories, trends, or transactions.
Views and creator earnings
Natifly uses server-side timing and abuse controls to distinguish meaningful story views from obvious self-views, automation, duplicate activity, and concentrated abuse. Exact anti-abuse thresholds are intentionally not published because doing so would make them easier to manipulate.
Qualified-view records use derived security fingerprints and timing evidence rather than storing raw browser UUIDs, raw user-agent strings, or raw IP addresses in the qualified-view record itself.
Creator earnings evidence, amounts reserved by payout requests, finance review, and final paid status are different states. An approved payout request is not the same as completed payment; paid status requires confirmed execution evidence.
Travel and booking clarity
Flight prices, schedules, availability, baggage rules, and fare conditions come from travel suppliers and can change. Search results are not reservations.
A saved trip records planning information. A Natifly booking record stores transaction and supplier-reference evidence, but it is not by itself proof that a traveler holds a valid airline ticket.
Travel rights depend on valid supplier or airline confirmation and any required ticket documents. Natifly should never present an unavailable live-travel capability as if it had issued a usable airline ticket.
Payments and memberships
Payment-card details are collected by secure payment components rather than being stored as card-number fields on Natifly servers. Natifly retains only the payment and reconciliation evidence needed for its own product records.
Creator memberships, billing periods, entitlements, and cancellation timing are shown in the creator's account. A successful browser redirect alone does not replace signed billing-provider lifecycle evidence.
Safety and support
Support tickets are requester-scoped private records. Customer-visible threads do not expose internal staff notes.
Blocking is applied across social discovery so blocked accounts are not surfaced through following, saved-story, or notification presentation where the product boundary requires exclusion.
Support may need Natifly, trip, or booking references, but users should never send passwords, MFA codes, full payment-card details, API secrets, passport numbers, or unnecessary passenger identity data.
Operational security
Public trust documentation explains user protections and product meaning. It does not publish credentials, private keys, infrastructure addresses, deployment procedures, fraud-control thresholds, internal approval gates, provider-account configuration, or other operational details that would create security or abuse risk.