1. DEFINITIONS

• 1.1. We will define below:
  • 1.1.1. "site", All the set of resources and services traceable to the web address www.pamast.com (and via redirect from www.pagemainstage.com) including the domain names pamast.com and pagemainstage.com.
  • 1.1.2. "third party", the whole set of third party software resources and services directly hosted on the site such as the integrated contents of facebook and google, and all the set of third party services and resources that, although not directly incorporated on the site, contribute to its usability and management, such as the resources and hardware and software services of the hosting provider.
  • 1.1.3. "owner of the site", the holder and owner of the domain pamast.com and pagemainstage.com, as well as the entire intellectual work traceable to the web address www.pamast.com (and via redirect from www.pagemainstage.com), with the exception of the resources and services of third parties hosted on the site which are exclusive property and responsibility of their respective owners.
  • 1.1.4. "use of the stage" or "access to the stage", the chance for the user to publish (through the page integration plugin provided by facebook.com) a public facebook page on the home page of the site, in the manner provided by the site.
  • 1.1.5. "publication" or "publication of a page", the effective publication of a facebook page (through the use of page integration technology provided by facebook.com) started by a blue form or a green form (it will be specified if necessary) in home page page of the site in a given room.
  • 1.1.6. "facebook page", a public facebook page web address of the type indicated at this address https://www.facebook.com/business/products/pages, excluding then all other types of facebook page.
  • 1.1.7. "timestamp", a time information that means the number of seconds between the date defined "Unix Epoch" (1 January 1970, 00:00:00 UTC) and the moment in which the timestamp is summoned, in this way is possible to indentify a precise moment in the time flow that can be eventually converted into date and time format (UTC).

2. PRIVACY POLICY

• 2.1. This information is provided to visitors of the site starting from the www.pamast.com address (with the exclusion of external links), in compliance with Legislative Decree n. 196/2003 as subsequently amended and in implementation of EU Regulation no. 2016/679 (called "GDPR").
• 2.2. Cookie:
  
  Cookies are text files containing data in string format that computer systems can send to the user's terminal for various needs in order to be retransmitted to the computer system by the user's terminal at the next visit. Cookies can be first-party (i.e. sent directly to the user by pamast.com) or third-party (i.e. sent and managed by third-party services). The period of activity of cookies depends from their type and purpose, some types may be active only until the browser is closed, others may have an unlimited duration.
• 2.3. The user can change the settings of the main browsers to limit the effectiveness of cookies until to inhibit their installation, some types of cookies are necessary for the correct technical functioning of the site and their complete inhibition could make impossible by the user to use its features. Further information on how to manage cookie settings in main browsers can be found below:
  • 2.3.1. Chrome
  • 2.3.2. Firefox
  • 2.3.3. Edge/Internet Explorer
  • 2.3.4. Opera
  • 2.3.5. Safari
• 2.4. According with the provision of the Guarantor for the protection of personal data "Identification of simplified procedures for the information and the acquisition of consent for the use of cookies" published on 3 June 2014, consent to the use of cookies can be given in a simplified way, by the the appearance of a banner containing the brief information, in the following ways:
  • 2.4.1. By performing a scrolling action (so-called scrolling down) within any page of the site.
  • 2.4.2. By clicking on one of the internal links from any page of the site.
  • 2.4.3. By clicking on the "I AGREE" button in the banner containing the brief information about cookies.
• 2.5. This site uses first-party technical cookies, these cookies do not collect personal data relating to the user, but are used exclusively for the correct technical functioning of some sections of the site. In the pages that require the use of these cookies, they will be immediately destroyed after they have carried out their task strictly aimed at the technical rendering of the pages.
• 2.6. This site makes use of third-party cookies relating to third-party services integrated into the site:
  • 2.6.1. Facebook Page Plugin » The cookies of this service have the purpose of allowing a browsing experience enriched by features and services belonging to the social network facebook.com, click here to know more about facebook cookies policy or click here to know more about facebook privacy policy.
  • 2.6.2. Google Analytics (with ip anonymization) » The cookies of this service collect anonymized data for statistical purposes for internal use as well as the analysis and monitoring of access to the site by the users, click here to know more about google cookies policy or click here to know more about google privacy policy.
• 2.7. Type of data collected by this site:
  • 2.7.1. Navigation data » This type of data includes all personal data that computer systems and software acquire during their normal operation and whose transmission by the user is implicit in the common use of internet communication protocols. These data are the IP addresses or domain names of the computer used by the user, the type of browser used by the user, the addresses in the Uniform Resource Identifier (URI) notation of the requested resources, the domain name and the addresses of websites from which the user arrives on the site, the information about the pages visited within the site, the stay on a single page, the time of the request for access to the site, the method used to submit the request to the server, the size of the file obtained in response, the numerical code indicating the status of the response given by the server (success, error, etc.) and other parameters relating to the operating system and the user's IT environment. These data are used only to obtain anonymous statistical information about the use of this site and to allow it to work correctly and will be destroyed once their function is exhausted for this purpose.
  • 2.7.2. Data provided by the user » The explicit and voluntary sending of e-mails via contact form and/or email involves the acquisition of the sender's email address (necessary to answer to the request sent), as well as any other data included in the communication itself, including technical data strictly linked to internet protocols and implicitly included in the communication. For some types of request, the sender's email address is stored in database (in encrypted form) as a necessary operation for the technical purposes relating to the request itself, in this case the email address will be stored in database only for time strictly necessary to carry out the type of request sent, at the end of which it will be automatically deleted from the system.
• 2.8. Owner of the data processing:
  
  The owner of the site (see 1.1.3) can be contacted for questions concerning the privacy policy at the email address .
• 2.9. Purpose of the processing of data collected according to art. 6 of the GDPR
  • 2.9.1. Allow the site to provide its services to the user.
  • 2.9.2. Improve the services by collecting statistical data on the use of the site.
  • 2.9.3. Communicate with the user if necessary.
  • 2.9.4. Fulfill applicable legal obligations and respond to requests from competent authorities.
  • 2.9.5. Protect our own rights.
• 2.10. Data retention period:
  
  The data will be kept for the period indicated in points 2.7.1 and 2.7.2 based on the related purposes, it may happen that some data have to be kept for a longer period if it is necessary to comply with a legal obligation or by order of a authority.
• 2.11. Methods of data processing:
  
  The data processing is managed through manual, computerized and telematic tools, however, in order to guarantee security, confidentiality and to avoid unauthorized access, dissemination, modification and theft of data thanks to the adoption of adequate technical security measures, physical and organizational.
• 2.12. Interaction with external social networks:
  • 2.12.1. Facebook Page Plugin » The site uses social plug-in of facebook.com, marked with the facebook logo and managed by Facebook Inc. The interaction of the user with these plug-in will involve the acquisition by facebook of some of his data and may take place in the following ways:
    • 2.12.1.1. If the user visits a page of pamast.com containing this plug-in, your browser will establish a direct connection with the facebook server, this involves the acquisition by the facebook systems of the user's navigation data on that page.
    • 2.12.1.2. If the user is connected to facebook, facebook can assign the user's visit to his facebook account. If the user interacts with the plug-in (for example by using the "Like" button or by leaving a comment), the browser transmits the corresponding information directly to facebook where they are stored. If the user does not want facebook to collect data in the manner indicated in this point, he must log out of his facebook account before visiting pamast.com.
  • 2.12.2. The purpose of data collection, their further processing and use by facebook, as well as the related rights and settings available to users in order to protect their privacy, can be consulted in the facebook privacy policy by clicking here.
• 2.13. Data retention and transferability:
  
  Users data are stored on servers located in Italy. User data may be freely transferred outside the national territory to countries located in the european union as well as to countries located outside the european union.
• 2.14. According to art. 15 of the GDPR, the user has the right to:
  • 2.14.1. Ask the data controller for access to personal data and the correction or cancellation of the same, or the limitation of the processing of data concerning him or to oppose their processing, in addition to the right to data portability.
  • 2.14.2. Obtain without obstruction from the data controller, the data in a structured format of common use and readable by an automatic device to transmit them to another data controller.
  • 2.14.3. Revoke the consent to the processing, without prejudice to the lawfulness of the processing based on the consent acquired before the revocation.
  • 2.14.4. Propose a complaint to the Authority for the Protection of Personal Data.
• 2.15. Consent formula, having acquired the above information, browsing and/or using this site, I declare that I have read the Privacy Policy in chap. 2 and to accept it in full. The Privacy Policy in chap. 2 may suffer changes over time without notice, being aware of it, I declare to stay up to date on any changes made, committing myself to consult this page regularly. If I do not accept the terms of the Privacy Policy in chap. 2, or any update, I will stop using this site.

3. GENERAL CONDITIONS OF ACCESS TO THE SITE

• 3.1. The site offers the chance to use the six rooms available on the stage in home page to publish a valid and suitable facebook page (see 3.6 and 3.9) through the integration plugin provided by the facebook platform.
• 3.2. The whole site is offered to the public as it is, without any kind of guarantee and may suffer occasional service interruptions due to technical or emergency factors (which we will try to minimize), if this happens during the publication of facebook pages the time lost by the pages during the interruption of the service would not be recovered, in any case the site owner reserves the exclusive right to decide case by case basis how to proceed in similar situations.
• 3.3. It's absolutely forbidden:
  • 3.3.1. Damage and/or destroy the devices of the site, of the resources of third parties and/or the devices of users visiting the site.
  • 3.3.2. Forcing in any way the execution of code to induce functionality other than those provided by the site.
  • 3.3.3. Install unauthorized code to induce functionality other than those provided by the site.
  • 3.3.4. Forcing access to any restricted areas on the site.
  • 3.3.5. Any other conduct that constitutes a crime under Italian law.
• 3.4. If unlawful conduct is detected, the site owner reserves to himself the right to act (possibly also in agreement with the third-party service managers), with all the technical and legal tools at his disposal to protect the integrity of the site, of the resources of third parties that contribute to its operation and of the visitor, if requested also by providing the necessary information to the authorities.
• 3.5. The owner of the site in no case and in no way will be responsible for the contents of facebook page that users of the site (through the use of the various features available) will enter directly, or indirectly, into the site contents. This responsibility will be totally and exclusively belonged to the users.
• 3.6. The publication in the areas of the site of a facebook page is only allowed to facebook pages considered suitable. A facebook page is not considered suitable when it has contents (or references to content) sexually explicit, violent, obscene, deceptive, fraudulent, offensive, illegal type.
• 3.7. The site owner (without any notification or notice) reserves to himself the exclusive, arbitrary, unilateral and unquestionable right to decide at any time what is appropriate for the site and what is not, possibly even in the case of facebook pages that do not fall into the categories indicated at point 3.6. The site owner may at any time prevent facebook pages judged unsuitable from any presence on the site and/or any use of the site (even in the case of facebook pages previously judged suitable), he may interrupt ongoing publications and/or change at any time the characteristics of ongoing publications.
• 3.8. If a user successfully publishes a facebook page in any area of the site and after the page contents should change into one of the contents judged unsuitable by these terms of use, the site owner reserves to himself the right to act as indicated at point 3.7.
• 3.9. A facebook page address is considered formally valid for use on the site if:
  • 3.9.1. It's entered where required, in one of these three formats:
    • 3.9.1.1. "http://www.facebook.com/page_id"
    • 3.9.1.2. "http://m.facebook.com/page_id"
    • 3.9.1.3. "https://www.facebook.com/page_id"
    • 3.9.1.4. "https://m.facebook.com/page_id"
    • 3.9.1.5. "facebook.com/page_id"
  • 3.9.2. It belongs to public facebook pages of the type indicated at this address https://www.facebook.com/business/products/pages
  • 3.9.3. The related facebook page, is not subject to any measure of exclusion from the activity of the site (see point 3.7).
• 3.10. The user by contacting the owner of the site for any type of matter, declares to always provide correct information corresponding to the truth and to respond exclusively and totally for any direct and indirect consequence relating to the transmission of incorrect information or not corresponding to truth.

4. TICKET CODE REQUEST AND ISSUING MECHANISM

• 4.1. In the contact area, using the option "Request ticket code for a facebook page" of the contact form, will be possible to request a ticket code, the use of which in the green form will allow to the facebook page paired with it, to be published in home page for a certain period of time.
• 4.2. For the use of this function are allowed only web addresses relating to valid facebook pages and not subject to any measure of exclusion from site activity (see 3.6, 3.7 and 3.9) and email addresses of the type "gmail.com".
• 4.3. Once a ticket code request has been successfully sent:
  • 4.3.1. A confirmation link will be sent to the email specified in the form which must be clicked within 1 hour (subject to exceptions), to perform the issuing of the ticket code, expired this period of time, the request will no longer be valid.
  • 4.3.2. Once clicked on the link, will be issued (if the operation is a success) a ticket code that will allow the facebook page paired with it to be published in home page through the use of the green form.
  • 4.3.3. The amount of projection time in the issued ticket code will be established the moment of issuing according to a probability criteria. On the basis of this criteria, once the issuing procedure has been completed, will be assigned a projection duration which will range from 1 hour (highest probability) to 6 hours (lowest probability).
  • 4.3.4. Once the ticket code delivery operation has been completed, a message will be sent to the email box used for the request, containing the ticket code and other useful data.
  • 4.3.5. Once a ticket code request has been sent, the mailbox just used cannot be reused for another ticket code request within 30 minutes (subject to exceptions).
• 4.4. For each month can be issued a certain amount of ticket codes (for a single facebook page and for the month in total), once this amount has been exhausted, will not be possible to issue further tickets for the concerned month. This quantity will be reset at the beginning of each new month.
• 4.5. A ticket code will be judged valid if:
  • 4.5.1. Effectively issued and present in the system.
  • 4.5.2. Paired with a valid and suitable facebook page (see 3.6 and 3.9) and not subject to any measure of exclusion from the site activity (see point 3.7).
  • 4.5.3. Used before its expiration date.

5. FUNCTIONING OF THE BLUE FORM IN HOME PAGE FOR A GIVEN ROOM

• 5.1. By entering a facebook page web address in the blue form, is possible to start a publication in home page for the relative facebook page for a certain period of time. Once a publication has been started, based on the expected duration, an interval will be calculated consisting of two timestamp for the start and end of the publication, within which the flow of the time for the publication started will be counted.
• 5.2. The terms of use of blue form for a given room are the following:
  • 5.2.1. The room must be active.
  • 5.2.2. The room must be free from other publications started by the blue form or by the green form.
  • 5.2.3. The web address of the facebook page of which you want to start a publication must be an address relating to a valid and suitable facebook page (see 3.6 and 3.9).
  • 5.2.4. The facebook page of which you want to start a publication, must not be published at the same time in any other room of the stage.
  • 5.2.5. The facebook page of which you want to start a publication, must not be candidate (through a ticket code paired with it) at the same time in any session365.
• 5.3. The standard duration of a publication started by blue form will be 1 hour (subject to exceptions).
• 5.4. The end of a publication started by blue form for a given room can occur:
  • 5.4.1. By natural expiry of the publication due to the exhaustion of the time available.
  • 5.4.2. If a publication of any facebook page would be started in the same room using the green form. In this case the publication previously started by the blue form would be terminated and replaced by the one just started by the green form.
  • 5.4.3. If for the same facebook page would be started a new publication in any room using the green form. In this case the publication previously started by the blue form would be terminated and replaced by the one just started by the green form.
  • 5.4.4. For technical reasons.
  • 5.4.5. By intervention of the site owner (see 3.7).

6. FUNCTIONING OF THE GREEN FORM IN THE ROOMS STATUS AREA FOR A GIVEN ROOM

• 6.1. Using a ticket code in the green form, is possible to start a publication in home page for the facebook page paired with the code for a certain period of time. Once a publication has been started, based on the duration contained by the ticket code, an interval consisting of two timestamp of start and end publication will be calculated, within which the flow of time of the started publication will be counted.
• 6.2. For a given room the functionality of the green form will be available on condition that meets the following criteria:
  • 6.2.1. The room must be active.
  • 6.2.2. The room must be free from other publications initiated by the blue form or by the green form.
  • 6.2.3. The ticket code must be a valid code (see 4.5)
  • 6.2.4. The ticket code must be related to a facebook page that is not published at the same time in another publication in progress previously started by the green form.
  • 6.2.5. The ticket code must be related to a facebook page that is not candidate at the same time (through the same ticket code or through another ticket code paired with it) in any session365 in progress.
• 6.3. The standard duration of a pubblication started by green form will depend by amount of time contained in the ticket code used to start the publication. This quantity can range from a minimum of 1 hour to a maximum of 6 hours (subject to exceptions).
• 6.4. The end of a publication started by the green form for a given room can take place:
  • 6.4.1. By natural expiry of the publication due to the exhaustion of the time available in the ticket code.
  • 6.4.2. For technical reasons.
  • 6.4.3. By intervention of the site owner (see 3.7).

7. PUBLICATION OF A FACEBOOK PAGE BY GREEN FORM AND SESSION365

• 7.1. For the next 365 seconds after the end (due to natural expiration) of a publication started by the green form, will be active a mechanism called "session365". Through this mechanism will be possible to candidate one or more different facebook pages at the same time to the next projection in the room through a valid ticket code (see 4.5). At the end of 365 seconds, if there are one or more candidate tickets, the one that will have the highest priority and so will be ranked in first position, will start the publication of the paired facebook page.
• 7.2. The ranking of the facebook pages at the end of a session365 will be decided considering the positioning of the related ticket codes candidate in the session365, according to the criteria listed below in order of priority:
  • 7.2.1. 1) Amount of publication time in the candidate ticket code (priority in descending order, i.e. from the largest amount of time to the smallest amount of time).
  • 7.2.2. 2) On equal amount of publication time in the candidate ticket code, will be considered the candidacy timestamp of the candidate ticket code (priority in ascending order, i.e. from the timestamp with the smallest value to the timestamp with the largest value).
  • 7.2.3. 3) On equal candidacy timestamp of the candidate ticket code, will be considered the alphabetical order of the title of facebook page paired to the candidate ticket code (priority in ascending order, i.e. from "a" to "z" )
• 7.3. When a publication through the green form begins, a link will be activated in the room status area for the concerned room. By that link will be possible to access a further area that will allow you to consult a list with all the facebook pages related to the ticket codes previously candidates for the current publication. The facebook pages will be shown from the first classified facebook page (which will correspond to the one published currently) to the last classified facebook page, based on the priority obtained from the paired ticket codes (see 7.2).
• 7.4. This list will remain visible only for the duration of the publication in progress, if for any reason the publication would end it will no longer be available.
• 7.5. For a given room, after 365 seconds have elapsed, a session365 can end in the following ways:
  • 7.5.1. There is a list with one or more candidate ticket codes, among these ticket codes the first classified (see 7.2) will start a publication for the paired facebook page.
  • 7.5.2. There is no candidate ticket code. In this case, since the session365 is ended, the first valid ticket code (see 4.5) that will be used in the green form will start a publication for the related facebook page.
• 7.6. If for a certain room, the end of a publication started by the green form does not occur due to the natural expiry of the time available in the ticket code, may be possible that no session365 will be started for this room. In this case the next publication of a facebook page will be started by the first valid ticket code (see 4.5) which will be used in the green form.

8. FUNCTIONING OF MONTHLY TOP20 RANKING IN MONTHLY TOP20 AREA

• 8.1. Each month a list of the top 20 facebook pages by amount of time spent in publications in home page will be shown in the monthly top20 area. The ranking will be updated during the course of the month, adding for each facebook page, the duration of each publication started by the blue form and by the green form.
• 8.2. As soon as a publication through a blue or green form will be launched for a facebook page, the entire duration expected for the publication (i.e. the amount of time contained in the interval of the timestamp of start and end of publication) will be immediately added to the relative total duration of the other publications launched in the current month for the same facebook page.
• 8.3. If for an ongoing publication some variations in the duration initially counted at the start of the publication should occur (i.e. in the original start/end timestamp), these variations would be integrated into the total count of the publication time of the related facebook page, eventually also making changes to its positioning in top20.
• 8.4. For publications started in a given month, but whose duration must exceeds the end of that month, the amount of time actually counted for the monthly top20 will be limited only to the part included in the month within which the publication was originally started, all the publication time that exceeds this month will not be counted.
• 8.5. The monthly positioning of a facebook page will be established for each month based on the criteria listed below in order of priority:
  • 8.5.1. 1) Total amount of publication time in the concerned month (priority in descending order, i.e. from largest amount of time to smallest amount of time).
  • 8.5.2. 2) On equal amount of total publication time in the month in question, will be considered the timestamp of the start of the first publication of the facebook page in the concerned month (priority in ascending order, i.e. from the timestamp with the smallest value to the timestamp with the largest value).
  • 8.5.3. 3) On equal timestamp of the start of the first publication of the facebook page in the concerned month, will be considered the alphabetical order of the title of the facebook page (priority in ascending order, i.e. from "a" to "z").
• 8.6. Each time the month changes, the ranking will be reset and all will restart with the publication counts for the new month.

9. FINAL ISSUES AND ACCEPTANCE OF THE TERMS OF SERVICE BY THE USER

• 9.1. Date and time, as well as any temporal reference related to them is always to be intended in compliance with UTC standard ("Coordinated Universal Time").
• 9.2. The PageMainStage trademark, as well as the entire site consisting of textual elements, graphic elements, software code elements, is copyright of the site owner. Trademarks, logos, textual elements, graphic elements, software code elements, belonging to third-party resources integrated into the site are copyright of their respective owners.
• 9.3. The terms of service on this page are subject to Italian law. In the event of any discrepancies between the Italian version and the version in other languages of the text shown on this page, the Italian version will always be the prevailing one.
• 9.4. Consent formula, having acquired the above information, browsing and/or using this site, I declare that I have read the terms of use of this page in full and accept them in full. These terms of use may suffer changes over time without notice, being aware of it, I declare to stay up to date on any changes made, committing myself to consult this page regularly. If I do not accept the terms of use on this page, or any updates, I will stop using this site.
• 9.5. Last update: 26 September 2020 - 15:48 (UTC)