{"id":959,"date":"2019-11-27T07:12:06","date_gmt":"2019-11-27T14:12:06","guid":{"rendered":"https:\/\/help.fooevents.com\/docs\/topics\/products\/fooevents-plugin-privacy-policy\/"},"modified":"2026-03-02T00:57:36","modified_gmt":"2026-03-02T08:57:36","slug":"politica-de-privacidad-del-plugin-fooevents","status":"publish","type":"docs","link":"https:\/\/help.fooevents.com\/es\/docs\/topics\/fooevents-plugins\/fooevents-plugin-privacy-policy\/","title":{"rendered":"Pol\u00edtica de privacidad del plugin FooEvents"},"content":{"rendered":"<h2>Sections<\/h2>\n<ul>\n<li><a href=\"#how-fooevents-stores-data\">How FooEvents Stores Data<\/a><\/li>\n<li><a href=\"#how-to-remove-data\">How To Remove Data<\/a><\/li>\n<li><a href=\"#user-roles-capabilities-and-permissions\">User Roles, Capabilities and Permissions<\/a><\/li>\n<\/ul>\n<h3>How FooEvents Stores Data<\/h3>\n<h3 id=\"database\">Database<\/h3>\n<p>FooEvents stores basic plugin configurations within the WordPress database using standard WordPress methods. All settings and configurations are stored within the wp_options table.<\/p>\n<p>FooEvents extends WooCommerce product functionality to create event products. This is done by adding certain meta to products using standard WordPress and WooCommerce methods. All event meta is stored within the wp_postmeta table where the post_id matches the product ID.<\/p>\n<p>On checkout, attendee, ticket, and customer data are stored as meta within the WooCommerce order custom post type in the <i>wp_postmeta<\/i>\u00a0table. This data is stored where the meta_key = \u201cWooCommerceEventsOrderTickets\u201d and where the\u00a0<i>post_id matches<\/i>\u00a0the custom post type order ID.<\/p>\n<p>FooEvents uses a custom post type to create event tickets. This custom post type is named \u201cevent_magic_tickets\u201d and is stored in the\u00a0<i>wp_posts\u00a0<\/i>table. Meta is added to the ticket custom post type which contains ticket details and is stored within the\u00a0<i>wp_postmeta<\/i>\u00a0table where the post_id matches the \u201cevent_magic_ticket\u201d ID.<\/p>\n<h3 id=\"ics-files\">ICS Files<\/h3>\n<p>When the \u201cDisplay \u2018Add to calendar\u2019 on ticket?\u201d option is enabled in product event settings, this adds functionality that end users can download .ics files to add events to their calendars. This file is generated as soon as the end user clicks the \u201cAdd to calendar\u201d button on their ticket and is not automatically updated remotely. The .ics files contain basic event information such as event name, date and time.<\/p>\n<h3 id=\"csv-export-files\">CSV Export Files<\/h3>\n<p>FooEvents contains functionality that allows the event organizer to export all event attendees and their details. This export feature is intended to be used as a backup in case the website administrator doesn\u2019t have access to attendee check-in functionality, as found in the\u00a0<a href=\"https:\/\/www.fooevents.com\/fooevents-express-check-in\/\" target=\"_blank\" rel=\"noopener\">FooEvents Express Check-in<\/a>\u00a0plugin and\u00a0<a href=\"https:\/\/www.fooevents.com\/apps\/\" target=\"_blank\" rel=\"noopener\">FooEvents Check-ins app<\/a>\u00a0for example. Information that is stored in this CSV export includes attendee and purchaser details, completed custom fields and selected variations and billing information (e.g. address, ticket check-in statuses).\u00a0<b>NB: The CSV export file is portable and printable and therefore appropriate care should be taken to keep this file safe by the site administrator and event staff.<\/b><\/p>\n<h3 id=\"mobile-apps\">Mobile Apps<\/h3>\n<p>The\u00a0<a href=\"https:\/\/www.fooevents.com\/apps\/\" target=\"_blank\" rel=\"noopener\">FooEvents Check-ins app<\/a> uses the built-in WordPress <strong>REST API<\/strong> to communicate with FooEvents plugins in order to retrieve event and attendee data as well as process ticket check-ins. If the <strong>REST API<\/strong> is not accessible, the app tries to communicate via the built-in WordPress <strong>XML-RPC<\/strong> connection as a fallback. Data that is transferred between the plugins and app includes: Attendee and purchaser data, event data, ticket check-in status.<\/p>\n<p>The app has offline features and therefore caches retrieved data on the device. The cached file is stored using standard iOS and Android security best practices.<\/p>\n<h3 id=\"barcodes\">Barcodes<\/h3>\n<p>FooEvents generates barcodes based on the unique ticket ID generated by the FooEvents plugin. Barcodes are used for ticket check-ins. The barcodes are stored in the \u2018<i>wp-content\/uploads\/fooevents\/barcodes<\/i>\u2018 directory. The barcode filename is generated using the following formats:<\/p>\n<pre>[unique-ticket-hash]-[unique-ticket-ID].jpg + [unique-ticket-hash]-[unique-ticket-ID].png<\/pre>\n<p>Each ticket is assigned a unique ticket hash, ticket ID and ticket generation time. Barcodes are accessible via HTTP.<\/p>\n<h3 id=\"pdf-tickets\">PDF Tickets<\/h3>\n<p>When the FooEvents PDF Tickets plugin is active and enabled, PDF copies of tickets are generated and stored in the \u2018<i>wp-content\/uploads\/fooevents\/pdftickets<\/i>\u2018 directory.<\/p>\n<p>Single PDF tickets are named using the following format:<\/p>\n<pre>[unique-ticket-hash]-[unique-ticket-ID].pdf<\/pre>\n<p>Multiple PDF tickets are named using the following format:<\/p>\n<pre>[first-ticket-unique-ticket-hash]-[first-ticket-unique-ticket-ID]-[last-ticket-unique-ticket-hash]-[last-ticket-unique-ticket-ID].pdf<\/pre>\n<p>PDF tickets contain purchaser and attendee data, event data and end user selected variations. PDF tickets are accessible via HTTP.<\/p>\n<h3 id=\"emails\">Emails<\/h3>\n<p>When the product event ticket option \u201cEmail tickets?\u201d is enabled, the tickets are sent to either the attendee or purchaser depending on whether the \u201cEmail attendee rather than purchaser?\u201d option is enabled or disabled. Tickets contain purchaser and attendee data, event data and end user selected variations. Once a ticket has been sent out, it will be stored indefinitely on the website administrators email server depending on the email address\/es that were completed at checkout.<\/p>\n<h3 id=\"how-to-remove-data\">How To Remove Data<\/h3>\n<h3 id=\"removing-tickets-and-orders\">Removing Tickets and Orders<\/h3>\n<p>To remove tickets:<\/p>\n<ol>\n<li>Navigate to the <strong>Ticket<\/strong>\u00a0admin section in your WordPress Admin Area<\/li>\n<li>Highlight the ticket\/s that should be deleted<\/li>\n<li>Select <strong>Move to bin<\/strong>\u00a0in bulk actions and click <strong>Apply<\/strong><\/li>\n<li>Navigate to the ticket <strong>Bin<\/strong><\/li>\n<li>Highlight the ticket\/s that should be deleted<\/li>\n<li>Select <strong>Delete permanently<\/strong>\u00a0in bulk actions and click <strong>Apply<\/strong><\/li>\n<\/ol>\n<p>To remove orders:<\/p>\n<ol>\n<li>Navigate to <strong>WooCommerce<\/strong>\u00a0&gt; <strong>Orders<\/strong><\/li>\n<li>Highlight the ticket\/s that should be deleted<\/li>\n<li>Select <strong>Move to bin<\/strong> in bulk actions and click <strong>Apply<\/strong><\/li>\n<li>Navigate to the order <strong>Bin<\/strong><\/li>\n<li>Highlight the ticket\/s that should be deleted<\/li>\n<li>Select <strong>Delete permanently<\/strong>\u00a0in bulk actions and click \u201c<strong>Apply<\/strong><\/li>\n<\/ol>\n<h3 id=\"removing-plugin-options-and-settings\">Removing Plugin Options and Settings<\/h3>\n<p>To remove all FooEvents options and settings, simply disable and uninstall the plugins. The plugins will automatically remove all options and settings from the database during the uninstallation process.<\/p>\n<h3 id=\"removing-fooevents-files\">Removing FooEvents Files<\/h3>\n<p>To remove the FooEvents files:<\/p>\n<ol>\n<li>Disable and uninstall the plugins as per above instructions (Removing Plugin Options and Settings)<\/li>\n<li>Connect to your web server via an FTP client and navigate to \u2018<i>wp-content\/plugins<\/i>\u2018 in the WordPress directory. Ensure that all FooEvents plugin directories have been deleted.<\/li>\n<li>Connect to your web server via an FTP client and navigate to \u2018<i>wp-content\/uploads<\/i>\u2018 in the WordPress directory and delete the entire\u00a0<i>\u2018fooevents\u2019<\/i>\u00a0folder<\/li>\n<\/ol>\n<h3 id=\"user-roles-capabilities-and-permissions\">User Roles, Capabilities and Permissions<\/h3>\n<p>FooEvents makes extensive use of the built-in WordPress user role and capability functionality to ensure better\u00a0privacy. By default, only users with the role of \u201cAdministrator\u201d will have access to all the FooEvents features. If you require an additional WordPress user role to have access to specific FooEvents features, you will need to assign capabilities to this role using a third-party WordPress plugin.<\/p>\n","protected":false},"featured_media":0,"parent":938,"menu_order":10,"comment_status":"open","ping_status":"closed","template":"","meta":{"site-sidebar-layout":"default","site-content-layout":"default","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"default","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-959","docs","type-docs","status-publish","hentry"],"comment_count":0,"_links":{"self":[{"href":"https:\/\/help.fooevents.com\/es\/wp-json\/wp\/v2\/docs\/959","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.fooevents.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/help.fooevents.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/help.fooevents.com\/es\/wp-json\/wp\/v2\/comments?post=959"}],"version-history":[{"count":1,"href":"https:\/\/help.fooevents.com\/es\/wp-json\/wp\/v2\/docs\/959\/revisions"}],"predecessor-version":[{"id":146652,"href":"https:\/\/help.fooevents.com\/es\/wp-json\/wp\/v2\/docs\/959\/revisions\/146652"}],"up":[{"embeddable":true,"href":"https:\/\/help.fooevents.com\/es\/wp-json\/wp\/v2\/docs\/938"}],"prev":[{"title":"FooEvents TPV","link":"https:\/\/help.fooevents.com\/es\/docs\/topics\/fooevents-plugins\/fooevents-pos\/","href":"https:\/\/help.fooevents.com\/es\/wp-json\/wp\/v2\/docs\/133560"}],"wp:attachment":[{"href":"https:\/\/help.fooevents.com\/es\/wp-json\/wp\/v2\/media?parent=959"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/help.fooevents.com\/es\/wp-json\/wp\/v2\/doc_tag?post=959"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}