Ur Next Door Ur Next Door
↑↓ navigate ↵ open esc close Try #tag or @user

Appearance

Home Marketplace Tools Jobs
Legal

Privacy Policy

Last updated: October 6, 2026

This Privacy Policy explains how Ur Next Door (“Ur Next Door,” “we,” “us,” or “our”) collects, uses, shares, and protects your information when you use the Ur Next Door community, knowledge, marketplace, hiring, and messaging platform (the “Service”). We have tried to describe what actually happens, including the parts that are easy to miss, rather than to state the minimum.

On this page

  1. 1. Information we collect
  2. 2. How we use your information
  3. 3. Your content is public
  4. 4. Chat & messaging
  5. 5. Jobs, applications & your CV
  6. 6. Marketplace, bookings & payments
  7. 7. AI writing assistant
  8. 8. Tools & calculators
  9. 9. Cookies & sessions
  10. 10. Advertising & analytics
  11. 11. Service providers we send data to
  12. 12. How we share information
  13. 13. Operational & administrative access
  14. 14. Data retention
  15. 15. Your rights & choices
  16. 16. Security
  17. 17. Children’s privacy
  18. 18. International users
  19. 19. Changes to this policy
  20. 20. Contact us & grievance redressal

1. Information we collect

Information you provide

  • Account information. Your username, email address, and password. Passwords are stored only as a one-way hash - we never store or have access to your plain-text password. If you sign in with Google, we receive your name, email address, and profile picture from Google instead of a password.
  • Profile information. Optional details you add: display name, bio, tagline, avatar, profile banner, website and social links, and a self-declared location (country, state, city). That location is coarse and typed by you - the Service does not use GPS or browser geolocation anywhere, and we do not derive your location from your IP address.
  • Content you create. Posts, questions, answers, polls, multiple-choice questions (MCQs), comments and replies, and the communities and tags you create.
  • Engagement. Reactions (likes and dislikes), poll and MCQ votes, follows, connections, saved favorites, and the reports and blocks you submit - including the free-text reason you give in a report.
  • CV and career details. If you build a CV, everything in it: headline and summary, work history, education, skills, projects, certifications, languages, and a contact email and phone number that are separate from your account email. See Section 5.
  • Job activity. Job posts you publish, and applications you submit - your cover note, the CV snapshot reference, and the status history of the application.
  • Marketplace activity. The services you list (titles, descriptions, pricing packages, images, FAQs, and the area you serve), the bookings you place or receive (your brief or requirements, preferred dates, quantities, contact details you choose to share, and the agreed amount), and the ratings and reviews you write or reply to.
  • Chat. The messages, attachments, and reactions you send, and the conversations and groups you are part of. See Section 4, which explains exactly which parts are encrypted and which are not.
  • Payment records. If you purchase a paid plan, a record of the transaction - the plan, amount, currency, billing cycle, the payment gateway’s order and payment references, a receipt id, and the access period. Your full card, UPI, or bank details are entered with and handled by the payment gateway; we never receive or store them.
  • Uploaded media. Images and other files you upload. These are stored as ordinary static web files and may be re-encoded (for example, to WebP) to speed up delivery. We do not strip metadata such as EXIF from your files. Where a re-encode happens it usually drops EXIF as a side effect, but that is a consequence of the conversion, not a privacy measure you should rely on. Remove location and camera metadata yourself before uploading if it matters to you.
  • Preferences. Your notification settings, privacy settings, theme, and who may invite you to a community.
  • Communications. The contents of any message you send us, including by email.

Information collected automatically

Our application does not keep its own access log. We do not store your IP address, your browser user-agent, or a per-request history in our database. What we do record automatically is limited to: the timestamps on the things you create and change; view counts on content, which are aggregate numbers and not tied to you; and short-lived rate-limiting counters, which identify a requester by a one-way hash rather than by a readable address.

Third parties do see your IP address. Serving a web page unavoidably reveals it to whoever sends the bytes. That means our hosting provider, and the analytics, advertising, font, and content-delivery providers listed in Section 11, each receive your IP address, your approximate location derived from it, your browser and device details, and which page you are on. Their own policies govern what they then do with it.

2. How we use your information

We use your information to:

  • Provide, operate, maintain, and improve the Service;
  • Create and secure your account and authenticate you when you sign in;
  • Display the content you publish and attribute it to your profile;
  • Power core features such as feeds, search, communities, tags, voting, reputation, and mentions;
  • Deliver chat and notifications, and send service email such as a welcome message or an update on a job application;
  • Operate the Marketplace and the jobs surface - publish your listings, job posts and CV, pass an application to the recruiter, and coordinate a booking through to completion;
  • Process payments for paid plans through our payment gateway and maintain your billing records;
  • Run the AI writing assistant when you ask it to (see Section 7);
  • Measure how the Service is used, in aggregate, so we can improve it;
  • Respond to your enquiries, support requests, and reports;
  • Monitor for, prevent, detect, and address fraud, abuse, spam, security incidents, and violations of our Terms of Use;
  • Comply with applicable law and enforce our agreements.

We process your information on the legal bases of performing our contract with you, our legitimate interests in operating a safe and useful platform, your consent (where required), and compliance with legal obligations.

3. Your content is public

Ur Next Door is a public platform. Your posts, questions, answers, polls, MCQs, comments, tags, service listings, job posts, reviews, and your public profile (display name, username, bio, tagline, avatar, banner, self-declared location, links, and reputation) are visible to anyone on the internet, whether or not they have an account. Your CV is public by default at your profile address until you turn that off.

Because this content is public:

  • It may be indexed by search engines and appear in search results.
  • It may be accessed and ingested by AI and generative-search crawlers (such as those operated by OpenAI, Google, Anthropic, Perplexity, and others), which we permit deliberately so that community knowledge is eligible for citation in AI answers. We list our public URLs in our sitemap and describe crawler access in robots.txt.
  • It is published as structured data - for example your service listings with prices and ratings, and your job posts - so third-party engines can read it directly.
  • Others may view, copy, quote, share, or cache it, including in places we do not control.

Things that are public but easy to miss

  • A poll’s creator can see who voted for which option. Poll and MCQ votes are attributed, not anonymous.
  • Viewing someone’s profile can notify them that you did. Profile views are recorded and shown to the profile owner.
  • Images you upload are served from public web addresses and may appear in our image search. The address includes your username.
  • Mentioning a member or a community notifies them and links your content to them.
  • Placing a booking or applying for a job automatically follows the other party and their community, which is visible on your profile until you unfollow.
  • Archiving is not deletion. Archived content is hidden from the Service but we still hold it.

Do not post information you wish to keep private or confidential. Removing content from the Service does not remove it from third-party caches, search-engine indexes, or systems that already accessed it.

4. Chat & messaging

Chat is private in the sense that it is not published, not indexed, and not shown to other members. It is not anonymous to us, and the following limits are important enough that we would rather you knew them than assumed otherwise.

Chat is not end-to-end encrypted. Message text is encrypted where we store it, with a key that we hold. That protects the contents against someone who obtains the database alone, but it does mean we are technically able to read messages - for example where the law requires it, or to investigate a serious abuse report.

  • Metadata is not encrypted. Who is in a conversation, when each message was sent, whether it was read, group names and photos, reactions, and the fact that a message was deleted are all stored in readable form.
  • Attachments are not protected by a login. Images and files you send in chat are stored as ordinary static web files, exactly like any other upload. Anyone who has the address can open one without signing in, and the address includes the uploader’s username. Treat anything you send in chat as something that could be seen by someone outside the conversation.
  • Search over message bodies works on a one-way index, so we can match a word you search for without the index itself revealing the message. Conversation and member search does not depend on it.
  • Other participants control copies. Anyone in a conversation can forward your message or media into another chat, and you are not notified.
  • History visibility depends on your plan. A free account sees the last 30 days. Nothing is deleted at 30 days - older messages are hidden from you and return if you upgrade.
  • Deleting your account does not erase your messages from other people’s conversations. They remain, no longer attributed to you.

5. Jobs, applications & your CV

You can build a CV on the Service. It holds a contact email and phone number separate from your account email, so check what you have put there. A CV is public by default - it is reachable at your profile address and can be indexed by search engines - and you can make it private in your settings.

Applying for a job shares your CV with that recruiter even if it is set to private. Three consequences follow:

  • Access extends to everyone who can manage that job post. For a job posted by a community, that means its editors and admins, not only the person who wrote it.
  • Access does not end when the role is filled or you are rejected. Withdrawing your application is what ends it.
  • Recruiters see your CV as it is now, not as it was when you applied. Editing it changes what every past recruiter sees.

Your cover note and application status history are shared with the recruiter, and a note the recruiter attaches to a status change is shown to you. Public job posts may also be published to third-party job search surfaces as structured data. We are not the employer, and we do not control how a recruiter handles what you send them - if that concerns you, ask them directly before applying.

6. Marketplace, bookings & payments

Marketplace and bookings

When you list a service, its details are public. When you place or receive a booking, the details of that booking - your brief or requirements, preferred dates, the chosen package and agreed amount, its status, and the messages and notes exchanged - are shared with the other party to that booking so the order can be fulfilled. Where the provider is a community, that means the members who manage it, not one individual. Ratings and reviews you leave after a completed booking, and any reply, are public and attributed to your profile.

Payments between members are arranged directly

In the current version of the Service, payment for a booking is arranged directly between the buyer and the provider, off the platform. We do not process, collect, hold, or escrow those funds, and we charge no platform fee on a booking. Any payment, contact, or other details you share with the other party are shared at your own discretion and are outside our control. Only the provider can mark a booking paid, so that record reflects what the provider states, not a payment we verified.

Paid plans

If you purchase a paid plan, your payment is processed by a third-party payment gateway (Razorpay or PayU - see Section 11). We receive and store a record of the transaction, but your full card, UPI, or bank details are collected and handled by the gateway under its own privacy policy, not by us. A redirect gateway takes you to its own hosted page to pay.

7. AI writing assistant

The editor offers an optional AI assistant. It runs only when you press one of its buttons.

When you use it, the text you are drafting leaves the platform. Up to 8,000 characters of your draft, plus your instruction and the model you chose, are sent to our AI provider (OpenRouter) and on to the model vendor behind the model you picked. Those vendors have their own privacy policies, and depending on the provider and tier we are using your input may be retained or used to improve their models. Do not put confidential information, or personal information about other people, into the assistant.

We do not store your prompts, and we keep only a per-member counter to enforce rate limits. The assistant is off entirely unless we have a provider key configured.

8. Tools & calculators

Our free tools and calculators run entirely in your browser. What you type into a calculator - salary figures, loan amounts, tax inputs - is never sent to us and is never stored by us. Some tool pages load charting or utility libraries from a third-party content delivery network, which will see your IP address and which page you are on, as any asset request does.

9. Cookies & sessions

We use a strictly necessary session cookie to keep you signed in. It is set with the HttpOnly flag (so client-side scripts cannot read it) and the SameSite=Lax attribute (to mitigate cross-site request forgery). It is scoped to our whole domain, so one sign-in covers the main site and every community subdomain, and it is honoured for up to 30 days. We also use a small cookie to remember your light or dark theme choice, and your browser’s own local storage for interface preferences that never reach us.

Signing out ends your session. The stored session record itself is cleared by a periodic sweep rather than at the instant it expires, so treat 30 days as the point at which a session stops working, not the point at which the record is guaranteed to be gone.

Third parties, including our advertising and analytics providers, set their own cookies. See Section 10. You can control cookies through your browser settings, though blocking the essential ones will prevent you signing in.

10. Advertising & analytics

Advertising

We display advertising through Google AdSense, including on pages that show member content, community pages, and profiles. Google and its partners may use cookies and similar technologies to serve and measure ads, including ads based on your prior visits to this and other websites.

  • You can opt out of personalized advertising at Google Ads Settings.
  • For how Google uses data from sites that use its services, see the Google Privacy & Terms page.
  • You can opt out of third-party vendor cookies for personalized advertising at aboutads.info/choices.

Analytics

We use Google Analytics 4 to understand how the Service is used. Events are sent both from your browser and from our servers, which means an ad blocker will not suppress all of them.

Two specific things go to Google Analytics that are worth naming. When you are signed in, we attach your numeric account id to events, so that a journey across devices counts once. We never send your email address, username, or any other directly identifying field. And when you use search, the words you typed are sent as the search term, which is how we learn what people are looking for and cannot find.

We also use Amplitude, in your browser and in our app, to understand how people move through the Service. On the website it records the pages you view (their address, without anything after a question mark), the buttons and links you click, including the words on them, form starts and submits, a copy of the browsing events we send to Google Analytics, and your device and browser details. In the app it records the screens you open (with member names and handles taken out of the screen address), the same browsing events we send to Google Analytics, when the app is opened or put away, and your device details. Our servers also send it the actions you take, such as signing up, posting, answering, joining a community or booking a service. It never receives your location.

When you are signed in, Amplitude receives your numeric account id and your public username, so that your visits and actions on different devices count as one person and we can understand how members use the Service. It never receives your email address, phone number or password. Visitors who are not signed in are recorded under a random device id only.

Amplitude also makes session replays, on the website and in the Android and iOS apps: a reconstruction of how a page or screen was used (layout, scrolling, clicks and taps) so we can see where people get stuck. Every piece of text is hidden in a replay, and so is everything you type. Your messages, CV, account and password screens, billing, settings, job applications and bookings are never recorded at all.

You can block the browser-side events with a browser extension or a Do Not Track setting, which stops Amplitude in your browser and its session replays. The actions you take while signed in are still counted from our servers, under your account id (and, for Amplitude, the device id your browser already has, if any).

11. Service providers we send data to

We use a small number of third parties to run the Service. Each receives only what it needs. This is the full list; if we add one, we will update this table.

Provider What it receives Why
Our hosting provider Everything stored in the Service, and your IP address as part of each request Running the site and its database
UND Services (hosted on Render) Your notifications and their contents, which are stored there rather than by us; outbound email, including the recipient address and the full message; and a copy of rendered public pages Notifications, email delivery, and page caching
Brevo Your email address and the contents of the emails we send you Actually delivering email
Slack Operational alerts about your account. On signup this includes your email address, username, display name, account id, plan, self-declared location, tagline, and avatar; afterwards, a running record of your activity on the Service, which can include a changed email address and the free-text reason you give in a report So our small team sees and can act on what happens on the platform. See Section 13
OpenRouter Up to 8,000 characters of the text you are drafting, and your instruction, passed on to the vendor of the model you chose - only when you use the AI assistant Generating the suggestion you asked for. See Section 7
Google Analytics Pages viewed, actions taken, your search terms, your IP address and device details, and your numeric account id when signed in Usage measurement. See Section 10
Amplitude On the website: pages viewed, what you click (including the words on it), form starts and submits, and a copy of the Google Analytics browsing events. In the app: screens opened (member names and handles removed) and browsing events. From our servers: the actions you take. When you are signed in: your numeric account id and public username. In all cases: your IP address and device details, and session replays with all text and typing hidden. Never your email address, phone number or location Understanding how the Service is used and where it is hard to use. See Section 10
WhatsApp (Meta) Only if you choose to message us there: your message. When you are signed in, the chat button pre-fills it with your name, username, account id, email address and plan, and the page you were on; you see and can change all of it before you send Answering your questions
Google AdSense Advertising cookies and identifiers, your IP address, and the page you are on Serving and measuring ads
Google Sign-In The fact that you signed in. In return we receive your name, email address, and profile picture Signing in without a password. Your Google profile picture stays hosted by Google, so your browser fetches it from Google each time it is shown - on your profile and anywhere your avatar appears
Razorpay and PayU Your payment details, entered with them directly, and the order amount. We receive back only a transaction reference Taking payment for a paid plan
jsDelivr, unpkg and Cloudflare (cdnjs) Your IP address, browser details, and the page you are on, when your browser fetches a script from them Delivering the charting and interface libraries some pages use

Several of these are optional integrations that are switched on by configuration. Where one is switched off, nothing is sent to it at all.

12. How we share information

We do not sell your personal information. We share it only as follows:

  • Publicly, for the content and profile details you choose to publish (see Section 3).
  • With other members, where a feature requires it: the other party to a booking, a recruiter you apply to and everyone who can manage that job post, the participants in a chat, and the moderators of a community you post in.
  • With the service providers in Section 11, which process data on our behalf.
  • For legal reasons, when we believe disclosure is reasonably necessary to comply with a law, regulation, legal process, or governmental request, or to protect the rights, property, or safety of Ur Next Door, our users, or the public.
  • In a business transfer, in connection with a merger, acquisition, financing, or sale of assets, in which case we will continue to protect your information consistent with this Policy.

13. Operational & administrative access

We are a small team and we look at the platform directly. Rather than hide that behind a phrase about “authorized personnel,” here is what it means.

Operational alerts

Activity on the Service is mirrored into our internal Slack workspace so we can see what is happening and respond. When you sign up, a message is posted containing your account details, including your email address. That message then anchors a permanent thread for your account, and subsequent actions you take - signing in, editing your profile or email, creating or deleting content, joining a community, making or receiving a booking, buying a plan, saving your CV, blocking or reporting someone, deleting your account - are appended to it. Some of those entries carry values, such as a new email address or the reason text you typed into a report. Chat message contents are never sent to Slack.

Administrative access

Our administrators can view and act on accounts through an internal panel. That includes viewing your content and your CV, editing profile fields including your username and email, resetting a password, changing a plan or a verification badge, changing account status, correcting a booking’s or an application’s recorded state, removing content, and deleting an account. We use this to operate the Service, handle reports, fix errors, and comply with law. We do not routinely notify you before or after an administrative action, and we do not currently maintain an audit trail of administrative access that we could show you.

14. Data retention

We retain your account information for as long as your account exists. Public content may remain on the Service after you post it, including where it has been quoted, referenced, or replied to by others.

To delete your account, email support@urnextdoor.com. There is no in-product delete button yet, and we do not currently offer a data export, so take a copy of anything you want to keep first. Deletion is immediate and irreversible when we action it, and there is no grace period.

Deleting your account removes your account, profile, and CV; your posts, questions, answers, polls, MCQs, comments, service listings, and job posts; your reactions, follows, favorites, connections, and blocks; your billing records; and any community you created, together with the content other members contributed to it. It also removes shared records that another member is part of: bookings on either side, the reviews attached to them, and job applications in either direction.

What survives is your messages inside other participants’ conversations (no longer attributed to you, so their threads stay readable); tags you created; content others quoted or re-shared; the operational Slack record described in Section 13; anything third parties have already collected under their own retention rules; and records we must keep to comply with law, resolve disputes, prevent abuse, or enforce our agreements.

15. Your rights & choices

Subject to applicable law - including, in India, the Digital Personal Data Protection Act, 2023 - you may have the right to:

  • Access the personal data we hold about you;
  • Correct inaccurate or incomplete data. You can edit most profile, content, and CV data directly in the Service;
  • Delete your data or your account, as described in Section 14;
  • Withdraw consent where processing is based on consent;
  • Nominate another person to exercise these rights on your behalf in the event of your death or incapacity;
  • Grievance redressal - raise a complaint about how we handle your data, with the officer named in Section 20.

To exercise any of these rights, email support@urnextdoor.com. We may need to verify your identity first, and we will respond within the timeframes required by applicable law. You can also control most notifications, and whether your CV is public, from your settings at any time.

16. Security

We use reasonable technical and organizational measures designed to protect your information: passwords are stored as one-way hashes, chat message bodies are encrypted where they are stored, every state-changing request is protected against cross-site request forgery, uploads are checked against a file-type allow-list, and access to personal data is restricted. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

Two honest limits, repeated here because they matter more than a general assurance. Uploaded files, including chat attachments, are served without authentication to anyone who has the address. And we do not keep access logs, so if something did go wrong we would have limited ability to reconstruct who saw what.

You are responsible for keeping your password confidential and for activity under your account. Tell us immediately at support@urnextdoor.com if you believe your account has been compromised.

17. Children’s privacy

The Service is not intended for anyone under 13, and we do not knowingly collect personal information from them. Under India’s Digital Personal Data Protection Act, 2023, anyone under 18 is a child, and processing their data requires verifiable consent from a parent or legal guardian.

We do not currently collect a date of birth and we do not verify age, so we rely on the representation each member makes when they register. We are working on this. If you are a parent or guardian and believe your child holds an account, write to support@urnextdoor.com and we will remove the account and its data.

18. International users

We operate the Service from India, and the providers in Section 11 operate in several countries. If you access the Service from outside India, your information may be transferred to, stored in, and processed in India or other countries whose data-protection laws may differ from those in your own. By using the Service, you consent to that transfer and processing.

19. Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes, we will revise the “Last updated” date above and, where appropriate, provide additional notice. Your continued use of the Service after the changes take effect constitutes your acceptance of the revised Policy.

20. Contact us & grievance redressal

If you have questions about this Privacy Policy or how we handle your information, reach out:

  • General enquiries: support@urnextdoor.com
  • Privacy & data requests: support@urnextdoor.com

Grievance redressal

In accordance with India’s Digital Personal Data Protection Act, 2023, you may raise a complaint about how we process your personal data by writing to support@urnextdoor.com. We will acknowledge it and respond within the period the law requires.

You can also visit our Contact page or read our Terms of Use.

Ur Next Door Ur Next Door

UrNextDoor - Where you Blog, Connect, Learn, Hire & Grow together.

Appearance

Explore

  • Posts
  • Questions
  • Polls
  • MCQs

Community

  • Communities
  • Tags
  • Members
  • Following

Company

  • About us
  • Compare
  • Pricing
  • Contact
  • Privacy Policy
  • Terms of Use

Compare Ur Next Door

  • vs LinkedIn
  • vs Reddit
  • vs Facebook Groups
  • vs Discord
  • vs Quora
  • vs Stack Overflow
  • vs Circle
  • vs Mighty Networks
  • vs Skool
  • vs Nextdoor
  • vs Fiverr
  • vs Upwork
  • All comparisons
© 2026 Ur Next Door. All rights reserved.
Privacy Terms Contact
Ur Next Door

Welcome back

Sign in to vote, comment, and ask your neighbors.

or
Forgot password?
3–30 characters: lowercase letters, numbers, underscores.
8–16 characters.
  • Free forever
  • 1 minute to join
  • No spam ever
Don't have an account? Create one. Already have an account? Sign in.

You're offline

Check your connection. This page will reload on its own the moment you're back online.

Trying to reconnect...
Choose an image
Loading your uploads…
Nothing here yet Upload an image and it'll show up here to re-use anywhere.
Crop image Drag to reposition · zoom to crop, or fit the whole image
0°
Background