Privacy Policy

1.Operator and contact

Yinzlist is operated by Community Access Project Inc., a Pennsylvania nonprofit corporation, which is the controller of the information described in this policy. Enquiries regarding this policy or the exercise of any right described in it may be directed to info@communityaccessproject.org.

2.Information collected

The application collects the following categories of personal information, each supplied by the user in the course of using the service:

Apple account identifier

An account is created by signing in with Apple. Apple supplies an identifier which is particular to this application and which identifies no one outside it. Neither the name nor the email address Apple can provide is requested. No password is held, and this identifier is not displayed to other users.

Name

A first name, supplied at registration, displayed to other users.

Username

An account identifier, supplied at registration, displayed to other users and used in invitation links.

Neighborhood

A neighborhood within the City of Pittsburgh, selected by the user, displayed to other users and used to determine the content shown.

Photograph

An optional profile photograph, an optional photograph for a group the user administers, and any photographs attached to a submission, displayed to other users.

User content

Posts, comments, and records of attendance submitted by the user.

Contacts and connections

The other users and groups a user is connected to.

Reports

Where a user reports a post or an account, the subject of the report, the reason selected, and any note the user writes. A note is free text and may describe another user. A report is visible to the user who made it and to a moderator; it is never shown to the user reported.

Feedback

Messages a user sends from the feedback screen, with the application version. Feedback is not shown to other users.

Blocks and hidden sources

The accounts a user has blocked and the event sources a user has removed from their own feed. Neither is shown to any other user.

Claims of an organisation page

Where a user asks to be recognised as responsible for an organisation's page, the account of themselves they submit in support of the request, and any contact detail they choose to include.

Telephone number

Where a telephone number is provided, it is collected and stored, and is used to verify the account, to send messages and notifications relating to the service, and to permit other users who already hold the number to locate the account.

Address book

Where the user grants permission, the telephone numbers held in the device's address book. No other field of a contact record is read.

3.Use of information

Personal information is used solely to operate the service: to create and maintain an account, to display a user's profile and submissions to the audience the user selected, to determine which content is shown, and, where a telephone number has been added, to verify that number and to enable contact matching under clause 5. Personal information is not sold.

Where a user chooses to add an event to their calendar, the application writes that event to the calendar held on the device. This requires the permission of the operating system. The application does not read the calendar, and no calendar information is transmitted to the service.

4.Disclosure to third parties

Personal information is held on servers operated by Community Access Project and hosted by Microsoft Azure in the United States. Information is disclosed to the following third parties, in each case as a consequence of an action taken by the user. As with any request made over the internet, each request identified below discloses the Internet Protocol address of the device to the receiving party, together with the technical information ordinarily contained in such a request, and the receiving party may record it.

• OpenStreetMap Foundation Where a user searches for a street address, the text entered is transmitted to the OpenStreetMap public geocoding service in order to resolve it to a coordinate. A search entered as a place name rather than an address does not generate such a request.
• Apple Inc. Map imagery is provided by Apple's mapping service through the operating system. The portion of the map being displayed is disclosed to that service. Such disclosures are governed by Apple's own privacy policy.
• Apple Inc. Signing in is performed by the operating system against Apple's own service. That exchange is between the user and Apple and is governed by Apple's privacy policy; what reaches this service is an identifier and nothing else.
• Telecommunications provider Where a user elects to add a telephone number, that number is disclosed to a message delivery provider for the purpose of transmitting a verification code.

Personal information may also be disclosed where disclosure is required by law or by valid legal process.

5.Contact matching

Contact matching is a feature that requires the user's express permission through the operating system. Where permission is granted, the application reads the telephone numbers held in the device's address book and no other field of a contact record. Each number is converted on the device into a SHA-256 digest, and it is those digests, to a maximum of two thousand, that are transmitted to the service. The address book itself is not transmitted and is not stored. A digest that does not correspond to a registered account is discarded and is not recorded, so a person who is not a user of the service does not become known to it by appearing in somebody's address book.

Users should understand what that protection does and does not extend to. It protects the people in a user's address book. It does not make a telephone number that has been added to an account under clause 2 private from the operator: a telephone number is short enough that every possible number can be converted to a digest and compared, and the digests must be calculated identically for every user in order to match at all, so no measure is available that would prevent this. A number added to an account should therefore be understood as held by the operator, and it is held in the manner described in clauses 2, 3 and 7.

6.Information visible to other users

A user's name, username, neighborhood, and photograph, if supplied, are displayed on that user's profile, together with that user's forthcoming submissions. Each submission is displayed, together with the user's name, to the audience the user selected for it. A submission addressed to the whole city is available to every user of the service.

A user's connections are not displayed as a list. Where one user views another user's profile, the connections and groups the two of them have in common are displayed, and no other part of either user's connections is disclosed.

7.Retention, export, and deletion

Personal information is retained until the user deletes it. Both of the following controls are provided within the application, under Privacy on the Me tab, and neither requires a request to Community Access Project:

Export

Produces a single file containing the personal information associated with the account, comprising the profile, the telephone number where one is held, submissions, attendance records, comments, connections, and groups.

Deletion

Deletes the account and the personal information associated with it from the database immediately. No retention period is applied and no deactivated state is maintained. Backup copies, kept only to restore the service after a failure, are deleted in the ordinary course within fifteen days.

Comments submitted under another user's post are deleted with that post. Event listings obtained from a public calendar published by a third party are not personal information of the user and are not deleted.

8.This website

The pages at yinzlist.com are static files served by GitHub Pages. GitHub, Inc. maintains ordinary web server logs, including the Internet Protocol address of the requesting device and the resource requested. Those logs are maintained by GitHub under its own privacy policy and are not accessible to Community Access Project.

A visitor may leave an email address on the home page to be told when the application is available. The address is held on the servers described in clause 4, is used only to send that notice, and is not disclosed to any third party. It is deleted once the notice has been sent, or earlier on request to the address in clause 1, and leaves backup copies as described in clause 7.

9.Children

The service is not directed to children and is not intended for use by persons under the age of 13. Community Access Project does not knowingly collect personal information from any person under the age of 13. A parent or guardian who believes that such information has been collected may contact the address in clause 1, and the information will be deleted.

10.Amendment

This policy may be amended. The effective date shown at the head of this page is the date of the most recent amendment. A change to the application that would render a statement in this policy inaccurate is made together with the corresponding amendment to this policy.

Enquiries: info@communityaccessproject.org