What we collect, what we don't, and how to make us delete it.

SidewalkSnitch is a service provided by SidewalkSnitch Inc., a Delaware corporation, c/o its registered agent in Delaware, Legalinc Corporate Services Inc., 131 Continental Dr, Suite 305, Newark, DE 19713 US. SidewalkSnitch Inc. is the data controller for the personal information described in this policy. You can reach us at hello@sidewalksnitch.com.

• We collect what you give us (photos, address, phone, optional email) and what we need to run a complaint flow (your GPS at the moment of submission, your photo's EXIF GPS). We also record and retain your IP address for security, abuse prevention, and traffic analytics.
• We do not sell your information. We do not run ads.
• Photos shown anywhere in the app have all GPS and camera metadata stripped. We separately retain a high-quality copy of your original file, metadata included but with faces and license plates blurred, in a private, staff-only AI training set.
• If your report captured a license plate, we clear that plate from your report after 30 days.
• We remove your original, unblurred photo file 90 days after you upload it, once a blurred copy of it exists. A report you send privately to a business gets no blurred copy, so its original is kept and you keep the photo on your own record.
• We read your photo's GPS to place your report and keep those coordinates with it — including to improve our AI. Deleting your account removes them.
• Reports about a business appear on the public SidewalkSnitch feed, and you can share your own report to social media after you submit it. If you instead send a report privately to a business, it stays off the feed, and that business sees your screenname and nothing else that identifies you — not your name, phone, email, or address.
• You can delete your account and your data at any time via the More tab. We honor deletion requests within 30 days.
• SidewalkSnitch is intended for adults. We do not knowingly collect information from anyone under 13.

From you, directly: photos you upload, the text you write, the mobile phone number you verify, your real name and email and mailing address (collected once when you first verify a phone), a screenname you pick.

Photos you add to someone else's report: other users can add photos to a public report. Those photos are blurred the same way and are labeled as added by another user. Photos you contribute to someone else's report are public.

If you join our launch waitlist: the mobile number you enter, an optional first name, an optional 5-digit ZIP code, and an optional neighborhood — used to text you when we launch, tell you whether your neighborhood is covered, and order the waitlist. Reply STOP to any text to opt out. Waitlist entries are kept until launch; once we go live and invites have been sent, the waitlist is deleted. We may show aggregate, non-identifying neighborhood signup counts publicly.

From your device: your photo's EXIF GPS and timestamp (read to pre-fill where the issue is; we keep these coordinates with your report and remove them from the stored image file itself), your current GPS at the moment of submission (used only to check you are near the issue), your browser's IP address. We record and retain your IP address — not only for abuse rate-limiting, but also in our own visit log, which we use for security investigations, abuse prevention, and understanding how people find and use the site. It is stored in full, not hashed or truncated, and is readable only by SidewalkSnitch operators. It is never sold, and never shared with a business you report.

Pages you open on this site (our visit log). Every page of this site — the app, the marketing pages, and the guides — carries a small first-party measurement script we wrote ourselves. It is not a third-party analytics product, it sets no cookies, and it assigns you no tracking ID. It runs whether or not you are signed in and whether or not you have an account. For each page you open it records: the page path, the date and time, your IP address (described above), and — worked out on our own servers from your browser's referrer header and any ref or utm_source parameter in the link you followed — a traffic-source category (such as search engine, social network, AI assistant, or direct) and the referring site's hostname. We keep the hostname and the category; we do not store the full referring URL. It also records clicks on links that open in a new tab, and on a small number of specifically tagged buttons, storing the destination address or that button's label. Approximate location — country, region, city, and coordinates rounded to about a kilometre, plus a New York City borough label where one applies — is derived from your IP address by our hosting provider and stored with the entry. This log does not record your browser or device type, and carries no name, phone number, email address, screenname, or account ID. We use it to see how people find and use the site, and for security and abuse investigations. It is stored in our own database, readable only by SidewalkSnitch operators, and is never sold or shared. If your browser sends a Do Not Track signal, this visit log is switched off for you entirely — no pageview and no click is recorded.

The link you first arrived from, kept on your device. If you reach us through a link carrying a referral code (ref) or campaign parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term), we save that first set of values in your browser's local storage. A later visit never overwrites it. Nothing is transmitted at the moment we save it; it reaches us only attached to something you do — joining the launch waitlist, or the product-analytics events described below. Clearing site data for sidewalksnitch.com in your browser removes it.

About your submissions: the AI's analysis of your photo (which rule was violated, confidence score, drafted complaint text), the rule it cited, the agency it routed to, and the city's acknowledgment if the complaint was filed.

How you move through the app (product analytics). We log step-level events as you use the app — opening the report screen, capturing a photo, each stage of the AI analysis, starting or abandoning a draft, signing in, and similar. Each event carries the event name, a session ID that lasts until you close the tab, your Firebase user ID (you have one even before you verify a phone number, so this includes anonymous visitors), how long the step took, and, where you arrived from a link or campaign, the referring URL and its tracking parameters. This log does not contain your phone number, your name, your email, your address, your GPS coordinates, or your photos. Our separate site visit log, described above, is what records your IP address. We use this to see where people get stuck, to fix the flow, and to decide which neighborhoods and categories to work on next. It is readable only by SidewalkSnitch operators and is never sold or shared. A randomly-generated identifier is also stored in your browser's local storage so we can connect this activity across visits on the same device, even before you sign in. It is not linked to your name, email, or phone number by us, persists until you clear this site's data in your browser, and — like the rest of this log — is never created or read at all if your browser sends a Do Not Track signal.

Photos and complaint text are stored to your account so you can view them in My Reports. SidewalkSnitch does not send every complaint to 311 on its own. For parking, sanitation, dining, and vendor reports you can ask us to send yours to NYC 311, and parking reports go automatically: a person on our staff submits it on the city's own site, usually within a day, and the Service Request Number appears on your report once the city gives us one. Nothing goes to 311 unless you ask for it or it is a parking report. We do not send your real name, email, phone, or address to 311, DOT, or DSNY as part of that. You can also take the same details to 311.nyc.gov and file it yourself, under your own name, any time — that filing is handled entirely under the city's own privacy policy, not ours. City agencies generally require a contactable submitter, so expect the city's own form to ask for your real name and contact details if you file it yourself.

Other users never see your name, phone, email, or address. Your My Reports view is private to your own account. Anywhere else a submission of yours is shown to other people, the most that is ever attached to it is your screenname.

The public activity feed. Once you submit a report, it appears in a public activity feed — on the app's home screen and on the community map — that anyone can read without signing in or having an account. A feed entry carries only: the location, coarsened before it leaves our servers (the street address is reduced to its hundred block, so “312 E 9th St” becomes “300 block of E 9th St”, and the map coordinates are rounded to roughly 110 meters); a category label such as “Parking” or “Trash / Sanitation”; the status of the report; roughly when it was filed (the date is coarsened, and every report is withheld from your neighbors' feed for a randomised 5 to 60 minutes after you submit it — you see your own report straight away); and aggregate like and comment counts. It does not carry your name, your screenname or any other identifier of you, the name of any business or person the report is about, the AI's written description of what it saw, or any license plate.

Photos on that feed. Reports that aren't sent privately to a business are public — including reports you file about a business, which appear on the feed and which you can share to social media yourself. Your photo — blurred — may appear on the public feed. Reports you send privately to a specific business are the exception and never appear there. A photo only reaches the feed after an automated service blurs faces and license plates in it (see “Third parties we share your information with”), and only the blurred copy is published — never your original upload. Be aware that once a blurred photo has been served publicly, we cannot guarantee that copies already downloaded, cached, or screenshotted by others stop being reachable, even after you delete the report.

Photos other people add to a report. Other users can add photos to a public report. Those photos are blurred the same way and are labeled as added by another user. Photos you contribute to someone else's report are public.

Comments and votes. If you comment on a post, your screenname — never your name, phone, email, or address — appears next to your comment, publicly, to anyone who opens that post. Your comment text is screened by automated tools (see “Third parties we share your information with”) before it's published; comments that fail screening or are flagged by other users are held for review and are not shown publicly until reviewed. Votes on posts and comments are recorded against your account but are never displayed publicly or attributed to you. If you flag someone else's comment, that action is recorded against your account for abuse-prevention purposes; it is not shown publicly.

License plates. For parking complaints, our AI may extract a plate visible in your photo. We then check that plate against NYC's public Open Parking and Camera Violations dataset and show you the vehicle's prior-violation summary ephemerally on the result screen. We do not store the prior-violation history on your complaint record. The plate itself is stored as a structured field on your complaint because the eventual 311 filing requires it, and it is automatically cleared from your complaint record 30 days after you file the report.

Crime reports may be shown on a public city map. Faces and license plates in those photos are blurred server-side before publication. Your name and contact information are never displayed alongside crime reports.

AI processing. Photos and the text you write are sent to xAI's Grok vision model for analysis. We do not send your name, phone, email, or address to the AI — it doesn't need them.

Sending a report to a business. For some kinds of reports — not parking, and not lost & found — if you picked a specific business from the address search, you can choose to send the report to that business instead of, or as well as, filing it with the city. This is your choice; nothing is sent to a business unless you tap that button.

If the business has already claimed its listing with us, sending the report opens a private two-way message thread between you and that business. In that thread the business sees: your screenname only — never your real name, phone number, email address, mailing address, or account ID — plus the category of the report, the address you gave for the issue, the AI's written description of the photo, and anything you write in the thread. We also email the business to tell them a message is waiting; that email contains only the category of the report and the business's own publicly listed address, and describes the report as unverified and submitted by a resident. It contains no information about you and none of your text. Your photo of the issue is never sent to the business. If you attach a photo to a message inside the thread, a human reviewer at SidewalkSnitch checks it before the business can see it. The business can reply, and we email you to say they replied — that email names the business but does not quote what they wrote. The business can close a thread, after which neither side can add to it and it becomes read-only. No one other than you, that business, its invited managers, and SidewalkSnitch operators can read the thread.

If the business has not claimed its listing, no message thread is created and we do not email that business. We record internally that a report of that category was made about that address, together with your account ID, so the business can see it if it later claims the listing.

How we decide which businesses to approach. Every time a report is sent to a business we email ourselves a note containing the business's name, address, category of report, and its Google listing ID — and nothing about you. We also keep an internal list of businesses that reports have been filed about, ranked by how many reports there are, how recent they are, and how many different categories they span, so we can decide which business owners to contact and invite to claim their listing. That list is built from the reports themselves. It is never sold, shared, or licensed, and no business is ever told who reported it.

Business manager invites. A verified business owner can invite managers to help answer messages by entering their mobile number. We don't store that number in the clear — only a one-way keyed hash we use to match and confirm the invite, plus the last two digits so the owner can recognize who they invited. A manager record is created only after the invited person accepts.

Suggest a Rule. If you use Suggest a Rule, the text you write (and any photo you attach, with location and other identifying metadata removed the same way it is for other uploads) is sent to xAI's Grok model to check whether a similar rule already exists and, if not, to draft proposed language — see “Third parties we share your information with” below. We also use your address (already collected for filing) to determine your City Council district using a public district-boundary dataset, entirely on our own servers; we do not send your address to any third party for this purpose. If your suggestion passes review, your screenname — never your name, phone, email, or address — appears publicly next to it, and other users can upvote or downvote it, the same as comments. We do not send your suggestion to any government official ourselves — we show you a pre-filled draft and public contact information for your Council member, and you decide whether and how to send it.

Open a report and you'll see a chart of 311 complaints recorded at that address, grouped by week and by category. That history is not ours. It comes from the City of New York's own 311 Service Requests dataset, which the City publishes on NYC Open Data for anyone to read, download, or chart. Your browser asks the City's data service for those records directly and draws the chart on your device. We do not add to the City's records, we do not keep our own copy of them, and we do not score or rate an address, a building, or a business — the chart shows counts and nothing else. Because that request goes straight from your browser to the City's data service, that service sees your IP address, the same as any website you open.

If a 311 record about your address is wrong, we can't change it. It belongs to the City. Corrections go to 311 or to the agency that created the record — and if the record changes there, the chart changes with it the next time it loads.

What we keep is a different list: the reports you write in the app — including drafts you started and never took to 311 — attached to your account, and our site visit log (described above), which records pages opened together with the visitor's IP address. We retain what you provide until you ask us to delete it (see “Retention and deletion”). Visit-log entries are deleted after 180 days by a daily automated sweep — that includes the IP address, the page path, the click records, and the approximate location on the entry.

Who can look at what. Anyone can read the public parts of this site with no account and no sign-in: the activity feed, the community map, a report's detail screen, and the address-history chart — the same access anyone already has to the City's 311 data. Everything else requires a verified mobile number: filing a report, commenting, messaging a business. Nothing in the app lets anyone search by a person's name, phone number, email address, or account; there is no people search here. SidewalkSnitch operators can see full records, including account details, in internal admin tools. Other users and businesses cannot.

Every photo path runs through a fail-closed strip-and-transcode step before upload (see src/lib/image/ensure-jpeg.ts). A JPEG is parsed byte-by-byte and its APP1 (EXIF/XMP), APP2 (ICC profile, camera maker notes), APP13 (Photoshop/IPTC), APP14 (Adobe), and APP11 (JPEG-XR/EXIF extension) segments are removed. A non-JPEG (PNG or HEIC, which can also carry GPS) is re-encoded to a fresh JPEG via the browser canvas, which drops all embedded metadata; if it cannot be processed, the upload is refused rather than stored. Either way, the stored JPEG has no camera model, no camera serial, and no embedded GPS.

We read your photo's EXIF GPS coordinates before stripping them from the file, and use them to pre-fill the location of your report. Two different things then happen to that location data, and they follow different rules — the coordinates are a small piece of text; your original photo file is a separate, much more sensitive object, and each is described below.

The coordinates. We keep the GPS coordinates (latitude/ longitude, plus a reverse-geocoded address) as a field on your complaint record, and — because location is a strong learning signal — we keep a copy tied to your account in our AI training data. The stored image file itself still contains no embedded GPS; only this separate text field does. There is no fixed expiry date for the coordinates: we hold them for as long as your account is active, and deleting your account removes them immediately from both your reports and the training data.

Your original photo file. Separately, we keep a high-quality copy of your original file — including its embedded GPS coordinates and camera/device identifiers — in a private AI training set accessible only to our staff. Any faces and any license plates in that copy are automatically blurred; nothing else about the image is changed or reduced in quality. It is never published, never shown to other users, and never sent to a third party. We keep that copy for up to 24 months, automatically deleted after that by a daily sweep — or sooner, immediately, if you delete your account first.

Who can access the training set. Our Storage security rules deny read access to this corpus for every signed-in user, with no exception — not even our own in-app admin accounts can open or download one of these files through the app or its admin console, because there is no read path there at all. The only way to reach an original file is direct administrative access to the underlying Google Cloud project (service-account credentials), which is restricted to SidewalkSnitch's own engineering staff. No object in this corpus has a public or shareable URL.

Photos and complaint records: retained as long as your account is active. When you delete your account, the records are soft-deleted and purged within 30 days.

Your original, unblurred photo file: removed from our storage90 days after you upload it, by a daily automated sweep. This applies to photos uploaded on or after 2026-08-21; photos uploaded before that date are not covered by this window. We remove an original only when a blurred copy of it already exists, so your own record of the report keeps an image. A report you send privately to a business never gets a blurred copy, so its original is kept and stays visible to you. Removal stops our servers from serving that file; a copy that someone already downloaded, or that a cache still holds, is outside our control.

Three different clocks, so they are not confused. The license plate text on your report is cleared after 30 days. Your original photo file is removed after 90 days. The blurred copy in our private AI training set is kept for up to 24 months. These are three separate items with three separate rules.

Business message threads: when you delete your account, every thread you started is deleted outright — the messages on both sides, and any photos in them. We keep only a record that a thread with that ID existed and was purged, containing nothing about you or its contents. The internal note recording that a report of a given category was made about an unclaimed business is retained.

Abandoned analyses (you uploaded a photo but didn't submit): purged within 30 days.

Visit log: 180 days, deleted by a daily automated sweep. See “Pages you open on this site” above for what an entry contains.

License plate on your report: the plate string stored on your complaint record is cleared automatically 30 days after you file it. This is separate from the plate-lookup audit log below, which we keep much longer for a different reason.

Plate-lookup records: we keep an audit log of every plate lookup (which user, what plate and state, when, and the stated purpose) for 7 years, to support our own use justification under federal law. The audit log entries do not include the violation history itself — only the plate string.

Billing records: if you delete your account while a subscription is live, we cancel that subscription with Stripe immediately — you are not charged again — and we delete our own copy of your billing status. Stripe keeps its own record of the payments it processed, which it is required to do for tax and anti-fraud purposes; that is outside our control and is governed by Stripe's own policy.

How long we keep the activity log. We have not set a deletion date for the product-analytics log described above, and we are not going to claim one we do not enforce. Today those records are kept while the product is being built, so we can compare how the flow performs over time. They contain no name, phone, email, address, GPS coordinate or photo. When you delete your account we remove the records tied to your account. If we set a fixed deletion window for this log, we will state it here and enforce it with an automated sweep, the way we already do for the visit log (180 days) and the error log (90 days).

Comments, votes and photos you added to other people's reports: if you delete your account, comments you posted that were published stay visible, so the public discussion other people took part in is not torn up around them — but your screenname is replaced with “[deleted]” and the comment is no longer linked to your account in any way. Comments that were held for review or removed are deleted outright. Every vote you cast, and every flag you raised, is deleted, and your votes are backed out of the totals shown on posts and comments. Photos you contributed to someone else's report are deleted, including the blurred copies published on the feed. Be aware that once anything has been shown publicly, we cannot guarantee that copies already downloaded, cached or screenshotted by other people stop being reachable.

Suggestions: if you delete your account, your published rule suggestions remain visible to preserve the public civic discussion, but your screenname is replaced with “[deleted]” and no longer linked to your account. Suggestions that were held for review, blocked, or removed at the time of your deletion request are permanently deleted, not retained.

To delete your account: open the app → More → Delete account. Or email hello@sidewalksnitch.com from the email address on file.

If you are a California resident, the California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA) give you the right to know what we collect, request deletion, and not be discriminated against for exercising those rights. We honor these requests for all users, not just California ones.

If you are a New York resident, the New York SHIELD Act applies; we maintain reasonable administrative, technical, and physical safeguards for the information we collect. Any breach affecting NY residents will be reported to the NY Attorney General within the statutory window.

We do not sell your information. We do not have any business arrangement under which any personal information is exchanged for money or anything of value.

Visitors outside the United States. SidewalkSnitch is a New York City service, and our servers and providers are in the United States. If you visit or use it from outside the US, including from the European Union or the United Kingdom, your information is processed in the US under this policy. You have the same rights we describe here — to know what we hold about you, to correct it, to have it deleted, and to object to a use — and you can exercise them by writing to hello@sidewalksnitch.com. We answer within 30 days. The app is not directed at people outside the US.

These providers process data only to run the service for us. All of the categories below exclude text messaging originator opt-in data and consent; that information will not be shared with any third parties. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes.

• Google / Firebase — authentication (including, if you use it, Google sign-in for business-ownership verification), Firestore database, and Storage hosting (us-central region).
• xAI — AI photo analysis via the Grok API; automated screening of the text of comments and rule suggestions you post before they're published (checking for PII about other people, harassment, and unsupported accusations); and, for Suggest a Rule, checking whether a proposed rule already exists and drafting proposed rule language. We do not send your name, phone, email, or address to xAI for any of these purposes.
• Vercel — application hosting and serverless functions.
• Google Places / Maps Platform — resolves an address you type (for filing a complaint, or for Suggest a Rule) to geographic coordinates and a formatted address, including to determine your City Council district for Suggest a Rule. Part of the Google/Firebase relationship above.
• Vercel Web Analytics — measures site traffic and how people find us using cookieless, aggregate analytics. It sets no cookies, does not build advertising profiles, and does not track you across other sites. Visitors are counted using a temporary hash derived from the incoming request that is discarded within 24 hours; we get only aggregate counts (pageviews, referrers, approximate location, browser/device type), never data tied to you as an individual. There are no third-party ad trackers on this site.
• Twilio — When a business owner asks us to verify their ownership of a business listing by phone, we use Twilio to place an automated verification call to the phone number that Google publicly lists for that business, and to speak a one-time code. Twilio processes that business phone number and call metadata (such as call time and status) to place the call on our behalf. This is separate from the SMS sign-in codes we also send through Twilio via Firebase. We do not send your name, email, or address to Twilio for this purpose.
• Google sign-in (business-ownership verification) — When a business owner chooses to verify ownership with Google, we ask you to sign in with Google and we receive the email address and basic profile of the Google account you select. We compare that email's domain to your business's Google-listed website to check your connection to the business. If they match, we store that Google email as your verified owner-notification address; if they do not match, we do not keep the email, and your claim is reviewed by hand. You control which Google account you use, and you can decline and verify another way.
• Resend — transactional email: the phone-auth email magic-link sign-in, and the notification emails described under “Sending a report to a business” (sent from the verified sidewalksnitch.com domain).
• Sightengine — server-side face and license-plate blurring. It receives the photo of any report you chose to make public, before that blurred copy is shown on the public feed, and would do the same for crime reports (that feature is currently switched off).
• Stripe — payment processing for the optional Snitch+ and business subscriptions. If you subscribe, Stripe receives and stores your card details (we never see or store your full card number — only the last four digits and the card brand), your billing email address, and the state of your subscription. Stripe uses this to take the payment and to detect fraud, and processes it under its own privacy policy as well as our agreement with it. If you never subscribe, we send Stripe nothing.
• Upstash — rate-limit counters (keyed by phone number or IP).
• Sentry — error monitoring: crash reports and error diagnostics (stack trace, browser/OS, route). Configured to send no default personal identifiers; photo data and request bodies are scrubbed before sending, and session replay is off.
• Twilio — text messages: the one-time sign-in codes (sent via Firebase Phone Auth), and the two opt-in texts described under “SMS / text messaging” below (the waitlist-spot text, and the business-owner alert when a neighbor reports or messages a claimed business). If you opt in to any text messages, we keep a record of that opt-in, and that record includes your phone number, so that we can show you agreed and can honour it if you later reply STOP. Twilio receives your number only to deliver those messages; it is never shared with any third party or affiliate for marketing or promotional purposes.

• Socrata / Tyler Technologies — the host of NYC Open Data. We read public city datasets from them: posted parking signs, the Open Parking and Camera Violations dataset used for the plate check, 311 service-request records, and the map layers. We do not send them your name, phone, email, address, photos, or any account information. They are a source of public data we look things up in, not a company we hand your data to.
• NYC 311 and city agencies — we read published city records (service requests, permits, violations) to show you what is already on file near you. SidewalkSnitch only sends a report to 311 if you ask us to (parking reports go automatically) — nothing is transmitted to any city agency without that. When we do send one, a person on our staff submits it, using the details from your report and not your real name, phone, email, or address. If you choose to file with the city yourself instead, you do that on the city's own site, under the city's own privacy policy.

SidewalkSnitch is intended for adults. We do not knowingly collect personal information from anyone under 13. When you verify your phone number, you confirm you are at least 13 years old. If you believe a child has provided information to us, email hello@sidewalksnitch.com and we will delete it.

We use SMS one-time-passcodes (via Firebase Phone Auth, sent through Twilio) to verify your phone number before you can file a complaint. By tapping “Send code” you consent to receive that SMS. Standard message and data rates may apply. Reply STOP to any verification message at any time to opt out. We don't send marketing SMS.

Optional text alerts. Two other kinds of text exist, and both are opt-in only: a single text when your waitlist spot opens (you tick “Text me when my spot opens” on the join form), and, for a business owner who claims a listing, a text when a neighbor reports the business or sends it a message (you tick “Text me when a neighbor reports my business or sends a message” on the claim form). Both boxes start unchecked, and you can join the waitlist or claim your business without ticking them. Message frequency varies with activity. Message and data rates may apply. Reply STOP to cancel at any time and HELP for help. We keep a record of each opt-in and opt-out (your number, the exact wording you saw, and the time) so we can honour it.

No sharing for marketing. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties. Your mobile phone number and your text-messaging opt-in consent are not shared with, sold to, or rented to any third party or affiliate for marketing or promotional purposes. We share your number only with the providers who deliver the messages on our behalf (Twilio, and Firebase for sign-in codes), and only to deliver them.

The complaint text you see on the result screen is drafted by an AI model from your photo. Before you submit, you must read the text, edit anything inaccurate, and explicitly attest that what it describes is what you personally observed. The submitted text is your statement on the record, not the AI's.

SidewalkSnitch Inc., c/o Legalinc Corporate Services Inc.
131 Continental Dr, Suite 305
Newark, DE 19713 US
Questions, complaints, or deletion requests: hello@sidewalksnitch.com.