The electronic RPC system was developed to support the process of resolving program related disagreements and create a repository of information related to these requests in one location. From the initial submittal to the final resolution, this site will provide the necessary tools to complete the process.

According to OnlyFans transparency reports, in February 2025, the platform received 103 data requests from global users over their personal data. This represents a decrease from February 2024, when the personal data requests submitted to OnlyFans were approximately 1,119. In the second half of 2024, video content platform OnlyFans received a total of 1,575 data requests.

In the second half of 2022, all user data requests issued to Microsoft by law enforcement agencies in the Dominican Republic resulted in the disclosure of only subscriber or transactional data, excluding content data. In the Lithuania, over 90 requests ended up with partial disclosure.

This table contains information regarding requested open data sets. Requesters have been hidden to protect personally identifiable information.

Between January and July 2024, Google received 61,402 requests for disclosure of user information from the United States federal agencies and courts. This is a slight decrease in comparison to the second half of 2023, in which over 63,000 requests were issued.

Disbursement Request Form Moto GP 2023

These are requests for particular government dataset to be made public (and ideally open). The requests are added by anyone, using a form at data.gov.uk and they are listed at https://data.gov.uk/data-request

Only 'public' data requests are included in the data published here. Confidential requests can also be made, e.g. for commercial confidentiality. There is a count of them provided on https://data.gov.uk/data-request which at the time of writing stands at 522 confidential requests out of 1257 dataset requests.

There are two versions of the data:

• v1 - missing a couple of fields. Live data (always up to date).
• v2 - contains all the public fields. Produced nightly. System fields: nid, url, created, updated. Requester fields: title submitted_by data_themes status description suggested_use suggested_use_detail benefits_overview. Government response: publisher dataset_link field_review_notes.

Policy for requests:

• a "data request" is a request for government to publish a dataset that is not yet published on data.gov.uk. Requests associated with specific datasets already on data.gov.uk should instead be made in a comment on the particular dataset page.
• only central government and its agencies are available in these requests. For others organizations, contact them directly and consider making an FOI request.
• your personal data should not be requested with this method - contact the relevant organization directly. each request will be directed to the relevant department by the Cabinet Office team.

(These have been shown on the form since late 2015, and before that the policy varied)

Data requests on file date back to September 2012.

Please fill out the linked form for any Water GIS data requests.We will provide the requested information for any potable, raw, or reclaimed water utilities in the defined area, in the form of shapefiles and kmz, once a data agreement has been received.For stormwater and wastewater infrastructure, please see our Open Data website: Storm GIS layers Waste GIS layers Stormwater and Wastewater overview map (this map also shows hydrant locations)For civil plans, please see our Property Information Maps. Information on how to utilize this map to access plan sets can be found here.If you are looking for older as-builts and plans not available through the Property Information Map, please contact waterengineering@auroragov.org.

This dataset contains the list of dataset nominations submitted to the NYC Open Data team.

All 311 Service Request from 2010 to Present. Starting in November 2011 the data will be updated on a daily basis.

In the first half of 2024, Facebook received over 99,000 user data requests from law enforcement agencies of India. The United States ranked second, with over 81,000 user data requests, followed by Brazil, with nearly 26,000 requests. During the measured period, a total of 324,000 requests were submitted to the social network.

Here you can find details on data items that have been requested as additions to the ESO data portal, along with any responses from the ESO as appropriate. We welcome any further suggestions or questions regarding future data items or portal functionality, please get in touch with us at box.OpenData.ESO@nationalgrideso.com

Service request data from MyLA311. This includes requests submitted via 3-1-1, call centers, email, mobile apps, website, and other sources.

This data set includes all channels of engagement in which a service request is created.

Refer to this link to learn more about BOS:311: https://www.cityofboston.gov/311/

Requests for public data to the State

Information on all MC311 Service Requests received (via email or phone) since July 1, 2012. This data is updated daily. The PIO’s business requirement includes adding the following data elements to the new and enhanced open data site being proposed by DTS. This data is derived from requests for service which originate in the CSC, from the County’s web portal, and via “walk-ins” from county departments including but not limited to DHCA. • SLA – to indicate the number of days in county business days the department has to fulfill the request. County business days must exclude weekends, county holidays and days when the county is closed due to inclement weather (snow days, etc) per CountyStat’s business requirement. This field has been published in the existing MC311 Service Requests dataset with the field name ‘Attached Solution SLA Days’. • +/- SLA –to indicate the number of days a service request is over or under SLA as is currently measured by CountyStat. The following 4 fields will be added to fulfill this line item  # of days open – Number of County Business days the Service Request has been opened.  Within SLA Window? - To indicate the number of days a service request is over or under SLA as is currently measured by CountyStat.  SLA Yes – Number of days to fulfill the service request is under the SLA window.  SLA No -– Number of days to fulfill the service request is over the SLA window.

Information on all MC311 Service Requests received (via email or phone) since July 1, 2012. This data is updated daily. The PIO’s business requirement includes adding the following data elements to the new and enhanced open data site being proposed by DTS. This data is derived from requests for service which originate in the CSC, from the County’s web portal, and via “walk-ins” from county departments including but not limited to DHCA. • SLA – to indicate the number of days in county business days the department has to fulfill the request. County business days must exclude weekends, county holidays and days when the county is closed due to inclement weather (snow days, etc) per CountyStat’s business requirement. This field has been published in the existing MC311 Service Requests dataset with the field name ‘Attached Solution SLA Days’. • +/- SLA –to indicate the number of days a service request is over or under SLA as is currently measured by CountyStat. The following 4 fields will be added to fulfill this line item  # of days open – Number of County Business days the Service Request has been opened.  Within SLA Window? - To indicate the number of days a service request is over or under SLA as is currently measured by CountyStat.  SLA Yes – Number of days to fulfill the service request is under the SLA window.  SLA No -– Number of days to fulfill the service request is over the SLA window.

DEQ Public Records Request Data

During the second half of 2023, Facebook received 1,067 requests for user data from the Israeli government. Overall, 79.29 percent of requests resulted in data being produced.

311 is a City of Cleveland program for reporting complaints and submitting service requests for non-emergency issues, such as potholes or problems with trash pickups. For emergencies, dial 911.This dataset includes 311 requests filed since 2/29/24. All records filed before 2/29/24 are archived. To view this list of archived 311 requests, click here. More information on Cleveland 311 can be found here: https://www.clevelandohio.gov/311.Please note: Prior to the new system launching on 9/4/2024, some dates in the close_date field are after the true date of closure.Update FrequencyDaily around 7:00 AM ESTContacts:311 or Open Data Team (opendata@clevelandohio.gov)Data GlossaryThis dataset is based on the Open311 data standard.Column | Descriptionservice_request_id | The unique ID (reference number) of the service request created in the 311 system.service_name | The human-readable name of the service request type.division_responsible | The Division or operation unit responsible for fulfilling or otherwise addressing the service request.agency_responsible | The Department responsible for fulfilling or otherwise addressing the service request.status_description | A single-word indicator of the current state of the service request.address | Human-readable address or description of location.requested_date | The date and time when the service request was made.updated_datetime | The date and time when the service request was last modified.closed_date | Date and time the request record was closed or cancelled.target_date | The date by which the request is targeted to be addressed by the responsible Department. source | Mechanism or path by which the service request was received.parcelpin | The parcel number corresponding to the location.neighborhood | The neighborhood of the location.ward_name | The readable ward name of the ward corresponding to the location.ward | The number of the ward corresponding to the locationlat | Latitude of the location in decimal degrees.long | Longitude of the location in decimal degrees.Related Data Products:Cleveland 311 Request ExplorerCleveland 311 Service Request Report