Prototype draft · Updated . Operator details have been supplied. Public launch, real payments, and international availability remain subject to the requirements described below.
About Bazaar Freedom
Bazaar Freedom lets users publish offers and requests, submit fulfillments, exchange messages, follow profiles, and share media. This version is a browser-based prototype. Its account, communication, and transaction features demonstrate how the service works.
Operator and contact information
Bazaar Freedom is operated by Writers Renaissance LLC, a New Jersey single-member limited liability company operating in New Jersey, United States.
For customer support, legal and privacy requests, use the contact email below.
Legal, privacy, accessibility, and general operator contact: bazaarfreedom8@gmail.com. Email links open your email application; you must send the message yourself. The on-site prototype support form does not send email.
This customer-support email was supplied by the operator. The email is not a representation that a copyright agent has been registered, a court has been selected, or every country has been approved for service.
Terms of Service
Scope of these draft terms
These terms describe the Bazaar Freedom prototype operated by Writers Renaissance LLC in New Jersey, United States. They are a draft for the current demonstration, not the completed terms for a live paid marketplace. Final commercial terms and any regional requirements must be presented before real transactions are enabled.
Age and regional availability
The intended service is for people who are at least 18 years old and have the legal capacity to enter the applicable transaction where they live. Signup now requires adult-eligibility self-attestation and acceptance of the current prototype terms, recorded with the document version on the server. This is not independent age verification or completion of every country’s age-assurance requirements. Final paid terms require their own acceptance before real transactions.
The operator intends international availability. Availability of browsing, accounts, purchases, sales, delivery, and payouts may differ by location. Real-money features must be limited to places, people, transaction types, and payment methods supported by the selected providers and permitted by applicable law. Worldwide access is not a promise of worldwide payment or payout availability.
Accounts and responsible use
Use accurate information where requested and do not impersonate another person. Only use an account you are authorized to access. New accounts use server-verified sign-in, salted password hashes and protected session cookies. Existing browser accounts must be migrated by the operator; old browser records or backups may still contain legacy credentials until migration. Posts, profiles, conversations and new uploads use server authorization. Existing browser content requires verified migration. Retained originals, backups and remaining legacy features still need separate handling; production security review is not complete.
Requesting $, Offering $, and fulfillments
Requesting $: the poster supplies an item or service and receives payment from the buyer. Offering $: the poster pays another user who supplies the item or service. These labels describe the money. Payments in this version remain simulated.
Describe the item or service honestly, including its format, price, delivery expectations, and relevant limitations. Do not claim to have completed a fulfillment or delivered an item when you have not. Participants should clarify expectations before exchanging material. Ratings, completion counts, and other credibility indicators do not guarantee identity, quality, or future performance.
Simulated payments
Amounts, payment proposals, purchases, and withdrawals are demonstration records only. No payment processing or escrow service is provided by this version. A simulated acceptance or balance is not proof that money was paid or received. Real payment, refund, fee, tax, and dispute rules must be established before financial transactions are enabled.
Finance → Marketplace payments provides a separate Stripe integration with server-stored payment listings and orders. It is disabled until the operator configures Stripe; test mode does not collect or pay real money. Its checkout shows the seller, price, delivery and refund terms and the payment mode. Historical simulated balances are never converted into money owed or available for withdrawal. Final commerce terms and the remaining launch work are required before live use.
Delivery and rentals
If participants select physical delivery, both must agree to the shipping arrangement before sharing addresses through the delivery feature. Carrier services are arranged separately; a user-entered tracking number or receipt confirmation is not independently verified delivery. Rental dates, pricing periods, possession and return arrangements, shipping charges, and responsibilities must be agreed before proceeding. The current prototype does not collect shipping charges, rental deposits, or damage payments.
Content permissions
You remain responsible for the content you submit and the permissions needed to share it. Submission allows the prototype to store and display that content to the audience selected through its features, and to process optional display translations. Uploading does not transfer ownership of your content. Do not assume another user’s uploaded work is licensed for reuse, resale, or publication.
Prohibited conduct
- Fraud, impersonation, harassment, threats, exploitation, or unlawful discrimination.
- Sharing stolen material, unlawful intimate imagery, or personal information without a lawful basis.
- Violating intellectual-property rights or misrepresenting the origin or authenticity of media.
- Distributing malware, attempting unauthorized access, or interfering with the site.
- Using offers, requests, or messages to arrange illegal activity.
Reports and disputes
Contact Support now sends reports to the operator’s server inbox, with a report ID and a response history. Older local reports and other prototype flagging controls are not proof of delivery; use Contact Support for an issue that needs operator attention. You can also email bazaarfreedom8@gmail.com. Closing a report does not itself remove content, reverse a payment or erase records. Complete moderation, removal, appeals, refund and dispute operations still need work before public launch. This is not an emergency-response service.
Availability and reliance
Features may be incomplete, change, or fail. Browser storage may be lost, and content may be inaccurate or unavailable. Keep separate copies of anything important. Automatic translation and user-generated information should be checked before you rely on them.
Ending use and legal rights
You can stop using the prototype at any time. Account deletion has the limitations described in the Privacy Policy. The operator’s New Jersey location does not remove mandatory consumer or privacy protections that apply elsewhere. These draft terms do not impose mandatory arbitration, select an exclusive court, or set a liability cap. Final governing-law and dispute provisions require review for the locations actually served.
Community Guidelines
Respect other users
Do not harass, threaten, impersonate, or expose another person’s private information. Keep posts and messages relevant and respectful.
Honest participation
Describe requests, offers, and fulfillments accurately. Honor stated Non-AI Generated requirements and do not misrepresent your identity or work.
Reporting concerns
Contact Support sends reports to the operator inbox. Check your report ID and status; receipt does not mean a moderation or removal action has been completed. You may also email bazaarfreedom8@gmail.com directly. Older local reports need to be resubmitted if they still require attention.
Acceptable Use Policy
Responsible use
Do not use requests, offers, uploads, or messages for scams, prohibited or illegal content, privacy violations, or unsafe delivery arrangements.
Content and access
Share only material you own or have permission or another lawful basis to share. Do not attempt to access another user’s account or interfere with the site.
Current limitations
These draft rules describe intended use. Enforcement procedures and operator-specific policies must be finalized before public launch.
User content and intellectual property
Posts, files, profile images, and statements come from users. Their appearance on the site is not verification or endorsement. Share only material you own or have permission or another lawful basis to share. Report content that infringes rights, invades privacy, or misrepresents another person.
Copyright / DMCA Policy
Respect ownership
Share only material you own or have permission or another lawful basis to share.
Copyright notices
Copyright questions can be emailed to bazaarfreedom8@gmail.com or submitted through Contact Support’s Copyright category. A registered designated agent and the complete notice and counter-notice procedure have not been confirmed. An operator-inbox receipt does not establish DMCA safe-harbor eligibility or complete a legal notice/counter-notice procedure.
Policy status
The operator must complete the notice, counter-notice, and repeat-infringer procedures before this becomes an operational Copyright / DMCA Policy.
Identity and confidentiality
Usernames, profiles, uploaded media, messages, and other information may identify you or someone else. Review your privacy settings and avoid sharing confidential or sensitive records.
Privacy Policy
Information this version stores
The site stores account details, profile information, photos and backgrounds, posts, media, messages and drafts, follow relationships, notifications, settings, reports, location choices and simulated transactions. The server stores usernames, contact emails where supplied, salted password hashes, session records, roles and agreement history, delivered operator cases and responses, private conversations and drafts, referral rewards and simulated discount purchases, agreed delivery arrangements and private business bookkeeping. Posts, profiles, privacy preferences, follows/blocks and new uploads now have server storage. Existing browser collections and IndexedDB media require verified admin migration; originals are retained. Older browser account records and backups may still contain legacy credentials until migrated.
When Marketplace payments is configured, the server stores public payment listings, seller account references, order participants, prices, accepted payment terms, payment/refund/dispute status and audit records. Stripe receives card and seller onboarding/banking details on its own hosted pages; this site does not collect full card or bank numbers in that flow. Order details are restricted to their buyer and seller; authorized operator refund actions are audited. Clearing browser data does not erase these server or provider records.
How information is used
These records support sign-in, profiles and posts, conversations and fulfillments, saved items, contact lists, notifications, credibility statistics, preferences, referrals, delivery, payments, operator requests and business recordkeeping. Server sessions authorize protected account, conversation, payment, delivery, referral, operator-inbox and accounting APIs. Existing browser content/media can be migrated by the operator with verified acknowledgments. Saved-post copies, notifications, ratings/activity and simulated marketplace records still need their own coordinated server/privacy workflows.
Visibility and profile choices
Public posts and visible profile sections are shown through the site’s feeds, profiles, search, and contacts. You can change profile visibility under Profile privacy on your profile or in Settings. Hiding a profile section changes that display; it does not remove existing posts, contact references, or copies of your content elsewhere.
Server checks now enforce migrated post audiences and profile field privacy, including private drafts, named recipients, follows, location audiences and hidden profile fields. Someone with access to the browser’s stored data may inspect that legacy content. Private conversations use server participant checks; an admin role alone cannot browse another user’s conversation. Server account passwords and sessions are handled separately; changing browser role metadata does not authorize protected server APIs. Separate uploads, downloads and backups still need their own access/removal handling. Avoid confidential content until the remaining controls have been completed and reviewed.
Server sessions and operator reports
Sign-in uses an HttpOnly session cookie and a random tab selector in session storage so different tabs can use different accounts. The server stores session hashes, expiry and account audit events. Password changes and deactivation revoke sessions. Temporary abuse-prevention counters use connection information in server memory; hosting logs depend on the deployment provider.
Contact Support stores the category, reply email, message, relevant content reference and any required request declarations on the server. Administrators can record a response, review status, identity-verification assessment and private notes. Signed-in users see their own cases. Guests receive a private receipt that grants access to their case; receipts are kept in the current tab and can be downloaded. Keep that receipt private. Operator notes are not shown to requesters. A received report or privacy request is not automatic fulfillment, content removal or deletion.
Location and Global View
Location features can use a location you enter or coordinates obtained when you choose a device-location control and grant browser permission. Global View user-location sharing is an optional setting; shared primary locations or coordinates can contribute to approximate concentrations on the map. Post maps can also show location information associated with visible posts, subject to the post’s visibility and applicable location-sharing controls. Device permission is separate from deciding to share information with other users.
Map areas and place centers are approximate and do not show a continuous live tracking feed. Approximation and grouping do not guarantee anonymity, especially where few people are shown. Changing sharing settings affects later displays but cannot retract information already seen, copied, or exported. Avoid entering a precise private address as a public post or profile location.
Delivery addresses and tracking
The server stores agreed delivery records, shared sender and recipient addresses, any contact information included in those addresses, tracking details, and the delivery history. Addresses are shared with the other participant after both users agree to the arrangement. They are not part of a public map. Tracking links lead to an external service when you choose to follow them. Canceling an arrangement or clearing browser data does not automatically delete its server records.
Private business bookkeeping
Authorized administrators can enter real business transactions, import statements, attach receipts, reconcile accounts, and save tax-planning inputs on the server. Those records are separate from simulated marketplace purchases and are restricted by the accounting access controls. The operator uses them for business administration and recordkeeping. Supporting records may contain information about business counterparties. They are retained with their correction history and private backups; they are not automatically removed by browser-data or profile deletion controls.
Optional Microsoft translation
American English is the default. When you are signed in, select another display language and translation is enabled, displayed text—including posts and messages—is sent through the site’s translation server to Microsoft Translator. Translated results are cached in page memory and cleared on account changes. Account-security and operator-case controls are excluded. Original stored content and unsent input values are not replaced by translations. Requesting the available language list also contacts Microsoft through the server.
See Microsoft’s Translator data and privacy information for the provider’s practices. Translation is optional; return to American English to stop requesting further display translations.
Optional site assistant
The assistant provides local site-help answers without sending your questions to an AI provider. When you are signed in, AI is configured and enabled, and you select AI mode, your question and recent assistant-chat turns are sent through the server to OpenAI. The assistant does not automatically read your posts, messages, password, or account details. Chat stays in page memory and is cleared on reload or account changes. Clear chat removes the local conversation; it does not retract requests already sent to a provider. Optional display translation does not process assistant chat.
Optional-service usage is limited using private account-linked counters. These store reserved attempts, character totals and time windows, without chat/translation text or provider keys. Your own counters are included in the server-data download; they are also retained in private server backups. Limits do not guarantee a provider spending ceiling.
Browser storage and external requests
This implementation uses browser storage for functionality and preferences; no advertising or analytics integration is included in the current code. If the site is hosted online, the hosting provider may receive connection information such as IP addresses and request metadata. Hosting-specific logging and retention must be disclosed when a provider is selected. Following an external link is subject to that destination’s practices.
Paid-order shipping uses private participant records for mutually agreed address sharing, tracking and parcel receipt. Shipping dialogs are excluded from automatic translation. You can remove your own shared address from the current server shipment without contacting the payment provider; counterpart copies and retained backups remain separate. Carrier fees are paid externally, and parcel receipt does not change item-payment status.
Retention and deletion
Local records remain until removed through available controls or by clearing browser data. There is no complete automatic retention schedule. Account deactivation revokes server sign-in sessions; it does not erase associated records. Removing a local profile does not delete posts, messages, media, cases, settings, authentication history, referrals, delivery records or required business records. The associated-data deletion control now opens a privacy request for review. Coordinated erasure, backup expiry and legal-retention exceptions still need implementation before public launch.
Deleting a message thread removes it from your list and deletes your saved draft. Conversation records remain for other participants and may reappear if you start that conversation again. Clearing the site’s browser data removes locally stored records for all accounts in that browser, not just your current account, and may be irreversible. It does not delete exported files, screenshots, or other people’s copies.
When an operator applies exact-bundle removal, private file fingerprints and decision records remain to block matching complete-bundle reuploads. File removal does not erase those denial records or retained backups. Transformed files, different file combinations and external copies require separate review.
Your choices and privacy requests
You can edit profile details, change profile visibility, choose whether to use translation, and manage content using the controls provided. For privacy access, correction, deletion, or other applicable rights requests, email Writers Renaissance LLC at bazaarfreedom8@gmail.com. Describe your request and provide enough information to locate the relevant account or record. Do not send passwords, payment-card details, or unnecessary identity documents. Additional verification may be needed before private information can be disclosed or changed.
You can also submit a Privacy request through Contact Support and track its status and responses. Settings offers a password-protected download of authorized records from eleven server sources, including owned posts, conversations, current-environment payment records and upload metadata. Media bytes, unmigrated browser originals, retained backups and some separately held records require separate handling; the download explains its scope. The operator inbox supports review and verification records; complete cross-system fulfillment, erasure and applicable appeals still need work. Applicable legal rights and deadlines are not waived by the prototype’s limitations.
Changes
This notice must be updated when data handling changes, particularly before adding hosted accounts, real payments, analytics, or additional service providers. The revision date above identifies this draft.
Cookie Policy
Cookies and browser storage
Server sign-in uses functional HttpOnly session cookies. A tab selector, display identity, preferences and prototype feature data use browser storage. Guest report receipts may be stored in the current tab. Clearing local site data removes local records and receipt copies; it does not automatically delete server records.
Cookie and consent status
The Privacy Policy describes the current prototype’s data handling. Browser storage is relevant even when a feature does not use cookies.
Before public launch
The operator must verify deployed cookies, storage, and external services and complete any applicable consent and retention details.
Payments and balances
Purchases, payment offers, balances, and withdrawals in this version are simulated. They do not transfer money, establish a bank balance, or provide escrow. Bank information fields store account labels and the requested last four digits for demonstration; do not enter full account or payment-card numbers.
Payment, Refund & Dispute Policy
Simulated transactions
Purchases, payment offers, balances, and withdrawals in this version are simulated. They do not transfer money or provide escrow.
Post labels
For Requesting $, the poster supplies the item or service and receives payment. For Offering $, the poster pays the user supplying the item or service.
Refunds and disputes
No payment-processing, refund, chargeback, or payment-dispute service is connected. Report incorrect simulated balances or transaction records through Contact Support.
Before real payments
The intended provider is Stripe. The operator must first complete the applicable marketplace payment setup, seller onboarding, supported-country checks, and payment/refund/dispute workflows. Checkout must identify the seller, describe what is being purchased or rented, and disclose the total price, currency, fees, taxes, delivery charges, applicable cancellation terms, and payout conditions before payment is authorized. Mandatory consumer rights cannot be removed by a seller’s policy.
Reports and urgent situations
Use Contact Support to send a problem to the operator inbox, identifying the relevant post or account and explaining the issue. Keep the report ID and, for a guest request, its private receipt. No email is sent automatically by the form. You may separately email bazaarfreedom8@gmail.com. The operator must monitor and act on reports; this site is not an emergency service. Contact the appropriate local emergency service when immediate help is needed.
Nonconsensual intimate imagery
Do not post or share intimate images or videos of another person without their consent, including altered or AI-generated intimate depictions.
To contact the operator about removal, email bazaarfreedom8@gmail.com with the subject “Intimate-imagery removal request.” Identify the affected person or your authority to act for them, describe where the content can be found (such as a post link, post ID, or account), give contact information for a response, state your good-faith belief that the depiction was shared without consent, and include your physical or electronic signature, such as your typed name. Do not attach intimate imagery or unnecessary identity documents.
You can also use Contact Support’s Intimate imagery category to deliver these details to the operator inbox and receive a report ID. The inbox tracks an urgent review target; it does not automatically remove images or identical copies. Complete removal, duplicate handling, monitoring and escalation remain launch requirements. Applicable removal obligations and deadlines are not waived.
Translations and external services
Automatic translations may change meaning or omit nuance. Check the original text before relying on a translated offer, request, or legal document. External services have their own terms and privacy practices.
Document status
These pages describe the current prototype and the operator’s planned 18+ international service. Server account sessions, password hashes, role checks, adult self-attestation, prototype agreement records and a delivered operator inbox are now implemented. Actual source-data migration, isolation of remaining legacy feature records, complete security review, stronger age assurance where required, coordinated privacy fulfillment/retention and safety/removal operations, supported countries, production hosting and real provider verification remain unfinished launch requirements.
This document is not a certification of legal compliance or approval to launch in every country. Adding these notices or connecting Stripe does not complete those operational requirements. The draft date is not a certification date.