Privacy Policy
QueueRing (the “Service”) sends notifications to Android devices using HTTP requests. This policy explains the information the Service handles and how it is used.
Information We Collect and Use
The Service does not require an account or ask you to register your name, address, phone number, or similar information. When you register a device to receive notifications, the Service handles information that identifies the device, the Queue ID that specifies its destination, and the Push Token used to send notifications.
The Service also handles usage information and temporary identifiers to verify devices, prevent misuse, limit usage, and operate the Service.
Notification Content
When sending a notification, the Service processes its title and body for delivery and sends them to Expo Push Service together with delivery information such as the Push Token. The Service does not store the title or body as notification history in its own delivery records, and it does not provide a feature for viewing notification history. Records such as request acceptance and delivery status are retained to the extent needed to operate the Service.
How We Use Information
- Registering and verifying devices and delivering notifications
- Managing notification destinations using Queue IDs
- Operating the Service, including preventing misuse, limiting usage, and responding to incidents
- Checking notification acceptance and delivery status
Retention Periods
Records about notification acceptance and delivery status become eligible for routine automatic deletion more than 30 days after acceptance.
Device registration information that has not been used for an extended period becomes inactive more than 180 days after its last registration, reactivation, or notification. It becomes eligible for routine automatic deletion more than 90 days after that. Revoked device registration information also becomes eligible for deletion more than 90 days after revocation. For existing information whose revocation time cannot be determined, the last update time is used as the reference point.
The periods described here indicate when Service data becomes eligible for automatic deletion. We do not guarantee deletion exactly at the end of a period, as timing may depend on processing status and infrastructure circumstances.
Temporary information used for device verification or misuse prevention is retained for the period needed for that purpose and then becomes eligible for automatic deletion. Short-term information used for rate limits becomes eligible for deletion after the applicable limit period ends; monthly usage information becomes eligible after the relevant month ends.
Third-Party Services
The Service uses Expo Push Service to deliver notifications to Android devices. Information needed for delivery, including Push Tokens and notification titles and bodies, is sent to Expo Push Service.
The Service uses Cloudflare for its infrastructure and operation. Cloudflare may handle technical information and logs in connection with providing the Service. Cloudflare manages retention and deletion of its data separately from the Service’s automatic deletion, and that data may not be deleted at the same time. Please refer to Cloudflare’s policies for details.
Contact
For inquiries about this policy or the Service, contact Tryel Works at info@queuering.org.