Published by FVA70K Services. Proposed official version: 2026-11-01-safety-proposal. This version is a proposal, not yet effective, until Fortune sets the effective date and approves this version.
Contact: FVA70K Services, [email protected], No. 1 Jude Edward Okeke, Ibusa Road by ULO Junction, Asaba, Delta State, Nigeria. LinkedIn: https://www.linkedin.com/in/fortune-godson. The privacy contact proposal is recorded in the decisions record, and is not settled until Fortune confirms it.
This version describes only what Fva Connect does today. Anything not yet decided is stated plainly as not yet decided, instead of being guessed.
Fva Connect is a professional and social network run by FVA70K Services. You create an account, post updates, connect with people, send messages, and view or post opportunities.
When you register with email and password, Connect stores your name, your email address, and your password in hashed form, so the password itself is not kept in readable form. Your password must be at least 10 characters long and include an upper-case letter, a lower-case letter, and a number.
Inside Connect, you also create the things you post: updates, comments, likes, connection requests, messages, job posts, job bookmarks, and job applications. Each post carries the visibility you choose: Public, Professional, or Connections.
If you choose Continue with Google, Connect receives your verified email address and your name from Google. If you choose Continue with GitHub, Connect receives your verified primary email address and your name or username from GitHub. Connect does not keep your Google or GitHub sign-in token after sign-in. Provider sign-in is live with Google and GitHub. Microsoft is parked, and Apple is unlicensed. Provider sign-in was set up on 2026-10-25, which is the provider setup completion date on record, not a new claim.
Connect has a verification step for email accounts. A verification email sender address, [email protected], has been set in the service settings, but email verification has not been proven live by a test-account send, so this version does not claim email verification is live. Provider accounts are different: they are marked verified because the provider already verified the email address.
Under the Nigeria Data Protection Act 2023, FVA70K Services must tell you who else receives your personal data. These are the only recipients.
Zoho Mail sends every email Connect sends, including sign-in verification codes, password resets, and job application notices. Zoho receives the recipient email address, the subject, and the message text. The emails come from [email protected].
Google and GitHub handle sign-in when you choose them. When you choose Continue with Google, your browser is sent to Google with a request for your email address, your name, and confirmation that your email is verified. Google then returns your verified email address and your name to Connect. When you choose Continue with GitHub, your browser is sent to GitHub with a request to read your profile and your email addresses. GitHub then returns your verified primary email address and your name or username to Connect. Connect does not keep your Google or GitHub sign-in token after sign-in, and it does not send your Connect posts, messages, or password to Google or GitHub.
Cloudflare hosts Connect. Your account and posts are stored in its database, and files you upload are stored in its file storage. Cloudflare receives the data needed to run the service, and it processes that data only to provide the hosting and storage Connect uses.
Three other companies supply files that the Connect pages load. Tailwind CSS supplies page styles from cdn.tailwindcss.com. Lucide supplies icons from unpkg.com. Leaflet supplies maps from unpkg.com. When a page loads, your browser fetches those files from their servers, so each of them sees that your browser visited a Connect page, including your IP address. They do not receive your name, your email address, your posts, or your messages.
Connect does not use analytics, advertising pixels, or crash reporting tools. None of those is loaded, and no data is sent to any analytics or advertising company.
Public posts are visible to signed-in Connect users. Connections posts are visible only to you and to people whose connection with you is accepted. Your own posts are always visible to you. Messages in a conversation are visible only to the two people in that conversation. You can delete your own posts. Admins can suspend accounts and hide or restore posts, and admin checks are recorded under a Trace ID.
Two-factor sign-in, where you turn it on, uses an authenticator app only. Email codes are never accepted as a second factor. After 5 failed sign-in attempts, an account is locked for 30 minutes. The human check, FVAVerify, must pass before registration or sign-in when it is active; when its site key and secret are not set, the check box is hidden and sign-in does not use it.
Signing in creates a session that lasts 7 days. You can see your sessions in your profile and revoke one session or all sessions. Signing out clears the session cookie. Details of each cookie are on the Cookies and Data page.
You can close your own account from your profile, with a 30 day grace period, as in the closure section below. To ask about deletion or download, contact FVA70K Services at [email protected].
No general retention period is set in this version, and this version does not promise automatic deletion after any period, except for the account closure rule in the closure section below: after the 30 day grace period, a closed account is deleted and its posts and comments are anonymised. General retention periods are still to be decided, and are recorded in the decisions record.
For privacy questions and requests, contact FVA70K Services at [email protected]. That address is proposed as the privacy contact in this version, and is not settled until Fortune confirms it, as recorded in the decisions record.
Connect has one suspension system. A temporary suspension has an end date. A permanent suspension is called a ban and has no end date. There is no separate ban system. Only an admin with the users suspend permission, or the founder, can suspend or ban an account, and the founder account cannot be suspended or banned, and no one can suspend or ban their own account. A reason is always required. Every suspension, ban, unban, and suspension change is recorded with the actor, the affected user, the old state, the new state, the reason, and the time. A suspended or banned account cannot sign in, and a user who is already signed in sees a suspended screen on the next protected load. While suspended, the account cannot use the feed, posts, messages, groups, or jobs. A suspended account can still see its own suspension status, its own appeal status, and safety messages about its own account, and can still appeal and contact support, and nothing else while suspended. When an account is banned, its posts are hidden and its sessions are deleted. Unbanning does not automatically restore hidden posts. A suspended or banned account profile is not shown as if it were active, and no private field is shown to other viewers. A ban or suspension never proves a crime.
A suspended or banned user can appeal from the suspended screen, with an appeal message. One appeal per suspension is allowed, and the appeal window is 30 days from suspension. These two rules are proposals in this version and are flagged as proposals in the decisions record, because Fortune has not set them in words. An appeal is reviewed by a human only. No appeal is approved or rejected automatically, and no account is unbanned automatically. A rejected appeal shows the reason to the user. An approved appeal unbans the account. Support is by email at [email protected], and by the in-app appeal form and the in-app safety report form. There is no separate in-app support chat in this version.
Do not use Connect to impersonate another person, to harass another user, to post content you do not have the right to share, to share another person's private information, or to try to break sign-in, sessions, or the human check. You can report a post, comment, message, profile, group, squad, organisation, job, or event, from your profile, with the item ID and a reason. Every report is reviewed by a human. Reporting alone does not ban, hide, or suspend anything automatically. A human reviewer may separately hide a post or suspend an account, using the existing moderation routes, and that action is recorded. Blocking is not built in this version: you cannot block a user, and this policy does not promise blocking. Identity verification is human admin review only, and it proves only that identity was checked by an FVA70K admin, nothing else. Organisation verification is page-admin only, and it proves only organisation page verification, nothing else. Licence verification is manual review, and a licence Verified label proves only that that licence entry passed its checks or manual review, never identity. Premium never proves identity, never proves legal identity, and never proves registration.
You can close your own account from your profile, with a Tap again to confirm step. Closing starts a 30 day grace period, which is a proposal in this version and is flagged as a proposal in the decisions record, because Fortune has not set it in words. During grace you can sign in and reopen your account. After 30 days the account is deleted: its name becomes Closed account, its bio is cleared, and its posts and comments are anonymised to a removed notice. Messages are not deleted by closure: the other person keeps their copy, and a closed account cannot be messaged. Your organisations are not deleted or transferred automatically: you must close or delete each organisation you own first, from its organisation page, before closing your account. Groups and squads you own are not deleted automatically. Premium is cleared at deletion. Closure never deletes another user's data.
You can set a next of kin in your profile, with full name, relationship, and contact, with a confirmation step. You can change or remove your next of kin at any time. Your next of kin can ask for memorial, closure, or a download of your public posts after your death, once a human has checked proof. Your next of kin can never sign in as you, read your private messages, change your password, or post as you. Your next of kin is never shown publicly, in search, in the feed, or on your profile. Contact confirmation for a next of kin is not built as an automated step in this version: an admin contacts the next of kin to confirm before acting on a death request.
When the owner of an account dies, the set next of kin, or a family member with proof if no next of kin is set, can send a death request, choosing memorial, closure, or a download of public posts. Proof is checked by a human before any action. The exact proof document type is a proposal in this version and is flagged as a proposal in the decisions record: a death certificate, a court letter, or an authority letter, sent to support by email, because no death proof file upload is built in this version. Memorial means the account is marked memorial, it cannot sign in, and its posts remain visible. Closure means the account is deleted and its posts and comments are anonymised, as in the closure section above. Download means a download of public posts and profile information only, prepared by an admin and sent through support: no automatic download file is built in this version. No private message, password, or private document is ever given to a next of kin or family member. Inactivity alone is never treated as proof of death, and no account is memorialised or closed for inactivity alone. Every death-related action is recorded with the actor, the affected user, the action, the old state, the new state, the reason, and the time.
Proposed official version 2026-11-01-safety-proposal, published by FVA70K Services. Not yet effective until Fortune sets the effective date and approves this version.