Privacy Policy

Responsibility and contact

Flieva is owned and operated by Flieva LLC, company number 2026-002099858. Office address: 30 N Gould St, STE R, Sheridan, WY 82801, United States. Contact support@flieva.com for support, account, subscription and privacy enquiries. Flieva LLC is responsible for the personal data processed through Flieva. For access, correction, deletion, portability, consent withdrawal or other privacy enquiries, contact the email above. This notice describes the service and does not claim universal regulatory compliance.

Accounts and age confirmation

We collect your email, account identifier, name if supplied, verification status, session details, age-range declaration and accepted policy version to create and secure your account, recover access, identify your saved records and communicate about the service. Supabase Authentication handles passwords; Flieva does not store raw passwords in planning records. Remember me keeps authentication in persistent browser storage; otherwise session storage is used. Administrator access requires an authenticator check. For supervised accounts aged 13–17, we also process the guardian consent information described below. We do not require a passport or date of birth merely to confirm the age range.

Saved planning and CV data

Signed-in journey answers and Track checklists are stored privately in your Supabase account and loaded when you sign in on another device. Paid CV drafts, photographs and saved versions also sync through private account records. A browser copy is used while you work; saving reports a failure if the account copy cannot be updated. Free CV previews remain unsaved. Saved tool drafts, deadlines and source bookmarks also sync privately to your account. Preferences and chat history may remain in your browser. Clearing browser storage is separate from deleting cloud records.

Private document vault

The vault stores uploaded PDF, PNG, JPEG and TXT files in private Supabase storage, with document names, types, sizes, account ownership and permission dates in the database. Files are limited to 2 MB; plan storage limits apply to new uploads. Your verified administrator may access a document only when you enable assistance permission for that document. You may change that permission, retrieve or delete your file. Plan expiry does not itself erase files or require payment to retrieve or delete them. Saving a document does not send it to an AI provider or use it to train a model. Supabase and hosting providers still process data to operate the private storage service; documents are not shared with employers, recruiters or other external recipients for applications. Authorised Flieva staff may review only documents for which you grant assistance permission.

FlieBot and local checks

When you request a FlieBot answer, your question and selected destination are sent to Flieva’s server. The service selects information from maintained references and connected public official pages. When OpenAI is enabled, your question, selected destination and relevant reference text are sent to OpenAI to generate a response. Flieva requests that responses are not stored as API application state; OpenAI may retain data for abuse monitoring under its own policies. Vault documents are not automatically sent to OpenAI. Chat history may be saved in your browser for your account. Pasted-text scam checks run locally. When you choose a screenshot or file in FlieBot and send your message, that selected attachment is sent through Flieva to OpenAI for analysis. Before sending, a warning identifies this processing and asks you to omit passwords, verification codes, passports, bank details and sensitive personal documents, and hide private details in screenshots. Cancel to avoid sending the attachment. Flieva processes chat attachment bytes in memory rather than saving them in the vault or chat history. The filename and answer may remain in browser chat history. OpenAI may retain submitted data for abuse monitoring under its policies. Private vault files are not automatically sent to OpenAI; selecting a chat attachment is separate from storing a vault file. Remove sensitive information before sending. Do not include passport numbers, financial account details or unnecessary sensitive data in chat or pasted text.

Plan access and usage records

We store an account-linked membership record when a subscription is valid, including tier, activation and expiry dates and payment-provider reference. We also record the feature, request reference, usage period and time needed to enforce trial and plan allowances. This prevents resetting a free trial by changing browsers and supports billing or access enquiries. Current checkout is closed; no card details are collected by this subscription update. Future payment-provider processing will be described before checkout opens.

Referrals and optional WhatsApp

Referral records associate confirmed accounts with their inviter, referral code and signup date to provide the referral feature and prevent misuse. Users see their own referral information; authorised administrators can review account emails and referral relationships. If you enable WhatsApp reminders, we collect your phone number, consent date and notification preference, and process reminder scheduling keys, due times and delivery status to send and troubleshoot requested reminders. Your number and reminder message are shared with Meta/WhatsApp for delivery. The deadline queue uses an opaque key rather than the name of your application. Saving a number alone does not send a message. Turn off WhatsApp reminders in Your connections to stop future scheduled reminders. WhatsApp has its own privacy practices; verification codes through WhatsApp are not currently offered.

Purposes and legal bases

We use account, saved tools and document data to provide the features you request; email and support correspondence to resolve enquiries and send necessary account notices; operational and usage records to maintain security, reliability and fair access; and billing records to manage purchases, refunds and applicable accounting obligations. Where applicable law requires a legal basis, requested core services rely on contract or steps you request before a contract, necessary security and service maintenance rely on legitimate interests balanced against your rights, mandatory records rely on legal obligations, and optional WhatsApp reminders and assistance sharing rely on consent. You can withdraw optional consent without losing unrelated features. Optional advertising/analytics consent will be requested where required if those services are enabled. Accepting the Terms does not waive privacy rights or consent to every possible use of your data.

Providers and international transfers

Render hosts the website; Supabase provides authentication, database and storage; The configured authentication email provider delivers account emails; Resend may deliver Flieva transactional notifications. Zoho Mail hosts our support and business mailboxes. Flieva receives transaction references and verified subscription status needed to manage account access and billing support; full card details are not stored by Flieva. Exchange-rate requests, the external Supabase library, optional Google maps and external source links may disclose normal network information such as your IP address to those providers. Maps load only when chosen and do not request device geolocation. Data can be processed outside your country. Applicable provider contracts, processing regions and lawful international-transfer safeguards must be confirmed for the operator before paid launch. We do not claim every provider processes data locally. Paystack is the intended payment processor for Flieva subscriptions. Checkout is not connected yet, and no subscription payment can currently be collected. When enabled, the checkout will show the amount, currency, taxes and renewal terms before payment. Flieva remains responsible for its service and refund policy. For billing or refund requests, contact billing@flieva.com. Paystack payment-processing terms are available at Paystack terms and privacy information.

Retention and deletion

Keep account and saved tool data only for as long as needed to provide your account and requested features, until you delete a record or the verified account deletion process is completed. Device-local records remain until you or your browser clears them. Support correspondence, security records and any billing records may need to be retained after closure only to resolve an outstanding issue, prevent abuse, meet applicable legal/accounting requirements or establish, exercise or defend legal claims. We will explain the relevant reason and retention criteria when responding to your request; we do not promise immediate removal from provider backups or records a payment provider must legally retain. Provider backups and logs follow their own retention schedules and access controls.

Open My account → Settings → Delete account to submit a private account deletion request. You must be signed in, review the consequences and confirm the request. This is a reviewed request, not instant erasure. Send the accompanying email to support@flieva.com from your registered address so Support can verify ownership, arrange deletion of your authentication account, saved CVs, journeys, drafts, preferences and private vault documents, stop account reminders and confirm completion. We will explain any records that must be retained. You may also email Support directly if you cannot sign in. Export anything you want to keep first. Clearing local data, uninstalling the app or signing out does not delete your cloud account. Deletion does not automatically cancel a subscription or grant a refund; manage renewal with your payment provider or contact billing@flieva.com before closure. Requests are handled within applicable legal deadlines.

Your rights and complaints

Depending on the law that applies, you can request access, correction, erasure, portability, restriction, objection or withdrawal of optional consent. Withdrawal does not invalidate lawful prior processing. We will handle requests within applicable legal deadlines and explain any refusal or required extension. You can complain to your competent data protection authority; this can include Nigeria’s Data Protection Commission or an EU/UK authority where its law applies. Selecting a destination alone does not determine which privacy law applies.

Security, children and changes

Access controls, private storage and administrator verification protect account records, but no service can promise absolute security. Independent Flieva accounts are for people aged 18 or older. Under-13 accounts are not offered. For ages 13–17, a parent or legal guardian signs in and submits the signed consent form for Support review. We store the guardian’s account identifier, name, email, typed signature, the young person’s account email, policy version and submission/review dates. This record is private to authorised Flieva reviewers. Account features remain blocked until approval is recorded; consent may be withdrawn through Support. If you believe an underage account exists or data has been exposed, contact support@flieva.com. This version is dated 10 October 2026; material processing changes will be described and any required new consent obtained.

Location and destination information

We use the country, destination, nationality, address or other location information you choose to enter in your profile, journey or CV to personalise research, show relevant opportunities and include the details you request in your documents. Destination selection does not establish your residence or legal eligibility. Hosting and other network providers receive your IP address, which may indicate an approximate location, to deliver and protect their services. Flieva does not currently request GPS or precise device geolocation; its browser permissions policy disables geolocation. Optional maps load when chosen and receive normal network information. You can leave optional fields blank or change saved answers; doing so may reduce personalisation.

Device, operational and usage information

When you access the website, our hosting and connected service providers process normal request information such as IP address, browser/user-agent, request time and requested resource to deliver pages, detect errors and protect the service. Browser preferences such as language, appearance and reduced-data settings are stored to respect your choices. Flieva records account-linked feature usage, request references and usage periods to enforce free allowances and plan limits, troubleshoot access and prevent abuse. These operational records are different from advertising or cross-site analytics. We do not currently run a separate marketing analytics tracker or collect your device contacts, private messages or other apps’ contents.

Payment and billing information

Live subscription checkout is currently closed. If you purchase when checkout is enabled, the payment provider identified at checkout processes the payment information you give it, which may include payer name, email, billing address, payment method and bank or card details. Flieva receives the transaction reference, payment/subscription status, plan, relevant billing dates and any receipt information returned by the provider to grant access, handle billing enquiries, refunds and accounting. Flieva does not store full card numbers, CVV/security codes or bank login credentials. Do not send these in chat or support email. Test checkout does not collect a real payment. Creating a merchant account with a provider does not itself enable payments on Flieva.

Advertising, analytics and browser storage

Flieva does not use Google AdSense or load advertising scripts. We do not currently sell personal data or run separate marketing analytics tracking. If advertising or optional analytics is enabled, we will first update this notice and provide any consent or opt-out controls required by applicable law, explaining the provider, identifiers/cookies, purposes and choices. Essential authentication, saved tool records and preferences use browser storage as explained in the Cookies and Browser Storage policy. External websites and providers have their own privacy practices.

Paystack payment processing

Flieva receives payment references and subscription status to provide access and billing support; Flieva does not store full payment-card details. Paystack is the intended payment processor for Flieva subscriptions. Checkout is not connected yet, and no subscription payment can currently be collected. When enabled, the checkout will show the amount, currency, taxes and renewal terms before payment. Flieva remains responsible for its service and refund policy. For billing or refund requests, contact billing@flieva.com. Paystack payment-processing terms are available at Paystack terms and privacy information.

Updated 11 October 2026.

Employer profiles and careers-board connections

We store company legal names, official websites, registration countries, account ownership and review history to operate the free employer workspace. Profile and connection records are restricted to the account owner and authorised Flieva administrators. Approved vacancy details and original application links are public. With the employer’s authorisation, Greenhouse, Lever and Ashby connections read published vacancies. These requests do not send applicant CVs, Flieva accounts, chats or documents to the ATS, and public vacancy feeds do not provide access to private applicant records. Employers can disconnect boards and withdraw listings; cached public results may take up to 15 minutes to refresh. Contact support for company-profile removal or account privacy requests.