TORC

EFFECTIVE NOVEMBER 17, 2026 · VERSION us-2026-11-17.3

Privacy and your choices

Northmere Software LLC provides Torc. This notice explains what the service collects, why, who can see it and the choices you have.

What you choose to share

We need an email address, account identifiers and authentication records to provide an account. Email addresses are encrypted in the account database. Sign-in uses email codes or saved recovery codes. An adult-age affirmation is not verified age assurance.

Profile text, interests, limits, roles, orientation, measurements, social links and relationship labels are optional. These can reveal intimate or sensitive information. Show controls determine which supported fields other members can see. Hiding a field does not delete its stored value. Public profile information means information available to eligible signed-in members, not permission to copy or redistribute it.

We use visible choices for discovery and matching. Matching is a suggestion, never consent or a guarantee of compatibility. Saved people and pending requests are private to the relevant participants. Relationship links require both participants' agreement. Blocks restrict access through Torc; they cannot recall screenshots or other copies.

Your agreement and consent

After verifying your account, you separately accept the Terms and Community Rules, acknowledge the Privacy and Retention notices, and consent to sensitive-data processing needed for the core member service, and separately consent to the collection and sharing of consumer health data described in the Consumer Health Data Privacy Policy. These choices start unchecked. We record each choice's timestamp and policy version without an IP address or device fingerprint. The receipt remains with your account and is removed during account deletion, subject to separately justified legal preservation obligations.

Membership itself may reveal sensitive interests. You do not have to fill in optional profile details, and Show controls are separate from processing consent. Remove optional details to stop their future use; hiding alone does not delete them. To withdraw consent for the core service, use Withdraw consent and delete account. You can still sign out, request privacy assistance or delete an account without accepting a new policy version. Device location requires its own choice.

Location

Manual city selection works without device permission. If you enable device location in Torc and allow your browser to share it, Torc uses your device to round latitude and longitude to three decimal places before sending them, together with reported accuracy, to Torc. This spacing is approximately 111 metres in latitude; longitude spacing varies with latitude. Device collection starts off until you opt in. The account service encrypts the latest rounded position; a fresh reading replaces it. Torc does not deliberately build a movement history. Rounding is not anonymity: locations can still be sensitive and patterns may reveal a neighbourhood or routine. Device location is not available inside certain areas the US government lists as sensitive (28 CFR 202.1401). There, your device does not send a reading and Torc does not store one; your chosen city still works.

A reading is excluded from distance calculations after at most one hour without refresh. Switching sharing off, ending the associated session, hiding the required profile/city information or deleting the account stops its use. Other members receive distance bands between rounded positions, with distances displayed approximately and never below 100 metres, not exact coordinates. Approximation and request limits cannot eliminate location inference or spoofing.

Expired readings are removed by scheduled cleanup. Custom daily recovery exports exclude location readings and their consent-control records. Provider-managed database recovery can retain earlier encrypted readings for up to one day. One-hour active expiry does not mean erasure from every recovery copy. See retention.

Opening a map loads OpenStreetMap tiles. That service receives network information and the map area requested. Torc does not send member identifiers or member-coordinate records to the tile service. Your browser or operating system may also use its own location provider.

Photos and review

Torc accepts photos at two levels, Open and Mature, described in the Community Rules; explicit photos are not accepted. Mature photos are shown blurred until a member chooses to see them. Torc converts accepted uploads to JPEG images and thumbnails, removing embedded metadata such as EXIF location. A scene, face or visible address can still identify someone or reveal a location. Only upload photos you have the right and permission to share.

Images are held privately while awaiting screening and human review. Torc sends the converted image to Sightengine for automated checks for nudity, graphic injury and hateful imagery, without adding your email, profile name or account identifier. The image itself may identify you. A clear automated result does not publish an image: the assigned Torc operator must approve it. Uncertain or failed checks keep it unavailable to other members. These checks can make mistakes and do not verify age, identity, consent or copyright.

Sightengine is operated by Kozelo SAS in France. Its standard service may process images in the United States, Canada or the European Union; selecting a US-only member market does not mean all processing stays in the United States. Torc uses its automated checking API, not its feedback or hosted human-review features.

After approval, profile and public-album photos are available to eligible members under your profile controls. Private-album grants and photos shared in conversations permit the corresponding recipients to view them. Private means restricted audience within Torc, not exclusion from necessary automated or human safety review. You can remove photos and revoke supported grants; recipients may still have independent screenshots or copies. Report a mistaken decision or request removal through Help and safety.

Conversations and activity

Messages are not end-to-end encrypted. Participants can read them, and authorized safety handling may require relevant evidence. Private writings start private; pasting a writing into a message creates a separate copy that is not recalled when the original changes.

Profile visits are visible to the visited member unless you enable Hide my visits. That switch also removes previous outgoing visit records used by Torc. We store latest activity for online/last-active information and private read positions for your inbox indicators. These read positions are not receipts shown to other members.

How information is handled

We use account information to authenticate, provide requested features, operate and protect Torc, investigate reports, answer rights requests and meet applicable obligations. We do not currently use advertising trackers, sell member information or use member contents to train an AI model. A new use requires review and an updated notice and, where required, consent.

Cloudflare provides application hosting, email delivery and object storage. Neon provides the PostgreSQL database, hosted in the United States. AWS stores encrypted recovery copies, which can contain account and message data and photo files; a separate audit archive on AWS stores access-event metadata rather than message text or query results. Sightengine screens photos as described above. Support emails currently forward to the project Microsoft Outlook mailbox. Share the minimum needed and never send intimate images, identity documents or sign-in credentials by email.

Assigned safety access is limited by case and purpose in the application. The founder retains broader cloud-administration powers. Encryption does not prevent an administrator with the keys from accessing information. Access to member data through the service is recorded in a separate audit archive whose records cannot be deleted for 30 days, including by the founder. Direct access to the database by the founder is restricted by a separate password but is not independently logged. US database placement does not mean US-only processing or access. The founder administers the service and may do so from outside the United States.

We may preserve or disclose relevant information when required by applicable law or a valid legal process, or as permitted to address serious safety concerns. Requests must be assessed for scope and authority; this is not permission for routine unrestricted inspection. Hosting and communications providers may process network metadata under their own terms.

Service development and government requests

AI-assisted development tools are used to build, deploy and scale Torc. They work with code, configuration and fictional test data. The credentials that can read or decrypt member information (the database owner login, database role passwords and encryption keys) are kept in a separate locked store that only the founder can open, and are not given to these tools. Member content is not placed in AI prompts. If the founder must inspect production data to fix a problem or meet a legal duty, the founder does so personally. This is a safeguard, not a guarantee: code written with AI assistance runs in the service after review and testing, and no-training statements do not mean that no AI processing occurs.

Providers or operators may be subject to lawful government requests in jurisdictions where they process or access information. We will assess security incidents and provide notices to affected people and authorities when required by applicable law.

You may raise a concern with privacy@jointorc.com or contact the Federal Trade Commission or your state attorney general. Contacting Torc first is not a condition of exercising a right to complain to an authority.

Your controls and requests

Edit or hide supported profile fields, disable location, hide visits, block members, withdraw connections, revoke sessions or delete your account in Torc. For access, correction, deletion or help using a privacy right, use Privacy requests or contact privacy@jointorc.com. We verify control through the registered contact method and explain the outcome and any permitted exception. A public username alone is not proof of ownership. Self-service data downloads are disabled; requests are handled through a verified request. Available responses use the signed-in portal and expire after seven days; a partial response is not a statement that every applicable access right has been fulfilled.

Deletion revokes access and queues removal across stores; outages can delay physical deletion. Relevant safety evidence and narrowly justified legal holds may remain separately. Restored backups must have later deletion and restriction instructions reapplied before members can access them. We will give material policy changes an updated date and appropriate notice; changes do not retroactively authorize unrelated uses.

All policies · Help and safety