Privacy Policy

Effective date: 2026-05-21 Last updated: 2026-07-28

This Privacy Policy explains how Radiusly ("Radiusly", "we", "us", or "our") collects, uses, shares, and protects information when you use the Radiusly mobile application, web application, and related services (collectively, the "Service").

Radiusly is operated by an individual sole proprietor based in Israel. By using the Service, you agree to the practices described below. If you do not agree, do not use the Service.

Questions or requests: [email protected].

1. Summary at a glance

• No accounts. We do not require an email, phone number, password, or sign-up. Your identity in each chat is a temporary name and emoji generated for that chat only.
• Precise location is required. The Service is location-gated: you must be within ~100 metres of a chat's pin to send messages. We process your device's GPS coordinates to enforce this.
• Messages are public within their chat. Anything you send is visible to other users in that chat and is stored on our servers.
• No advertising. No third-party analytics SDKs. No selling of personal data.
• Chats inactive for more than one year are automatically deleted, along with their messages.

2. Information we collect

We collect only what is necessary to operate the Service.

2.1 Information you provide

• Messages and chat names. The text content of messages you send, and the names of chats you create. This is user-generated content ("UGC").
• Location coordinates. When you create a chat, view nearby chats, or send a message, your device transmits latitude and longitude to our API.
• Reports and support correspondence. If you report content or contact support, we receive the message and any context you include.

2.2 Information collected automatically

• Ephemeral session identifiers. A random in-memory identifier used to maintain your WebSocket connection and tie your messages to your session. It is not linked to your real identity.
• Temporary display identity. A randomly-generated name and emoji icon assigned per chat. This is generated on the fly and is not derived from any personal information.
• Device push notification token (mobile only). If you grant notification permission, we store an Expo push token to deliver notifications.
• Technical/connection metadata. Standard server logs including IP address, user agent, timestamps, and request paths. Used for security, abuse prevention, and operational diagnostics.

2.3 Information we do not collect

• Names, email addresses, phone numbers, or government IDs.
• Contacts, photos, microphone, camera, or files from your device.
• Advertising identifiers (IDFA / AAID).
• Health, financial, or biometric data.

3. How we use information

We use the information above to:

• Operate the location-gated chat feature. Your coordinates are compared in-memory against the coordinates of the chat pin to determine whether you are within range. We do not build a movement history or profile from your coordinates.
• Persist chats and messages. Chat metadata and messages are stored in Amazon DynamoDB so other nearby users can read them and so the chat is available when participants return.
• Deliver real-time updates via WebSockets (Socket.io).
• Send push notifications that you have opted in to receive.
• Enforce our [[community-guidelines]] and [[terms-of-service]], including investigating reports and removing prohibited content.
• Secure the Service against abuse, spam, scraping, and attacks.
• Comply with legal obligations in Israel and other applicable jurisdictions.

We do not use your data for advertising, profiling, automated decision-making with legal effects, or training third-party AI models.

4. How information is shared

4.1 Within the Service

Messages you send and the chat name you create are visible to every other user in the same chat. The display name and emoji shown next to your messages are visible to other users in that chat. Anything you post should be treated as public.

Your precise device coordinates are not shared with other users. Only the coordinates of the chat pin (which you or another user set explicitly when creating the chat) are visible to others.

4.2 Service providers

We use the following processors, each bound by their own terms:

These providers process limited data strictly to perform their function on our behalf. Google may receive your approximate location and IP address when map tiles load; refer to the Google Privacy Policy.

4.3 Legal disclosure

We may disclose information to a government, court, or law enforcement authority where we are required to do so by Israeli law, by a valid legal process binding on us, or where we believe in good faith that disclosure is necessary to prevent imminent harm.

4.4 No sale or rental

We do not sell, rent, or trade personal data, and we do not "share" personal data for cross-context behavioural advertising.

5. Retention and deletion

• Messages and chats are stored for as long as the chat remains active. A chat with no activity for more than one year is automatically deleted on server start and as part of a daily cleanup, along with all of its messages.
• Server logs are retained for a rolling window not exceeding 90 days, then deleted or aggregated.
• Push notification tokens are deleted when they become invalid or when you uninstall the app.
• Support correspondence is kept only as long as needed to resolve your request, typically no more than 12 months.

Because the Service has no accounts, we cannot link a specific historical message to "you" after the fact. Deletion requests for individual messages should be made via the in-app report / delete controls (you can delete your own messages while your session is active), or by contacting [email protected] with sufficient information (chat name, approximate location, approximate time) for us to locate the content.

6. Security

We use industry-standard measures including TLS in transit, IAM-scoped access to data stores, network segmentation, and least-privilege deployment on AWS ECS Fargate. No method of transmission or storage is perfectly secure, and we cannot guarantee absolute security.

Because the Service is accountless and uses temporary display identities, the most effective privacy protection is your own behaviour: do not post information you would not be comfortable making public. Coordinates of a chat pin can reveal a real-world location.

7. Your rights

Depending on where you live, you may have rights to access, correct, delete, port, or restrict processing of your personal data, and to object to processing. These rights are limited where we hold no information that can be linked to you (which is generally the case for the Service).

To exercise any right, email [email protected]. We may need additional context to locate any data attributable to your session.

• Israel. Residents have rights under the Protection of Privacy Law, 5741-1981, including the right to inspect data held about them and to request correction. Complaints may also be filed with the Privacy Protection Authority (Rashut Hahaganah Al HaPratiyut).
• European Economic Area / United Kingdom. Where the GDPR or UK GDPR applies, our legal bases are (a) performance of the contract you enter into by using the Service, (b) our legitimate interests in operating, securing, and improving the Service, and (c) compliance with legal obligations. You may lodge a complaint with your local supervisory authority.
• California, USA. Residents have rights under the CCPA/CPRA. We do not sell or share personal information as defined by those laws.

8. Children

The Service is intended for adults and may not be used by anyone under 18. We do not knowingly collect data from minors. If you believe a minor has used the Service, contact [email protected] and we will delete relevant content promptly.

9. International transfers

The Service is operated from Israel and hosted primarily on AWS infrastructure in the United States. By using the Service you understand that your information may be transferred to, stored in, and processed in countries other than your own, including the United States, which may have different data protection laws than your jurisdiction.

10. Apple App Privacy disclosures

For transparency, the data we declare in App Store Connect maps to this Policy as follows:

11. Changes to this Policy

We may update this Policy from time to time. The "Last updated" date at the top reflects the most recent version. Material changes will be highlighted in-app or on the website prior to taking effect. Continued use of the Service after a change constitutes acceptance.

12. Contact

Radiusly Email: [email protected] Operator: Sole proprietor (individual), Israel