Awareverse · AwareTogether

Version 2026-10-11.1 · Effective 11 October 2026

Privacy Notice

Choose what to share and who receives it.

Who is responsible

Scott Allen trading as Awareverse is responsible for AwareTogether account and service data. Contact support@awareverse.co.uk for privacy questions, access, correction or deletion requests.

Account and agreements

We store your email, display name, a password hash, account creation time, email-verification status and records of the Terms, Privacy Notice and support acknowledgement versions and acceptance time. Passwords are hashed, not stored as readable account passwords. Sign-in tokens are stored on your device and as hashes on the server. Each phone has its own session.

Circles, chats and requests

We store circle names, ownership, memberships, message retention choices and hashed invitation codes. Your circle members see your display name; your account email is not included in member lists. Group messages go to members of the chosen circle. Private messages go to the chosen person with whom you share a circle.

Messages and delivery records wait in the Awareverse database until the required accounts and signed-in devices have collected them, or for up to 7 days under the default server settings. Chats are then saved on recipient devices. Support requests contain their type, your support instructions, time, status, optional location and records of who opened or acknowledged them. Requests are kept for up to 24 hours before scheduled cleanup. Do not include detailed health records; support instructions or messages may themselves reveal sensitive information.

Location is optional

We do not request location to create an account. If you separately choose location with a request, its coordinates and accuracy can be sent to the chosen circle. Live sharing stores your latest latitude, longitude, accuracy and captured/update times for each circle you share with. It updates while the app is open; stopping sharing removes the server position. Stale positions are removed after 12 hours by scheduled cleanup. Your own trail is stored only on your device for up to 7 days; the optional trail view shows the latest 24 hours. Recipients may see old positions until the app refreshes.

Email, notifications and maps

Verification, reset and account-security emails are sent from awaretogether@awareverse.co.uk through Awareverse's hosting mail service. Single-use verification tokens are stored as hashes for 24 hours and reset tokens for 30 minutes. Queued email bodies are encrypted in the database and removed after the sending server accepts them; failed jobs are discarded within a day or after five attempts. The mail provider and your recipient mail service process the messages and may retain mailbox or delivery records.

When Google Firebase Cloud Messaging is configured and you allow notifications, device push tokens and notification metadata pass through Google. Notifications contain IDs and event types, not message text or coordinates. Without configuration, closed-app notifications are unavailable. Firebase is not the chat-message database. Opening the map downloads OpenStreetMap tiles; the tile service receives your IP address and requests for the area shown. Normal device and browser software may process connection information.

Technical and test data

The server processes IP addresses for connections and uses keyed hashes of IP addresses and email addresses for rate limiting. Short limits are cleaned after about 10 minutes; email hourly limit records after 2 days. We record account-linked event type, time and whether an action was practice for test counts, kept for up to 14 days. Practice events do not include simulated message text or location; Practice mode works offline, with event reporting only when signed in and connected. This build contains no advertising SDK or third-party analytics SDK.

Why we process it

Account details, circles and delivery records are needed to provide the service you request. Our processing basis for core account and messaging functions is performance of our agreement with you. Security, rate limiting and limited test-event counts serve our legitimate interests in preventing misuse and improving reliability. Optional location sharing uses your consent; withdraw it by switching sharing off. Confirming you have read this notice is an acknowledgement, not blanket consent to all processing. We do not ask for medical diagnoses. Contact us before sharing sensitive health information if you need advice about this test.

Who can access it

The chosen recipients receive the messages and locations you share. Awareverse's hosting provider processes the database, website and mail. Authorised Awareverse administrators can maintain the service; the admin dashboard shows aggregate test counts rather than chats or coordinates, but the underlying database is not end-to-end encrypted. HTTPS protects data in transit. Google and OpenStreetMap process the limited data described above when those features are used. We do not sell personal data.

How long it stays

Account, membership and agreement records stay while your account exists. Sign-in sessions expire after 60 days without renewal; active sessions renew. Push-device entries unused for 60 days and push retries older than an hour are cleaned up. Invitations expire after 24 hours. Device chats follow your selected timer (1 hour, 24 hours, 7 days, 30 days, 90 days or until deleted), or the circle's setting. You can clear local chats and your trail. Scheduled cleanup runs periodically, so removal occurs at its next successful run and may be delayed during outages.

Hosting backups and access/mail logs are separate from the live database. Their precise retention and hosting locations need confirmation with our provider before wider release. Deletion from the live database does not immediately erase an existing backup or messages already copied by recipients. Providers such as Google may process data outside the UK. Contact us for the applicable provider locations and transfer safeguards; this test notice does not claim they have been independently verified.

Deleting an account

Settings → Delete my account removes your account and linked live database records, including sessions, device tokens, agreements, circles you own, memberships, your server messages, support requests and positions. It clears the local chat store on that device. Other people's saved chats, other devices' local copies, copied messages and provider logs/backups may remain. To request deletion without the app, use https://awareverse.co.uk/awaretogether/delete-account.html or email support@awareverse.co.uk from your account email. We verify your identity before processing a manual request.

Your rights

Depending on the processing basis, you may ask for access, correction, deletion, restriction, portability, object to legitimate-interest processing and withdraw consent. Contact support@awareverse.co.uk. You may complain to the UK Information Commissioner's Office at https://ico.org.uk/make-a-complaint/. We do not make automated decisions producing legal or similarly significant effects about you.

Children and changes

This initial test has no guardian-consent or child-account setup. Test with adult accounts and do not enter a child's sensitive information. A separate child flow and review are needed before child accounts are supported. The app records notice versions and dates, and asks you to review updated required versions.

© 2026 Scott Allen / Awareverse. All rights reserved. You may share a link to this notice.