Legal
Privacy Policy
Last updated September 22, 2026
Porchside is operated by Kinward, Inc. ("Porchside," "we," "us," or "our"). This Privacy Policy explains how we collect, use, disclose, and safeguard information when you use the Porchside mobile application, the porchside.co website, and related services (the "Service"). Because Porchside is a social product built around in-person activities, the section "How We Share Your Information With Hosts and Other Members" describes what other people can see about you, and it is the section to read first.
1. Who and What This Policy Covers
This Policy covers four groups of people. Members. People with a Porchside account, on the app or the web. Website visitors. People who visit porchside.co without signing in, including people who open a link someone shared with them and people who browse our public directory of communities and events. Prospective hosts. People who submit the host interest form on our website. We collect that information before any account exists. People who do not have an account. If a member invites you to a community by email, we hold your email address in order to send that invitation. If a member saves you as a safety contact, we hold the name and phone number they gave us. Where a section applies to only some of these groups, it says so.
2. Information We Collect
Information You Provide: Account information: your first and last name, email address, password where you set one, and phone number. A verified phone number is required on the mobile app. Profile information: your photo, bio, neighborhood, zip code, date of birth, gender where you choose to give it, interests, vibe and companion-style preferences, availability preferences, age-bracket preferences, and, where you choose to set them, a username and a displayed last initial. Location information: the zip code you provide, which is required to finish onboarding, and the neighborhood and approximate coordinates we derive from it. See section 9. Content you create: activity listings and their cover photos; community and series names, descriptions, taglines, icons and covers; ideas; messages and the photos in them; memory cards, their photos and notes; polls, poll options and votes; reactions; group and thread names; the note you send with a request to join a community; ratings, reviews and review tags; tournament rosters, team names, match results and the scores recorded against them; feedback you send us; and reports you file. Transaction information: what you bought, ticket counts, amounts, fees, tax, refunds, and the payment references our processor returns to us. See section 8. Identity verification data: if you use the optional selfie verification feature, a selfie photo, processed and then deleted, a retained verification status, similarity score, and timestamp, and a record of your consent to the feature with the version of our documents you accepted and when. See section 19 and our Biometric Data Policy. Phone verification data: your phone number, a one-time code sent to it, the verification status, a cryptographic hash of the number used for contact matching, and the version of the text-message consent wording you agreed to and when. Contacts you choose to share: if you opt in to the find-friends feature, the app reads your device address book and converts phone numbers into cryptographic hashes on your device. Only the hashes are sent to us, never your contacts' names or raw numbers. See section 10. Safety contact: if you save a safety contact, the name and phone number you enter. You are responsible for having that person's permission. See section 11. Email addresses of other people: if you invite people to a community by email, the addresses you enter. See section 11. Calendar information: if you grant calendar access, the app reads your device calendar so you can turn events into plans and can add activities you are attending to your calendar. Calendar entries are read on your device for that purpose. Host interest form: if you submit it, your email address, the community you want to run, an optional description, category, cadence, and zip code. Information Collected Automatically: Device and usage information: device type and model, operating system, unique device and installation identifiers, app version and build number, the screens and features you use, the actions you take, timestamps, IP address, and browser type. Push notification tokens, and your notification preferences and timezone. Analytics events. On mobile we use Google's Firebase Analytics. On our website we use Google Analytics 4, which sets cookies and is not loaded at all for visitors whose browser signals Global Privacy Control. Share tokens are removed from page addresses before they are sent, and our analytics events are designed not to carry names, email addresses, phone numbers, or message content. Error and performance data collected by our error-reporting service in the mobile app, which can include device information, stack traces, performance traces, a redacted route, and your account identifier. Location signals described in section 9, including, on our website, the approximate area derived from your IP address. Attribution information: how you came to Porchside and how you came to be at a particular activity, for example through a referral link, a share link, a printed code, a community invitation, or the feed, and a first-touch campaign tag stored in a cookie on our website. Where a campaign brought you to us, we record which one against your account: on the web from that cookie, and on Android from the install referrer that Google Play passes to the app when it is installed. Scanning a printed code is described in section 12, and section 21 covers the cookie. Information From Third Parties: authentication data from sign-in providers, and payment and payout information from our payment processor. Information About Public Events: we also collect basic information about public events from publicly accessible sources and publish listings for them. Those records are about events and their organizers, not about our members.
3. How We Use Your Information
We use information to provide, operate, and improve the Service; create and manage your account; show you activities, communities, and people that may interest you; run activities, RSVPs, check-ins, and communities; process ticket payments, refunds, and host payouts; send notifications, reminders, and account messages; keep the Service safe, including detecting and acting on fraud, abuse, and violations of our Terms; compute the measures described in section 18; analyze usage to improve the Service; diagnose errors; communicate with you about updates and support; publish public web pages for public activities and communities; and comply with legal obligations. We also create aggregated or de-identified information that can no longer be linked to you, and we may use and share that for any lawful business purpose. We do not attempt to re-identify it, except to test that our de-identification works. We do not use your personal information to train general-purpose artificial-intelligence models.
4. Personalization, Ranking, and Recommendations
We rank what you see, and we suggest people. Your activity feed is ranked using your connections on the Service (for example, invitations you have received and activities your friends are attending or interested in), the filters you set, your location, and how much interest an activity has drawn from other members. The feed can show your friends that you are interested in an activity, which means your first name and photo can appear that way in their feeds. The distance filter uses your device's current location while you use the app; we do not store it in your profile. Some placements are chosen by people at Porchside rather than by an algorithm: we may feature an activity or mark a community as official, which affects where they appear. Where a feature pairs or suggests people, we use the preferences you set for it, your interests, your neighborhood, and your history on the Service, including activities you have attended and the people you have met. People search is ranked in the same way. You can influence what you see by changing your interests, preferences, neighborhood, filters, and who you are friends with, and by leaving a pairing pool.
5. Categories of Personal Information We Collect
For purposes of U.S. state privacy laws, the categories of personal information we collect include: identifiers (name, email address, phone number, username, device and installation identifiers, IP address); customer records and account information; age and date of birth; commercial and transaction information (tickets purchased, payments, refunds, payouts); internet and device activity (usage, analytics events, error reports); geolocation, including precise geolocation when you enable location access; biometric information, when you use selfie verification; audio, electronic, or visual information (photos you upload); professional information, where you volunteer it in a listing or profile; content and communications you create; and inferences drawn from this information, including the ranking, pairing, reliability, and engagement measures described in sections 4 and 18. We collect these from you, automatically through your use of the Service, from other members (for example when a member invites you or saves you as a safety contact), and from service providers including our payment processor and sign-in providers. We use them for the business purposes described in this Policy. We disclose them to the recipients described in sections 6, 7, and 8. We do not sell personal information, and we do not share it for cross-context behavioral advertising or targeted advertising.
6. How We Share Your Information With Hosts and Other Members
This section sets out in full what other people can see about you. We describe it in full because our Host Agreement allows hosts and organizers to use it only for the activity or community where they received it, and you should know what that covers. "Host" means the member who created an activity and any co-host they added. "Organizer" means the owner or an admin of a community. Your profile, to any signed-in member. Your first name, photo, bio, neighborhood, interests, selfie-verification badge, Local Host badge, activity badges, the month you joined, and, where you set them, your username and last initial. Your age is shown as a range. Other members also see how many mutual friends and shared communities you have with them, and the names of those mutual friends and communities, including private communities you are both in, and how many communities and activities you are in. To the host of an activity you RSVP to, and their co-hosts. That you are attending, your profile as above, how many guests you are bringing, whether you checked in and when, and whether your RSVP is pending, maybe, declined, waitlisted, or withdrawn. Hosts and co-hosts also receive notifications when you join, change your RSVP, withdraw, or buy tickets. Where a no-show is recorded for an activity, the host and co-hosts can see it. Co-hosts, who can be added only to free activities, see everything the host sees. To other people at an activity. Whether you are going, your profile, your guest count, and whether you checked in. Who can see the full attendee list depends on the activity: the host and co-hosts always can; so can anyone who has RSVP'd and, for an activity posted into a community, that community's members, including before they RSVP; others see only their own friends by name plus a count of everyone else. When you check in, other participants are notified. We do not record your location when you check in. To the organizers of a community you join. Your profile and role, when you joined, how you came to join (an invitation, a link, a request, or joining an open community), and the note you sent if you asked to join. Organizers also receive a notification each time someone joins, asks to join, or posts an activity, and they can see, for each member: how many of the community's activities you RSVP'd to and attended, how recently you were active, and what share of the activities you said you would attend you actually attended. They can see the roster of each of the community's past activities with check-in status, and summary measures of the community's attendance and retention built from those. This covers activities posted into the community even where the activity itself was limited to friends or to selected members. Joining posts a message in that community's chat, which can name the member who invited you. To the host of a paid activity. Your first name, your last initial and username where you set them, your neighborhood, how many tickets you bought, what you paid, and the refund status. Hosts never receive your card details, your email address, or your phone number from us. To anyone holding a share link or QR code. A link or QR code for an activity or a community can be opened by anyone who has it, including people who are not signed in, until it expires. It shows the activity or community, the first name and photo of the person who shared it, the host's first name, photo, and neighborhood, counts of attendees or members, and the first names and photos of a small number of attendees or members. On the public web. Public activity pages show the host's first name and neighborhood, the listing, and its cover photo, and after you sign in they show a small number of attendees' first names. A page that resolves a share link shows the first name, photo, and neighborhood of the person who shared it. A public community page shows the community and its upcoming public events, with a member count but no member names. Link previews for these pages can include a first name in the title, and some of these pages can be indexed by search engines. Ratings and reviews. Your review of another person is shown to them once they have also reviewed you for the same activity, and it is attributed to you. Aggregate ratings, including a host's average stars, are visible to signed-in members. Your rating of an activity, including which activity and that it came from you, is visible to signed-in members. What members are not shown. We do not display to another member your email address, your phone number, your date of birth, your exact home address or coordinates, your full last name unless you choose to display an initial, your payment details, or your similarity score. Our Terms of Service prohibit collecting, copying, or scraping other members' information, and we treat doing so as a violation. Your card details are held by our payment processor rather than by us. Limits we place on hosts and organizers. Our Host Agreement allows a host or organizer to use attendee and member information only to run that activity or community. It forbids exporting, copying, or compiling it, using it to contact you off Porchside for marketing, sharing it with anyone else, combining it with other sources to learn more about you, and keeping it after it is no longer needed, and it requires them to delete what they hold about you if you ask. We can suspend a host who breaks those rules. We cannot prevent someone taking a screenshot of what they can see, which is why this section describes what is visible rather than promising it cannot be copied. Tell us at support@porchside.co if a host misuses your information. To everyone who can see an activity that runs a tournament. Your name on its roster, the team you are on, the matches you played, and the scores recorded for them. These are visible to the same people who can see the activity itself and no wider, and they stay visible after the activity ends. The gender on your profile is copied to your roster entry, is used to balance teams where the organizer asks for that, and is shown to the organizers of that tournament only; it is not shown to the other players.
7. How We Share Your Information With Service Providers and Others
With service providers. We share information with providers who process it on our behalf, in these categories: Cloud hosting, database, file storage, and authentication providers, including the provider and telecommunications carriers that deliver one-time codes by text message, and the provider that hosts our website. Stripe, for payments, saved cards, and host payouts, including Stripe Connect onboarding for hosts. Amazon Web Services, for the facial comparison used by optional selfie verification. Push-notification and app-update delivery services, and Apple and Google, whose push services deliver notifications to your device. Push payloads can include a sender's name, an activity title, and a message preview. Google, for analytics: Firebase Analytics in the mobile app and Google Analytics 4 on the website. Error and performance reporting services for the mobile app. Mapping services, for turning a zip code into a neighborhood, for venue search, and for the map on an activity page. Some of these calls are made from your device, so the mapping provider receives your IP address and the location or query involved. Email delivery services, for transactional email including community invitations and feedback sent to our support address. Services that fetch and structure public event pages for the listings described in section 2, including a page you ask us to import when you paste an event link. We require our providers to protect information and to use it only to provide services to us. With other members. See section 6. For safety and legal compliance. We may disclose information where required by law or legal process, to protect the safety, rights, or property of users, of the public, or of Porchside, to investigate fraud or abuse, to enforce our Terms, and to respond to an emergency. Reports of child sexual abuse or exploitation are reported to the National Center for Missing and Exploited Children and to authorities as the law requires, and we preserve related data as permitted by law. With professional advisors, such as lawyers, auditors, and insurers, in the course of their services to us. Business transfers. In a merger, acquisition, financing, or sale of assets, or in insolvency, information may be disclosed to counterparties and their advisors and transferred to the acquiring entity. With the app stores, for install attribution. Where you reach a download link from one of our campaigns we read the install referrer that Google Play provides to the app on Android, and where you reach it by scanning one of our printed codes we may also pass Apple a short campaign name so that installs are counted in the App Store's own analytics, which reports totals to us and never individual people. Neither is an advertising identifier and neither is used for advertising. Within Porchside, access to your information is limited to the people on our team who need it to run the Service, support you, and keep it safe, including tools that show a member's activity on the Service. It is not open to everyone who works here. We do not sell your personal information. We do not share it for cross-context behavioral advertising or targeted advertising. We do not allow third-party advertising trackers on our website or in our app.
8. Payment Information
When you reserve a seat at a paid activity, payment information (card details, billing address, transaction amount, and related identifiers) is collected and processed by our payment processor, Stripe. Porchside does not store full card numbers or full payment credentials. We retain the references Stripe returns to us, such as a customer identifier and transaction identifiers, along with our own record of the ticket, fee, tax, refund, and payout amounts. Stripe processes payment data under its own terms and privacy policy at stripe.com/privacy. Hosts who receive payouts complete onboarding directly with Stripe; the identification and bank information collected there is held by Stripe, not by us. We retain transaction records as described in section 14.
9. Location Information
We use location in four ways. Your zip code, which you must provide to finish onboarding. We send it to a mapping provider to derive a neighborhood and approximate coordinates, which we store on your profile and use to show nearby activities and for the neighborhood signals in section 4. Your neighborhood is shown to other members; your zip code and coordinates are not displayed. Your device's current location, with your permission, while you use the app. It is sent to our server to filter and rank activities by distance and to show distances. We do not store it in your profile, and we do not track your location in the background or use geofencing. The approximate area derived from your IP address, on our website, to show you the right metropolitan area, and a cookie recording which area to show you, set from the area on your profile when you are signed in. Venue and map lookups. When you search for a venue or view an activity's map, your device sends the query or the activity's coordinates to our mapping provider. You can turn off location permission at any time in your device settings; distance features will not work without it. A zip code is required to complete onboarding, so it cannot be skipped.
10. Contacts and Address Book
If you choose to use our find-friends feature, the app accesses your device address book to help you connect with people you already know. Phone numbers are converted into cryptographic hashes on your device, and we receive only those hashes, which we compare against hashes of our members' verified numbers. We do not upload or store your contacts' names or raw numbers, and we do not contact the people in your address book on your behalf through this feature. We store a hash of your own verified phone number so that your contacts can find you. This feature is optional, and you can disable contacts access at any time in your device settings.
11. Inviting People Who Do Not Have an Account
Community organizers and members can invite people to a community by email. When a member does that, we hold the address in order to send the invitation, and we delete the readable address within a few days. We keep a cryptographic hash of it after that, so we do not invite the same person twice and so we can tell if the invitation was accepted. The invitation names the member who sent it and uses that member's own email address as the reply-to address, so recipients can reply to them directly. The invitation tells recipients why they received it and that ignoring it ends the matter. If you received an invitation and want your address removed, email support@porchside.co. A member running a tournament can add someone who has no Porchside account to its roster, by entering a name and a gender, which is used if teams are being balanced. That entry is visible to everyone who can see the activity. The member who enters it is responsible for having that person's permission, as they are for a safety contact. If you have been added to a roster and want the entry removed, ask the member running it. Once the entry has been placed on a team or played a match, it can no longer be removed in the product, so email support@porchside.co and we will do it. If a member saves you as a safety contact, we hold the name and phone number they entered. We do not currently send anything to a safety contact.
12. Website Visitors and Prospective Hosts
You can browse our website, including public activity and community pages and our directory of communities by area, without an account. Section 2 describes what we collect automatically, section 21 describes cookies, and section 9 describes the approximate area we derive from your IP address. If you scan a printed code of ours, our website records the scan before sending you where the code points: the day and time, the kind of device you used, the approximate city derived from your IP address, and, where the link was shared rather than scanned, the site it came from. We do not keep your IP address or your browser's user agent. We keep a visitor value derived from them, which lets us count a visitor once in a day and not across days, and we erase that value after 90 days. The record of the scan itself, without it, stays. Where your browser signals Global Privacy Control we derive no visitor value at all. None of this is tied to your account unless you go on to create one, in which case we record which printed code or link brought you, which is more specific than a campaign. Opening a page we sent you to also records that the visit happened, and whether you went on to act on it, in the same way and never against your account. If you fill in the host interest form, we collect your email address, the community you want to run, an optional description, category, cadence, and zip code, together with the campaign tag in the attribution cookie if there is one. We use it to contact you about hosting on Porchside and to understand where interest comes from. It is read by our own team; it is not published, and it is not sold. We keep it until you ask us to remove it, or until we no longer need it. To have it removed, email support@porchside.co with the address you submitted.
13. Sensitive Personal Information
Some information we collect is sensitive under certain U.S. state privacy laws: your precise geolocation, when you enable location access, and your biometric information, when you use selfie verification. We collect and use sensitive personal information only to provide the features you ask for, to verify identity, to support safety, and to comply with law. We do not use or disclose it to infer characteristics about you, and we do not sell it or share it for advertising. Where applicable law gives you the right to limit its use, you may exercise that right as described in section 16, and you can also avoid most of this collection by not using the optional features or by turning off the related device permissions.
14. Data Retention and Deletion
We keep information for as long as your account is active or as needed to provide the Service, and then as described here. When you delete your account, we anonymize your profile immediately: your name is replaced, and your photo, bio, neighborhood, coordinates, date of birth, and similar fields are cleared. About 30 days later we complete the deletion. Where you have no payment history, your account and the records linked to it are deleted, and messages you sent are removed from other people's conversations. Where you do have payment history, we keep an anonymized shell of your account and the underlying payment, settlement, and payout records, because we need them for tax, accounting, chargeback, and audit purposes; in that case your remaining personal details are scrubbed and the text of your messages is blanked, and the records themselves are kept for as long as the law and our obligations require. Any amount you owe us, for example the card-processing cost of refunds on an activity you cancelled, survives deletion. Your selfie verification status, score, timestamp, and consent record are retained while your account exists and are cleared when you delete it; you can also ask us to delete your verification record at any time. Some things are deleted on their own schedule. The group chat for an activity is archived once the conversation has gone quiet after the activity, and deleted about 30 days after that. The readable email address of a community invitation is deleted within a few days. Operational logs are kept for no longer than 30 days. The visitor value recorded when a printed code is scanned (section 12) is erased after 90 days; the scan record it belonged to is kept. Photos you upload can remain in our storage after the message, listing, or account they belonged to is gone. Ratings, reviews, and the aggregates built from them persist and continue to inform other members. Where you played in a tournament, your roster entry and the matches and scores recorded on it also persist, with your name replaced and the gender on the entry set back to unknown, so the activity's own record stays intact for the people who were there. Records we keep to prevent fraud, to enforce our Terms, to resolve disputes, or to comply with law are kept as long as needed for those purposes. We also keep aggregated and de-identified information indefinitely. You can ask us to delete your information at any time in the app or by emailing support@porchside.co.
15. Data Security
We use administrative, technical, and physical safeguards designed to protect information, including encryption in transit and at rest. No method of electronic transmission or storage is completely secure, and we cannot guarantee absolute security. Keep your device and your credentials secure, and tell us at support@porchside.co if you believe your account has been accessed without your authorization.
16. Your Privacy Rights and Choices
Depending on where you live, you may have the right to know what personal information we hold about you and how we use it, to receive a copy in a portable format, to correct inaccurate information, to delete your personal information, to opt out of certain processing including profiling, to limit the use of sensitive personal information, and to withdraw consent where processing is based on consent. You will not be discriminated against for exercising these rights. In the app you can edit most of your profile, manage notification categories, control device permissions, and delete your account. Everything else, including access, a portable copy, correction of information that is not on your profile, and a request about profiling, is handled by email: write to support@porchside.co and say what you want. We verify requests against the information associated with your account before we act, and we respond within the time applicable law requires. You may use an authorized agent where the law allows, and we may ask the agent for proof of authority. Some choices have consequences worth knowing. A verified phone number is required to use the mobile app, so you cannot withdraw consent to receive verification codes and keep using it; the website offers an email and password path instead. Selfie verification is optional, and you can ask us to delete your verification record. Contacts and location access can be turned off in your device settings.
17. State Privacy Rights and Appeals
California. Under the California Consumer Privacy Act, as amended, you have the rights described above, including the right to know, delete, correct, and opt out of the sale or sharing of personal information. We do not sell personal information and do not share it for cross-context behavioral advertising. This Policy is our notice at collection. On our website we honor recognized opt-out preference signals, including the Global Privacy Control: when your browser sends that signal we load no analytics tag and set no attribution cookie. Under California's Shine the Light law you may ask us for the categories of personal information we disclosed to third parties for their own direct-marketing purposes in the prior calendar year; we do not make such disclosures. Email support@porchside.co with "Shine the Light Request" in the subject. Texas, Virginia, Colorado, Connecticut, Utah, Oregon, Montana, and other states. If you are a resident of a state with a comprehensive consumer privacy law, you have the rights described above, including access, correction, deletion, and a portable copy, and the right to opt out of targeted advertising, the sale of personal data, and profiling in furtherance of decisions that produce legal or similarly significant effects. We do not sell personal data and do not use it for targeted advertising. Section 18 describes the profiling we do. Appeals. If we deny a privacy-rights request, you may appeal by replying to our response or by writing to support@porchside.co with "Privacy Appeal" in the subject. We will respond within the time applicable law requires and explain our decision. If your appeal is denied you may contact your state attorney general. Nevada. Nevada residents may direct us not to sell certain personal information by contacting support@porchside.co. We do not sell personal information as Nevada law defines it.
18. Automated Decision-Making and Profiling
We use automated processing in ways that affect what you see and, in some cases, what you can do. This section describes those uses, their effects, and how to challenge them. Ranking, pairing, and suggestions. Described in section 4. Effect: what appears in your feed and who is suggested or paired with you. An internal reliability measure. We compute a measure for each account from your record on the Service, including attendance, no-shows recorded against you, and upheld reports about you. Effect: the measure determines whether an account qualifies for our Local Host tier. It does not affect your ability to join activities, buy tickets, message people, or be placed on a waitlist. The measure is not shown to you and not shown to hosts. An automatic decision can remove the Local Host tier where the measure falls below our threshold or where a report against you is upheld. Adding the tier is not automatic: an account that qualifies goes to a person for review. Automatic no-show records. Where we have no sign that you took part in an activity you said you would attend, we may record a no-show, which lowers the measure above. Effect: as described. You are notified and you can dismiss the record yourself, which reverses it. Automatic suspension. Where multiple members have open reports about you, your account may be suspended automatically pending human review, and it stays suspended until a person reviews it and lifts it. Effect: your account is taken out of use, activities you are hosting are cancelled, your pending requests to join activities are cancelled, and you are removed from activities you had been matched into. You are notified, the reason is shown to you, and you can ask us to review it at support@porchside.co; a person reviews every such request and can lift a suspension. Eligibility limits set by hosts and organizers. Where a host or organizer has limited an activity or community by age bracket or gender, and you join that community or accept an invitation to that activity, we compare the date of birth and the gender on your profile against the limit automatically. Effect: the join is refused, and leaving gender blank counts as not matching a gender limit rather than as matching every one. The limit is the host's or organizer's setting and we apply it. If you think one has been applied to you in error, write to support@porchside.co and we will look at the activity or community and the limit set on it. Friend-request limits. Requests to people you have no connection with are limited. Effect: you may be prevented from sending a request for a time. The limit and what remains of it are shown to you in the app. Measures shown to hosts and organizers. Where you join a community, its organizers see per-member measures derived from your behavior, including the share of activities you said you would attend that you actually attended. Effect: a named judgment about you is visible to people who run communities you joined. See section 6. Referral attribution. A new member can name an existing member as the person who brought them to Porchside, which records a connection between the two accounts and can pay a referral reward. This is the new member's unconfirmed statement, and the named member is told about it. Content moderation. We may use automated signals to detect fraud, abuse, and violations of our Terms, which can lead to restrictions or suspension as described above. Human review, correction, and objection. A person reviews any suspension or restriction you ask us to review, and can reverse it. A person reviews an account before it gains the Local Host tier. Automatic Local Host removal and automatic suspension take effect pending human review, so the routes to challenge them matter: dismiss a no-show record in the app, or write to support@porchside.co. Because the reliability measure is computed from recorded events rather than entered by hand, correcting it means correcting the underlying event, for example dismissing a no-show or having a report reversed; ask us at support@porchside.co and we will review the events on your account. Where applicable law gives you a right to opt out of profiling, or to a decision made with human involvement, write to support@porchside.co and we will honor it to the extent the law requires.
19. Biometric Information
If you choose to use the optional selfie verification feature, we process information that biometric privacy laws may cover, including the Illinois Biometric Information Privacy Act, the Texas Capture or Use of Biometric Identifier Act, and Washington law. We ask for your consent before processing, we process your selfie only to compare it against your profile photo, and the comparison is performed by Amazon Web Services (Rekognition). The selfie is uploaded to our storage for the comparison and deleted as part of it; we keep a verification status, a similarity score, and a timestamp, none of which can reconstruct your face. We do not store facial-geometry templates or scans. We do not sell, lease, trade, or otherwise profit from biometric information, and we disclose it only to the service provider performing the comparison or where the law requires. Your verification badge is visible to other members; your selfie and score are not. Our retention and destruction schedule, including how to ask us to destroy your verification record, is in our Biometric Data Policy. You can use the Service without this feature.
20. Notifications, Email, and Text Messages
Push notifications. We send push notifications about matches and RSVPs, messages, reminders, ratings, reactions, friends and communities, and account and safety matters. The app lets you turn most categories off and lets you set a quiet period in the timezone we have for your device. Safety alerts, cancellation notices, and check-in reminders for an activity that is starting ignore quiet hours by design. Turning a category off stops the push notification; the item still appears in the notifications list inside the app. You can turn all push notifications off in your device settings. Notification content, which can include a sender's name, an activity title, or a message preview, passes through our push delivery service and then Apple's or Google's push service to reach your device. Email. We send account and security email through our authentication provider, invitations through an email delivery service, and replies from support. We do not send marketing email campaigns. Where we ever do, it will include a way to unsubscribe. Text messages. See section 2, section 16, and our SMS Terms. The only text messages we send are one-time codes.
21. Cookies and Tracking Technologies
Our website uses a small, fixed set of cookies and similar technologies: a cookie that keeps you signed in, a cookie that records which metropolitan area to show you, a cookie that records for 90 days which campaign or link first brought you to the site, and Google Analytics cookies. We do not use cookies for cross-context behavioral advertising, and we allow no third-party advertising trackers. We also use a few session-storage keys in your browser to remember things like where you were in a calendar. There is no cookie banner: where your browser signals Global Privacy Control the analytics tag and the attribution cookie are not set at all, and a scan of a printed code is counted without the visitor value described in section 12, and you can block or delete cookies in your browser settings, although sign-in will not work without its cookie. Our mobile app contains no advertising software and we do not use advertising identifiers. It does include analytics and error-reporting software, as sections 2 and 7 describe, and on Android that analytics software may collect an advertising identifier until an app update turns that collection off. See our Cookie Policy for more detail.
22. Data Breach Notification
We maintain safeguards designed to protect your information. If a breach of security affects your personal information, we will notify you and any authorities as applicable law requires, in the manner and within the time it requires.
23. Children's Privacy
Porchside is intended only for adults aged 18 and older and is not directed to children. We do not knowingly collect personal information from anyone under 18. We ask for date of birth during onboarding and block registration where the date given is under 18. If we learn that we have collected information from a person under 18, we delete it promptly. If you believe a minor has provided us information, or has an account, contact support@porchside.co. Our Child Safety Standards describe how we prevent, detect, and respond to child sexual abuse and exploitation.
24. International Users
The Service is operated from the United States and is intended for users in the United States. If you access the Service from outside the United States, your information will be transferred to, stored, and processed in the United States and in other countries where our service providers operate, where privacy laws may differ from those where you live.
25. Changes to This Policy
We may update this Privacy Policy from time to time. We will post the updated version with a new "Last Updated" date and, where the changes are material, notify you in the app and on the website, both of which ask you to review and accept the current version, or by email. The current version is always at porchside.co/privacy. Your continued use of the Service after changes take effect means you accept the updated Policy.
26. Contact Us
For questions about this Privacy Policy, or to exercise a privacy right, contact us at support@porchside.co. Kinward, Inc. Austin, Texas