TORCPRIVATE TEST ENVIRONMENT

TEST ENVIRONMENTS ONLY · UPDATED 17 NOVEMBER 2026

Your account data.

This notice applies only to Torc's private test environments, which use fictional data. If you are a member of the live service, read the Privacy notice and the other policies instead. In a test environment, use made-up addresses ending in @example.test and do not enter real personal or sensitive information.

Torc is developed by Northmere Software LLC, a Wyoming limited liability company.

What this build stores

An encrypted email address, a keyed lookup value, a random member ID, the date you affirmed you are at least 18, and the notice version. Email possession and your age statement are not identity verification or verified age assurance.

A test product profile stores your display name, handle, selected town/city and country/territory, optional biography, connection intentions, interests and per-interest roles. You choose whether the profile is discoverable. Only interests marked visible, and roles marked visible, appear to other signed-in preview members or affect search. Private interests and hidden roles remain stored for you. Exploring a different area does not relocate your profile. This build also supports photos and writings as described below. Do not enter street addresses, payment details or real sensitive information.

Private favorites, blocks, introduction requests and accepted text conversations are stored in the test social database. Messages are not end-to-end encrypted. The developer can inspect these synthetic databases; access isolation for real users is not established by this preview. Do not enter real health information or other personal data.

Favorites and Sparks

Favorites are a private list. Favoriting someone does not notify them, follow their activity or send a message. Existing saved profiles are now called Favorites.

Sparks are optional interest signals, off until you turn them on. Both people must opt in and have visible profiles. A Spark stores the sender, recipient and sending time, and appears only to those two people. Sending one does not create a conversation or favorite. Dismissing a received Spark hides it for you without telling the sender. Withdrawing removes it from the recipient's Sparks. Blocking, hiding a profile or turning Sparks off removes existing signals in both directions; re-enabling does not restore them.

Sparks expire after 30 days. Withdrawn and dismissed records remain until that expiry to enforce one signal per person every 30 days and 10 signals per sender in 24 hours. Expired records are excluded from reads immediately and deleted by local maintenance, normally within another 15 minutes while the server runs. No Spark email or push notification is sent. A mutual Spark is interest, not consent to an activity or permission to send chat messages.

Introduction starters

Contact settings store whether you accept Kinky connection and Easy hello preset introductions. Both are enabled initially. Members who can view your profile see which preset buttons are available. You can turn off either or both while still accepting personally written introductions. Preset selection is checked when sending; edits that change the preset text are treated as a custom message. These settings do not classify or prohibit subjects in personally written messages.

Limits and social links

Optional hard and soft limits use the same per-item visibility choices as interests. Visible limits appear on full profiles, not compact cards, and do not count as positive interests in discovery or matching. Shared-limit highlighting compares visible choices at the same level and role scope; it does not indicate consent or overall compatibility.

You can add X, Instagram and Bluesky usernames or profile links and choose whether each is shown. Hidden links remain private. Torc stores the normalized username and generates a link to the selected service. Opening a link takes you to that service, whose privacy practices apply. Torc does not load social embeds or previews. Deleting your account removes these choices.

Optional profile basics

You can add self-reported adult age, height, weight, position, body type, relationship status/style, gender, pronouns, orientation and languages. Every field is optional, with its own Show control. Hidden values remain stored for you but are omitted from other members' profiles and search filters. Saving public basics requires your explicit sharing choice. Height and weight are stored in centimetres and kilograms and can be displayed in imperial units. Age is self-reported, may become outdated, and is not verified age assurance. This profile field does not collect your birth date. Gender and language selections include custom entry. Each orientation combines selected labels and optional Other wording under one Show choice. If old components had mixed visibility, the combined editor starts private until you explicitly choose to show both.

Optional browser location

The city picker's Detect city button requests one reading and automatically fills a likely nearby town/city. That lookup runs on your device; only the chosen place is submitted when you save or search. It can be wrong near a boundary or with a broad location estimate, and you can correct it. Your browser/OS may use its own location service. Country data downloads can disclose a broad region to the host. Manual city search works without device permission.

Location starts off and needs an explicit choice in Profile → Visibility, plus browser permission. While Torc is visible, the device rounds coordinates to three decimal places before transmission. The account service stores the latest encrypted rounded position, reported accuracy, expiry and search cells. Three decimal places means approximately 111 metres of latitude spacing; longitude spacing varies. Other members see approximate distances between rounded positions, never below 100 metres. This does not guarantee anonymity or prevent inference of neighbourhoods and routines. A discoverable profile with city sharing enabled is required. Old consent must be renewed for this behavior.

Each reading stops participating after at most one hour unless replaced by a fresh reading while Torc is open, or when its session expires. Switching location off, ending its session, hiding your city, hiding your profile, or deleting your account removes it from active use. Expired rows are deleted by maintenance, normally within another 15 minutes while this local server runs. A closed or background tab stops refreshing; its last reading may remain active until expiry. The one-hour limit is not a backup-erasure guarantee. Encrypted data can still be decrypted by an operator who controls the service and its keys; independent production access controls are not established. Distance bands and rate limits reduce exposure but cannot prevent all inference, spoofed locations or copying.

Opening a member's full profile records your latest visit for that member's Visitors list when your profile is visible and Hide my visits is off (the default). Repeat visits within five minutes are grouped. Visits expire after 30 days. Blocking removes visits in both directions; hiding your profile removes your outgoing visits. Turning on Hide my visits removes your existing outgoing visits from both Visitors and discovery ranking, and prevents new records while enabled. Turning it off resumes future visits only.

Explore compares saved profile towns/cities and city centres. Near my current device location uses temporary device readings. Neither mode changes your saved profile city. Worldwide place data is not global service availability. GeoNames attribution.

Discovery and maps

Featured uses a fixed 60-mile area and distinct profile visitors over the last 90 days. A separate latest-visit record supports that ranking; the named Visitors list still expires after 30 days. Ranking records expire after 90 days and are removed when either person hides their profile, blocks the other person, or deletes their account. New members can receive reserved positions. Only an approved, explicitly selected public profile photo qualifies for photo priority; private albums do not. Photo uploads and delivery are not yet available in this preview.

Matches compares visible interests, connection intentions and relationship approaches. It is a discovery suggestion, not a promise of compatibility or consent. Hidden interests and limits do not earn a match score. Shared kinks requires at least one visible positive kink tag in common, regardless of roles. Everyday-only overlap does not qualify. Location and refined filters still apply; Any/All controls only the interests selected in Refine.

Opening the map loads tiles from OpenStreetMap. Its service receives your IP address, Torc's origin and the viewed map area. Member locations and profile identifiers are not sent to the tile service. Map pins are used for the current search and are not saved in your profile or saved searches. City lookup remains on Torc. Map and city searches compare shared profile towns/cities, not other members' precise device positions. OpenStreetMap attribution.

Signing in

Email codes expire in ten minutes and are stored as keyed hashes. Session tokens are held in an HttpOnly browser cookie; only hashes are stored in the database. This preview uses a separate local cookie and a synthetic mailbox in memory. A live deployment must use HTTPS and Secure cookies.

Passkeys store public keys. Their secret key stays with your authenticator. Your password manager may display jointorc.com, and a live email would reveal its sender domain. Neutral message text cannot hide your use of the service from someone with access to your mailbox or password manager.

Security and retention

Expired codes and sessions cannot be used. Scheduled maintenance removes expired records in batches; an outage or backlog can delay physical removal. Overdue cleanup is monitored in staging. Sign-in and security-event dates are retained for 30 days in this development policy. The application does not store raw IP addresses or user-agent strings. Short-lived keyed rate-limit values are retained to prevent abuse. Hosting and email providers may process network metadata under their own policies in a future deployment.

Synthetic profile reports copy the visible profile when available. You can choose to include your introduction and up to ten recent messages from your shared conversation; chat evidence is off by default. Temporary distance bands are excluded from copied report profiles. Reports survive blocking and account deletion, and normally expire after 90 days. Evidence stays while a related removal notice is pending or an image restriction is active, with a retention-review alert after the normal expiry. Cleanup runs while the local development server is running or through protected staging maintenance. This is a test retention rule, not an approved production policy. There is no staffed moderation in this preview.

Removal notices, image fingerprints and related case and decision records can remain beyond that period while a restriction or removal request is active, including after account deletion. Restricted photos may remain in private storage for assigned review until they are deleted. Image fingerprints identify matching canonical images, not every altered or cropped copy. These test controls still require an approved production retention policy and human review.

Optional identity, boundaries and connections

Relationship status, approach, sexual and romantic orientation, roles, availability and context are independent optional choices. Hidden fields do not appear in member views or discovery filters. Discuss first and Hard limit interests are never positive interest matches. Your selections do not authorize anyone to act for you or imply consent to an activity. Saved searches are private filter combinations; they do not save device coordinates or lists of matching people.

Connection requests require recipient opt-in. Only the two participants can see a pending request. Both must approve the labels, direction and audience before a link is active. Members is preselected, but both participants must explicitly approve the audience. Only us is also available. Members visibility requires that the viewer can see both profiles. Either participant may withdraw or make a link private. Editing labels or broadening the audience requires a new approval. Blocking a participant or hiding either profile revokes the association; restoring visibility does not restore it. A connection to someone not on Torc is self-described. You may optionally enter their name or nickname. It is private unless you choose Show on my profile, and it does not link to a Torc account.

Pending connections expire after 14 days. Declined, withdrawn and expired records are removed 30 days after entering that state by local maintenance. These are prototype retention choices, not approved production rules. Expiry prevents approval even before cleanup runs. No relationship email or push notification is sent. Turning off connection requests withdraws incoming pending requests. Turning off new introductions leaves existing conversations available.

Circle and friends

Saved people are private to you. Friend requests are visible only to the two participants and require acceptance; friendship does not publish a profile link. Pending requests expire after 14 days. Declined or cancelled requests and removed friendships have a seven-day cooldown before another request. Up to 20 requests may be sent per day. Blocking cancels the friendship and prevents new requests in either direction. Hiding a profile withdraws pending requests and temporarily hides accepted friendships. Closed records are removed after 30 days. Friendship records are included in account account data and deleted with the account.

Unread activity

Private read positions keep Inbox reminders consistent across sessions. Messages are marked read when displayed in an open chat; loaded incoming requests and Sparks are marked seen when their list is viewed. Read positions are deleted with your account or the underlying conversation, request or Spark. They are not read receipts shown to other members. Friend requests also appear in Inbox Requests.

This browser tab remembers your current section, subtab, layout and open profile or conversation across refreshes. Navigation is stored separately for each account in session storage and cleared on sign-out. It does not store unsent messages, profile edits, search filters or device coordinates.

Access and deletion

You can revoke sessions and request account deletion after a recent sign-in. Account downloads are currently disabled. Deletion immediately revokes access; a durable job retries removal across stores. Profile, connection, chat, photo and writing records are removed from the live social database. Private object-storage files use a durable deletion queue; a database cascade alone does not erase those files. Reports follow the separate test retention rule above.

A minimal random-ID erasure ledger supports deletion replay after a restore. Aggregate admission counts survive account deletion. Local test data stays on the developer's computer; protected staging stores its test data with Cloudflare and records database access in a separate synthetic audit archive. Backups and audit records have separate retention. A local restore rehearsal has passed, but production recovery, retention and provider contracts still require review.

Photos and writings

One profile album can hold several photos. Additional albums can be public to members who can view your profile or private. Private album owners can grant access to selected members or share individual photos in conversations. Bilateral blocks prevent profile and photo access. Revocation stops future access through Torc, but cannot remove copies someone has already saved or photographed.

Uploads are decoded and re-encoded on the server before storage. The resulting image excludes the original EXIF, GPS and other embedded metadata. This does not remove identifying details visible in the picture. Staging photos remain pending review until approved; local synthetic test photos can be automatically approved.

Writings default to private. Authors can change visibility and share a writing in a conversation. Text pasted into a message is a separate copy: making the original private or editing it does not recall that message. Public writings, reactions and reports are test data too.

Getting help

Help and safety contacts are available without signing in. Torc email currently forwards to the founder's Outlook mailbox. Share only the minimum information needed; do not email intimate images, identity documents or sign-in credentials.

Who can access data

Development uses synthetic data only. Production access, age assurance and user notices remain subject to review before real member data is collected.

Return to your account