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 names only the cookies and stored data Connect actually uses today. Anything not yet decided is stated plainly as not yet decided, instead of being guessed.
When you sign in, Connect sets a cookie named fva_connect_session. It holds your session token, lasts 7 days, and is marked HttpOnly, Secure, and SameSite=Lax, so page scripts cannot read it. Signing out clears it, and revoking all sessions in your profile clears it too. Only the hashed form of the token is stored on the server.
When you choose Continue with Google or Continue with GitHub, Connect sets a cookie named fva_connect_oauth_state. It holds a one-time check value for that sign-in attempt, lasts 10 minutes, and is marked HttpOnly, Secure, and SameSite=Lax. If the returned value does not match, provider sign-in fails closed and you are not signed in.
Your Dark, Light, or Auto theme choice is stored on your own device only, not in a Connect cookie and not on the server. Clearing your browser storage resets it to the default.
Connect itself does not set advertising cookies and does not set tracking cookies for other sites. The human check, FVAVerify, does not use a Connect cookie: its pass is sent with the registration or sign-in request itself. The pages load a styling script from a content delivery network; that script is not a Connect cookie and Connect does not use it to track you.
Connect stores your name, email address, and hashed password; your profile details; your posts, comments, likes, connections, messages, and job posts, bookmarks, and applications; your sessions; and a record of admin checks under a Trace ID. Passwords are stored hashed, never in readable form. Provider sign-in tokens are not kept after sign-in.
Connect has no account deletion route yet and no data download route yet, so this version does not describe how deletion or download would work, and does not promise a timeframe or a method for such a request. To ask about deletion or download, contact FVA70K Services at [email protected]. No retention period is set in this version, and this version does not promise automatic deletion after any period.
Signing out clears the session cookie. To end every session at once, revoke all sessions in your profile, then sign in again. Clearing cookies in your browser also ends the session on that browser.
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.