The PRESTIGE FUNDING LIMITED platform uses a limited set of cookies and storage technologies to keep the session running, protect requests, and remember your decision regarding measurement.
Necessary cookies
- The session cookie links the browser to the sign-in session and maintains the state of the request. The platform may also use a security token to prevent request forgery.
- These cookies are necessary for security and account functions, and they are not used to build an advertising profile based on your balance or transactions.
- A sign-in session may remain active until the configured inactivity period expires, or it may end upon sign-out or upon revocation for security reasons.
- The protection system uses a necessary cookie that holds a random value containing no name, phone number, or balance. The database stores a hashed fingerprint of this value, not the value itself, and that fingerprint is used together with independent evidence to detect artificially created accounts. Deleting the cookie generates a new value and does not erase security records or existing financial rights.
Your decision on Meta measurement
When Meta tools are configured, measurement is enabled by default on the permitted pages and events. You can open the measurement settings at the bottom of the site at any time to turn measurement off or back on, and your decision is saved in a cookie set on the platform's own domain. When measurement is turned off, we do not load the Meta Pixel and do not send Conversions API events, and we attempt to remove the associated measurement cookies from the site's domain.
Meta cookies while measurement is on
While measurement is on, Meta may create cookies such as _fbp and _fbc to link a visit to public pages, or a conversion, to a campaign. The event catalog covers public pages, account creation, choosing to contact support, a purchase event when a USDT purchase or deposit is completed, and withdrawal request status events upon submission, approval, or rejection. Withdrawal events do not include the wallet address, the reason for rejection, the proof, the account balance, or verification documents.
While measurement is on, and only then, the platform also creates a random identifier on its own domain that does not describe its holder and that the page's scripts do not read. It exists so that an event is attributed to a single browser rather than to an IP address shared by thousands of users across carrier networks, and it is sent as a one-way hash from which its value cannot be recovered. It is not created before measurement is allowed, and it is deleted as soon as measurement is turned off.
Managing your choice
You can open “Measurement settings” at the bottom of the site to change your decision, and you can also delete cookies from your browser. Blocking necessary cookies entirely may cause sign-in or protected forms to stop working.
Values in effect
Cookies and storage technologies in use
The following values come from the actual session and measurement settings.
- Platform session cookie
- prestigefunding_session Required for signing in and protecting the session.
- Session idle timeout
- 8 hours The session may end earlier on sign-out or if it is invalidated for security reasons.
- Session SameSite setting
- LAX
- Meta measurement choice cookie
- prestige_meta_consent Created when the measurement setting is changed, to save whether it is on or off.
- Meta measurement choice lifetime
- 365 days The choice can be changed at any time from the site footer.
- Measurement identifier cookie from the platform's domain
- prestige_meta_visitor A random number that does not describe its owner. It is created only while measurement is on, so that an event is attributed to a single browser rather than to a shared IP address, and it is deleted when measurement is turned off.
- Measurement identifier lifetime
- 730 days It is not readable by page scripts, and it can be deleted from the browser at any time.
- Meta measurement
- On by default and can be turned off