tagme is built to tag you in photos, not to track, profile or monetise you. Here is exactly what we collect and why.
tagme is operated by tagme LLC, an Indiana limited liability company ("we," "us," or "our"), covering the tagme mobile app and the website at plstag.me. For any privacy questions, reach us at [email protected].
By creating an account you agree to this policy. If you don't agree, please don't use the service.
tagme is for users aged 13 and older. We don't knowingly collect data from anyone under 13. If you think a child under 13 has created an account, email us and we'll delete it promptly.
| Data | Details |
|---|---|
| Account info | Username, email, bcrypt-hashed password, optional display name and bio |
| Phone number (optional) | Only if you add one and tick the SMS consent box. Used for verification codes and account notifications. See Section 6 |
| Device contacts (optional) | Names and phone numbers from your contact list, only if you choose to share them. See Section 6 |
| People you tag who aren't on tagme | A name and phone number you save to a face in a group photo or your own post. Only you can see it. See Section 6 |
| Photos | Photos you upload to groups or set as a profile picture |
| Biometric / face data | Mathematical face embeddings derived from uploaded photos via AWS Rekognition. See Section 5 |
| Server logs | IP address, device type, pages accessed, timestamps. Retained 90 days |
| Signup location | The IP address you created your account from and an approximate location based on it (city, region and country, never precise location). Used only for security and to stop abuse and fake accounts. Kept while your account exists and deleted with it. Never sold or used for marketing |
| Push token | Expo push token if you enable notifications |
We don't use your data for advertising. We don't sell your personal information.
If you're an Illinois resident, completing signup and consenting to face enrollment constitutes the written release required under the Illinois Biometric Information Privacy Act (740 ILCS 14). You may revoke consent and request deletion of your biometric data at any time by deleting your account or emailing [email protected].
What it is: a numeric vector ("face embedding") that represents your facial geometry, generated by AWS Rekognition from photos you upload. We don't store raw pixel data as biometric data, only the vector.
Why: to automatically identify and tag you in photos uploaded to your groups.
Who can auto-tag you: you are only auto-tagged by people within your own network on tagme: members of groups you have joined, and your friends. You are never auto-tagged by the general public or by all tagme users. Because your face is only enrolled after you consent, and because tag suggestions must be confirmed by you before they appear, you retain control over who on tagme can identify you.
Retention: kept for as long as your account exists. Deleted from AWS Rekognition within 30 days of account deletion.
No sale: we don't sell, lease, trade, or otherwise profit from biometric data.
Processor: AWS Rekognition (Amazon Web Services) processes face data on our behalf under a data processing agreement. AWS doesn't use your data to train its own models. See the AWS Privacy Notice.
Security: face embeddings are stored in an AWS Rekognition collection secured by IAM access controls. They are not stored on our server or in our database beyond the reference ID.
Your phone number: adding a phone number to your tagme account is optional. You can add one when you sign up or later in Settings, and remove it there any time. If you add one, we use it to confirm that you own it and to send you account notifications. We don't use your phone number for marketing, and we don't sell it.
When you enter a phone number on the tagme sign-up screen, or add one later in Settings, on the web or in the iOS app, an unchecked box appears. It reads: "I agree to receive non-marketing text messages from tagme at this number, including one-time verification codes and account notifications. Message frequency varies. Msg & data rates may apply. Reply STOP to opt out, HELP for help. See our Terms of Service and Privacy Policy." We only text you after you tick that box yourself and tap "Text me a code."
Texts tagme sends:
We never send marketing or promotional texts. Message frequency varies. Message and data rates may apply. Reply STOP to any tagme text to opt out, or HELP for help. You can also email [email protected]. Carriers are not liable for delayed or undelivered messages.
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.
Contact-based tagging: if you choose to share your device contacts with tagme, we use the names and phone numbers in your contact list only to (a) help you find friends already on tagme, (b) tell you when someone in your contacts joins tagme later, and (c) let you tag an unidentified face in a group photo with a contact who isn't on tagme yet. Sharing your contacts is optional. You can decline the permission prompt or turn it off later in your device settings, and your account keeps working either way.
What we keep from a contacts match: when you share your contacts, we compare the phone numbers against numbers that tagme users have verified on their own accounts, and we keep only the account IDs of the people who matched. For numbers that don't belong to anyone on tagme yet, we keep a one-way keyed hash of each number (a scrambled code made with a secret key, which can't be turned back into the number without that key), never the number itself, and never the contact's name. If someone later verifies one of those numbers on a tagme account, we match the hash, tell you they joined, and delete the hash. Hashes are replaced each time you share your contacts again, so a number you remove stops being checked. While contacts access is on, the app refreshes this about once a week. We keep those matches so the people you already know keep appearing in your friend suggestions after the moment you shared contacts, instead of only once. These suggestions are shown to you alone: the person who matched is never told that they appear in someone's contacts. You can clear them at any time in the app under Invite friends ("Stop suggesting them"), which deletes every match and every hash stored for your account, and both are deleted automatically if you delete your account.
Invite links and codes: if you sign up through someone's invite link, or type their code when you sign up, we record that they invited you. They can see your name, profile picture and when you joined in a list of people who joined from their link. If they're a TagMe Student Ambassador, they can also see whether your account counts toward their rewards, which only depends on whether you've uploaded a photo and have had your account for 7 days. They never see your photos through this. We use it to work out what ambassadors are paid, and it's deleted with your account.
Tagging someone who isn't on tagme: if a face in a group photo, or in a photo you post, belongs to someone who isn't on tagme, you can save their name and phone number to that face. Only you can see what you save. When you save a number, you can also choose to have tagme send that person one text letting them know they were tagged. Before it's sent, you have to tick a box confirming that you know this person, that you have the right to share their number, and that tagme will send them one text on your behalf. The text reads: "tagme: You've been tagged in a photo! See it by downloading the app: https://plstag.me/app. Reply STOP to opt out. Msg&data rates may apply."
Limits on tag notices:
If you got a text from tagme and don't have an account: reply STOP and we'll never text you again. You can also email [email protected] to have your number deleted from our systems.
Retention: your own phone number is kept while your account exists and deleted within 30 days of account deletion. A name and number you save to a face stays private to your account until you remove it, the face, group or post is deleted, or you delete your account. So that nobody gets a tag notice twice and opt-outs are respected, we keep a one-way hash of each number we've sent a tag notice to, not the number itself.
Photos you upload are stored on our server and visible to members of the group you upload to. They are not publicly accessible by default. Deleting a photo or your account removes the photo, all derivatives (thumbnails, medium sizes), and any linked face embeddings from our systems.
| Party | Role | Data shared |
|---|---|---|
| AWS Rekognition | Face recognition processor | Face images and embeddings |
| Oracle Cloud | Hosting | All data stored on their servers |
| Cloudflare | CDN / DNS | Network traffic in transit |
| Twilio | Delivers the texts described in Section 6 on our behalf | The recipient's phone number and the message text, only to deliver that message |
| Legal | Compliance | Disclosed only if required by law or court order |
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.
No advertisers. No data brokers. No analytics SDKs.
Email [email protected] or use in-app controls to:
We'll respond within 30 days.
Legal basis: we process personal data on the basis of (a) contract performance, to provide the service you signed up for; and (b) consent, for biometric data, which you may withdraw at any time.
Data transfers: your data is stored and processed in the United States. By using the service, you acknowledge transfer to the US, which may not have equivalent protections to those in your country.
Your rights include access, rectification, erasure, restriction, portability, and the right to object. You also have the right to lodge a complaint with your local supervisory authority. Contact us at [email protected].
All data in transit is encrypted via HTTPS / TLS through Cloudflare. Passwords are bcrypt-hashed and never stored in plaintext. Biometric data is access-controlled via AWS IAM. No method of storage or transmission is 100% secure. We can't guarantee absolute security, but we take it seriously.
The website uses no tracking cookies. The mobile app stores your login token in device secure storage. We don't use third-party analytics or advertising SDKs.
If we make material changes, especially to how we handle biometric data, we'll notify you via email or an in-app notice before the change takes effect. The date at the top of this page reflects the most recent update.
Email us any time at [email protected]. We actually read it.