Privacy Policy
Junxion is a tenant-side platform, and that shapes how we handle your information. This policy explains what we collect, what we do with it, who can see it, and the choices you have. It applies to the Junxion website and mobile apps.
The short version
- Your case materials are private by default. No other user can read them unless you share them. Junxion staff see a case redacted by default, and reading its content requires a recorded decision.
- Administrators cannot browse private conversations. The only route into one is the thread behind a message someone reported, while that report is open.
- We do not use your content to train machine-learning models. Not your reviews, not your posts, not your cases, not your messages.
- We run no advertising and no third-party analytics, and we do not sell your information.
- We give landlords no special access. There is no landlord account on Junxion.
- Location is used to verify residency, not to track you.
- Some things are public, including reviews, and your landlord can read them.
1. Who we are
Junxion is a housing technology and advocacy platform based in Washington, DC. In this policy, “Junxion”, “we”, and “us” mean the operator of Junxion. We operate junxion.us and the Junxion mobile apps.
Privacy questions and requests: support@junxion.us.
2. Scope
This policy covers information we collect through Junxion. It does not cover other people’s sites that we link to, or information about buildings and owners that we obtain from public government records, which describes properties rather than you and is public before it reaches us.
If the Terms of Service, the Community Guidelines, and this policy conflict, the Terms govern, then the Guidelines, then this policy, except that this policy governs on what we do with personal information.
3. Information you give us
Account. Your first and last name, email address, and a password, which we store only as a cryptographic hash. A profile photo is optional. We do not collect a phone number, date of birth, government ID, income, or Social Security number, and we process no payments, so we hold no card or bank details. Sign-in is email and password only, so no outside authentication provider receives information about you from us.
Optional questions about you. You may tell us your age range. These are optional, kept separately from your account record, and skipping them costs you nothing. We ask in order to understand who Junxion is and is not reaching. You can change or clear your answers at any time in Account, under About you. Your age range is the only one of these questions we ask today.
Content you create. Posts, comments, and reactions. Chat and direct messages, with any images attached. Reviews and ratings of buildings. Events, polls, and votes. Marketplace listings. Tenant association materials. Reports you file and blocks you place.
Case materials. A case can contain a title, summary, dispute type, and tags; the property address and ward; the landlord or managing entity you name; notes; files you upload, such as photographs, letters, and inspection reports; records of correspondence; and a history of how the case progressed.
Residency. The building associated with your account, buildings where your residency has been verified, and the records of those attempts.
4. Information we collect automatically
Device and technical information, meaning browser and device type, operating system, and app version.
Diagnostic and error logs. When something goes wrong we record the error, the page involved, your browser’s user-agent, a session identifier, and, if you were signed in, your account reference. These exist to find and fix defects, and we delete them automatically on a short schedule.
Product usage events, a small set of milestones such as that a signup occurred, and the referrer that led to it. They carry no message content and we delete them automatically.
IP addresses. We record your IP address when you redeem a community invite link, as an anti-abuse measure. Our hosting provider and reverse proxy also process IP addresses in ordinary server logs as part of delivering the service.
Push notification tokens. If you turn on notifications in a mobile app we store the device token, the platform, and when the device was last seen, in order to deliver notifications you asked for. The token is used only for that and is deleted when you sign out on that device. You control push separately from the in-app bell, with a switch for each category, and your device settings can turn all of it off.
Analytics, when it is switched on (it is not running yet). We would use one analytics tool, hosted on our own servers. It is cookieless and sets no identifier on your device. When you are signed in its events would carry your Junxion account identifier, a random string and never your name or email, so repeat visits could be told apart. That makes the data pseudonymous rather than anonymous, and it stays with us. We strip name, email, phone, and address from the analytics events we send ourselves. Page content, message text, and case materials are never sent to an analytics provider. We use no third-party analytics, so no analytics event goes to Google, Meta, or any advertising network. (Maps are different: when a page shows one, your browser loads it from Google or MapTiler directly; see our service providers page.)
5. Location
To confirm that you live in a building, which is what separates a resident from an outsider in your building’s private spaces, we ask your device for its location at the moment you verify and compare it to the building’s location. We record the outcome, the method, a confidence strength, and supporting evidence about the check.
We do not track your location continuously, in the background, or between verifications. We build no location history, do not use location for advertising, and do not sell it.
Because residency verification controls access to private spaces, our server evaluates the check independently and caps the accuracy value your device reports, so a falsified reading cannot defeat it.
Your browser or device asks for location permission and you can decline or revoke it. If you decline you can still use much of Junxion, including filing a case, but you will not be able to verify residency by location. A moderator’s invite can still admit you to your building.
6. Information from other sources
A substantial part of Junxion is built from District of Columbia open government data: property tax and assessment records, ownership, licenses, violations, permits, rent control registrations, registered tenant associations, and related records. This describes properties and the entities that own or manage them, and it is public before it reaches us. Where such a record names an individual, that name comes from the public record and we reproduce it as published.
When you enter an address we use mapping and geocoding services to resolve it. Other people may also include information about you in content they create.
7. Sensitive information
Housing disputes carry unusually sensitive information. Case materials can reveal health conditions, disability, income or public benefits, family status, immigration status, household composition, or the substance of a legal dispute.
Please share only what you need to document your issue. A photograph of a leak does not require a photograph of your family.
Access is enforced in the database query rather than hidden in the interface, so a record you cannot see is never sent to your browser in the first place.
8. What other people can see
Junxion mixes public, semi-private, and private spaces, and the differences matter, because content you make public can be read by your landlord.
Public
Your display name and photo where they appear beside public content. Reviews and ratings, with photos and the rent and unit type you report. Posts you mark public, and comments on them. Tenant organization pages. (Marketplace listings are visible to your building only, link previews included.)
Public content may be indexed by search engines, copied, quoted, archived, or reshared, and may be ingested by systems that crawl the web. Once that happens we cannot claw it back: deleting it from Junxion does not delete someone else’s copy.
Your building
Posts limited to your building, the open chat room, events, polls, and the building marketplace are visible to anyone whose account is currently a member of that building. A separate verified chat room and your building’s tenant association hub are limited to residents holding a verification of sufficient strength, plus the building’s moderators and administrators.
Who can be in these spaces is a rule, not a wall. Our Terms forbid anyone who does not live in a building from entering its spaces, and forbid landlords, property managers, and anyone acting for them from entering tenant organizing spaces under false pretenses. We cannot technically guarantee it: membership comes from a geofenced location check or a moderator’s invite (a moderator scan can later raise a member’s verification), none of which proves tenancy, and someone standing at the building can pass the location check.
Case materials are private by default
Your cases, notes, files, and correspondence are visible to no other resident or moderator unless you take a step to share them. This is enforced in the system, not by convention. Tenant organizations are switched off at present, so no outside advocate can see anything at all.
Building-wide case digests are anonymized and are not optional. Once a day, for each building where a case was filed, Junxion posts an anonymized summary into that building’s chat room. It reports dispute types and counts, never who filed what, and it is suppressed entirely in very small buildings, where even an anonymous count could identify a person.
What “anonymous” does and does not mean
Anonymous means other users do not see your name. It does not mean we cannot tell it was you: the content is still associated with your account in our systems so we can enforce our rules and respond to reports.
Anonymity on a review requires a tie to the building: your account belongs to it now, or belonged to it before. Otherwise the option is not offered, and a request to post anonymously is refused rather than published under your name.
Anonymity also has limits we cannot engineer away. In a small building, a review describing a specific unit, date, and condition may identify its author whatever name is attached.
What landlords can see
Junxion offers landlords, property managers, and their agents no special access. There is no landlord dashboard, no verified-owner program, and no arrangement under which a housing provider receives your data from us. There is no landlord account at all.
A landlord can read anything the public can read. If you are worried about retaliation, keep sensitive material in your case, where it is private, rather than posting it publicly.
Moderators and administrators
Building moderators are residents who volunteer. For their own building only, they can see content that has been reported, messages held for review, who is a member of the building, residency verification records, the moderation log, and the building’s invites and external chat links. They cannot see case files, cannot read your direct messages, and cannot see anything in another building.
A campaign is the one exception you choose: if you join one in your building and agree to share case details, your building’s moderators and Junxion administrators see the details you picked (any of your case summary, issue type, status, address and date opened), and a moderator can download them as a spreadsheet. You can withdraw, but a copy downloaded before you do stays with whoever downloaded it.
Administrators and conversations. An administrator can read the thread behind a message someone has reported, and only while that report is open. Access closes when the report is resolved or dismissed. Every access and every refusal is logged with the report that authorized it, and those records are kept. There is no way for an administrator to browse or search conversations generally.
Administrators and cases. An administrator sees a case redacted by default: that it exists, its status, which building, when it was opened, and how many notes and files it holds, and none of the title, your description, the dispute type, the landlord, or your unit. Reading the content requires either a help request you filed yourself or a decision recorded by a named administrator who must give a reason, or a campaign you joined and chose to share case details with (above). Every time an administrator opens a case, redacted or not, that is logged and kept. You can see and close a help request you filed.
The honest limit. These are controls in the application, not in the database. Anyone holding database credentials can read anything directly, and no setting in the product changes that. What the controls buy is that reading a tenant’s file is a deliberate, recorded act rather than a side effect of opening a page.
9. How we use information
To create and secure your account; operate Junxion; verify residency and administer access to private spaces; show content to the audience you chose; deliver notifications as your notification settings allow, including categories that are on by default until you turn them off; respond to reports and enforce our rules; provide support; detect and prevent fraud, abuse, and security incidents; diagnose defects; understand aggregate housing conditions in order to support tenant advocacy, using aggregated or de-identified information; and comply with law.
We do not run advertising or use your information to target ads; run any third-party analytics; use your content to train machine-learning models, meaning not your reviews, posts, case materials, messages, or photographs; sell your personal information; or share your information with landlords, property managers, brokers, or screening companies.
Where we publish aggregate figures about housing conditions we suppress small groups, report at ward or city level, and publish the response rate beside the number, because a breakdown drawn from a fraction of a building describes the people who answered rather than the building.
10. How we share information
We share information with companies that operate Junxion under contract. The current list is published on our service providers page, deliberately on its own page so it can be corrected when the list changes without reissuing this policy. That page commits to listing a company before it starts receiving anything. Those companies may use the information only to provide services to us.
Disclosure to a tenant organization happens only with your affirmative consent, by sharing a case, only to the extent of that consent, and it is revocable. This is switched off at present. Joining a campaign shares only what you chose, with your building’s moderators and administrators (see Moderators and administrators, above).
Legal process, safety, and law enforcement
We may disclose information where we believe in good faith it is necessary to comply with law or valid legal process, to enforce our Terms, to establish or defend legal claims, or to protect the rights, property, or safety of Junxion, our users, or the public.
This deserves candor. Material you store on Junxion to document a dispute may be sought by an opposing party in litigation, by subpoena, or by a government agency, and we cannot promise we will never be compelled to produce it. What we commit to: we will make reasonable efforts to notify you before producing anything, so you can object, unless we are legally prohibited or there is an emergency involving a risk of death or serious physical injury; we will require valid legal process, construe demands narrowly, and push back on ones that are overbroad; and we will produce the narrowest set of information responsive to a valid demand.
Legal demands should go to support@junxion.us.
If Junxion is involved in a merger, acquisition, financing, reorganization, dissolution, or sale of assets, information may be transferred as part of that transaction.
11. Automated content screening
Automated screening is switched off. No image and no text is sent to any screening company. Nothing is rejected and nothing is held by software. If we turn it on we will list the company on our service providers page first.
We do maintain records related to enforcement: reports filed, moderation actions taken, mutes, and blocks. No automatic penalty applies to your account. Nothing suspends, mutes, or removes you without a person deciding.
12. How long we keep information
We keep your account and content while your account is active, until you delete it. Diagnostic logs and product usage events are deleted automatically after a short period. Database backups are taken regularly and rotated out. Enforcement records are kept while they are needed for security and enforcement.
Account deletion and the undo window. When you delete your account it is immediately hidden: your name stops appearing and your content is attributed to a deleted account. The record is kept for 7 days so you can undo it if you change your mind, and you can still sign in during that time to do so. After that an automated job is meant to delete the account record permanently. Today that does not work for many accounts, including any that ever verified residency: where other records still point at yours (a reaction, a follow, a block, a residency check), the account record stays in our database, hidden and attributed to a deleted account, until we fix it. Your name, initials, and photo stop appearing either way.
What survives deletion, which is the part worth reading: your cases survive, with their notes, files, and correspondence, no longer connected to a live account. A case you shared with a tenant organization stays shared, so revoke it first if you want it ended. Messages you sent remain in the recipients’ conversations. Reviews and public posts remain, attributed to a deleted account. Content others have copied or reshared is beyond our reach. Copies already written to backups remain until they rotate out, and we keep records we must for legal, security, or enforcement purposes.
13. Security
We protect Junxion with encryption in transit for all traffic; passwords stored only as cryptographic hashes; a sign-in cookie that browser scripts cannot read authorizing requests to our servers (a copy of the sign-in token is also kept in your browser’s storage, where scripts on the page can read it, for reads made directly from the browser); cross-site request forgery protection on every state-changing request; rate limiting on sensitive operations; access control enforced in the database query, so records you may not see are never sent to your browser; automated checks in our build pipeline that fail the build when code omits a required access filter, so a privacy control cannot be dropped silently; and regular automated database backups.
Encryption at rest, stated precisely. Your information is encrypted at rest by the platforms that store it, and those providers hold the keys, not us. We do not add a layer of our own on top. Our database backups are stored with a separate provider from the one that runs the application, and the same is true there.
It is worth being plain about what that does and does not do. Encryption at rest protects your information if storage hardware is lost or stolen. On its own it does not protect against someone obtaining our credentials, or against a legal demand served on us or on one of our providers. We manage those risks separately: a short list of people with administrative access, two-factor authentication on each of those accounts, holding as little information about you as we can, and deleting what we no longer need.
Junxion accounts do not currently offer multi-factor authentication. No system is completely secure and we cannot guarantee absolute security. If we learn of a breach affecting your personal information we will notify you and the relevant authorities as required by law.
14. Your choices and rights
In Junxion you can view and update your name, email, photo, and password; adjust notification preferences per category and per channel, meaning in-app, email, and push; edit or delete content you posted; revoke a case you shared and withdraw from a campaign; block another user; delete your account with 7 days to undo; and control location and notification permissions in your device settings. There is no SMS channel and we collect no phone number.
Depending on where you live, you may also have the right to know what information we hold, obtain a copy, correct it, delete it, and appeal a denial. You have the right not to be discriminated against for exercising these rights. To make a request, email support@junxion.us. We will verify your identity, usually by confirming control of the account email.
Downloading your information. Requesting an export in Account, Security & Privacy assembles a bundle and makes it available as an authenticated download inside the product. It is never an emailed link: a bundle is your entire case history, including photographs of your home and correspondence with a landlord, in one file, and a link in an inbox can be intercepted, forwarded, or read off a shared screen. Your signed-in session is the gate instead. The bundle selects cases using the same access rule the product uses to decide what you may read, and chat and direct message contents are excluded, because a conversation belongs to everyone in it. The copy is available for a limited time after it is prepared.
There is nothing to opt out of on analytics. We run no third-party analytics and no advertising, and we do not sell your information. Our own analytics is not running yet; when it is, it will be first-party, set no cookies, and honor Do Not Track.
15. Cookies and similar technologies
We use no advertising cookies, no retargeting pixels, and no third-party analytics cookies. The strictly necessary cookies, which you cannot turn off and stay signed in, are your sign-in session and a security token that protects against cross-site request forgery. One more cookie, jx_ft, records how you first arrived (for example a building’s invite link) so a signup can be attributed to it: a random value, the source and the time, kept for up to 30 days and cleared when you sign up.
There are no analytics cookies. Our self-hosted analytics, when it runs, sets none and stores no identifier on your device, so there is nothing to decline and no cookie banner to show you.
Your device also holds some things locally: your theme preference (also saved to your account when you are signed in, so it follows you between devices), your last map view, a cached copy of your sign-in state, and an autosaved draft of a case you are filling in, which is cleared when you submit it or sign out.
16. Children
Junxion is for adults. You must be 18 or older to create an account. We do not knowingly collect information from anyone under 18 and will delete it if we learn we have. We do not verify age, so this is your representation rather than our finding. If you believe a minor has given us information, email support@junxion.us.
17. Mobile applications
Our apps may ask permission to use your camera and photo library, to send notifications, and to access location in order to verify residency. You can grant or revoke each permission in your device settings, and some features will not work without them. Apple and Google operate the app stores and their own privacy practices apply to your download and to push delivery.
18. Changes to this policy
We may update this policy. When we do, we will post the updated version with a new “Last updated” date.
If a change affects what information we collect, who we share it with, how long we keep it, or your rights, we will ask you to accept the new version before you continue using Junxion, and we will record that you accepted it and when. For other changes, corrections and clarifications that do not affect the above, we will post the updated version and let you know, and continuing to use Junxion will mean you accept it.
If you would rather not accept an update, you can stop using Junxion. You will still be able to sign in to export your information and delete your account.
19. Contact us
- Privacy questions, requests and rights, legal notices and legal process, and support: support@junxion.us