FictionCom beta privacy notice

Updated October 2, 2026. The beta is operated by @dgueye1 in Georgia, United States. This notice describes the current beta; public launch still requires policy review.

Your account and data

Supabase handles your account email, authentication and password security. FictionCom stores your chosen profile, posts, uploads, follows, comments, likes, story views, saved posts, series progress, profile shelves and pins, dismissed suggestions, private story reactions/replies, blocks, reports, private chat messages and requests, chat read markers, support messages and app feedback. Signup asks you to confirm that you are at least 14; we do not ask for your birth date.

Who can see content

Public posts can be browsed without an account. Private posts require an accepted follow. Story owners can see their signed-in viewer list. Story reactions and replies are visible to their sender and the story owner; owners can restrict who may respond. Profile shelves and pinned posts follow profile/content privacy rules. Saved posts, reading progress and support messages are private to you, with moderator access to support messages. Moderators can inspect reported and private uploads to enforce community rules. Other users may save copies of content they can view.

Private chats are visible to their participants. Messages from people you do not follow arrive as requests; you can accept or deny them. Denying a request removes its messages and retains a declined conversation record to prevent repeated requests. Unread counts exclude your own outgoing messages. Feedback is submitted privately through the moderator Support inbox.

Services and technical information

Supabase stores account and community data. The server queries Kitsu to provide anime and manga search suggestions; search text is sent to that catalog service. Login sessions, opened-story history and the time of your last visit alert are stored on your device. FictionCom uses a keyed, irreversible hash of the connection IP and a 30-minute time window to avoid duplicate visit alerts; it does not store the raw IP for this feature. The operator receives email alerts for visit sessions, registrations, support and feedback through Brevo. Alerts include the event time and relevant account or request identifier; message content stays in the moderator inbox. Delivered alert records are removed after 30 days. Post drafts, including selected files, are saved in this browser’s local storage database until posted or discarded; keep shared devices secure. Error monitoring sends only runtime/async error categories, not captions, email addresses or authentication tokens. AI review is disabled; uploads are not sent to an AI provider.

Membership and payments

When subscriptions are activated, FictionCom records your one-time trial dates, Stripe customer/subscription identifiers, subscription status and paid access period. The trial lasts 7 days and requires a card through Stripe Checkout. After the trial, Stripe automatically charges $5 USD per month unless you cancel before it ends. Stripe handles payment details through its hosted checkout; FictionCom does not store card or bank account numbers. Subscription access is updated using verified Stripe events. You can contact Support and manage or delete your account after your trial expires. Stripe retains payment records under its own policies. Live Stripe checkout is enabled.

Retention and controls

Stories stop appearing after 24 hours. Their files can remain stored until cleanup runs. Use account settings to block accounts, request help from the moderator or permanently delete your account. Account deletion first removes uploaded files, then removes your account and associated community rows. If deletion fails after file removal, your account can remain visible but new posting and uploads are disabled, and some files may already be gone; retry or contact the moderator. Copies held by other users and provider backups may persist independently.

Questions and requests

Signed-in users can use Support to contact @dgueye1 privately. You can also email doudousygueye1997@gmail.com, including when you cannot sign in. The operator is @dgueye1 in Georgia, United States. Public-launch policy review remains pending. Users under 14 should not register or post.