Security and data
What Loop31 keeps, where, who can see it, and how it goes away. Plain facts only; where we haven’t done something, this page says so. The full detail is in the privacy policy.
The short version
- We never hold your customer list. Loop31 doesn’t ask for, import or read your customers’ names, numbers or deals, and it doesn’t connect to a CRM or DMS.
- One place, in the United States. Everything is kept in one Supabase project, on Amazon Web Services in Northern Virginia.
- Managers see what each person was told they’d see, word for word, before they joined. Nothing else.
- No passwords. People sign in with a code sent to their email, and Loop31 never asks for a Facebook or Instagram password.
- Deleting is real. Delete an account in the app and everything we hold for it goes.
Your customers’ information
Loop31 posts to each salesperson’s own friends and followers, so it has no reason to know your customers, and it doesn’t.
- No customer list, CRM, DMS or deal data comes into Loop31, and there is no way to upload one.
- The only words from a customer are a review a salesperson types in themselves, with the customer’s OK to share: the words, the name the customer wants shown, and the date. The salesperson can delete it any time.
- For a dealership that connects its website, Loop31’s server reads the cars the store publishes each night: the VIN, year, make, model, trim, mileage, condition, the price shown, the page’s address and up to three photos. It honors the site’s robots.txt, never keeps a page’s text, and never reads anything about a customer.
- Loop31 reads only a website the person giving it confirms is theirs to give, and never social networks, marketplaces or listing sites. If your website was given to us without your OK, write to support@loop31.com and we’ll stop reading it and delete what we got from it (terms).
What we keep, and where
Everything lives in one project on Supabase, in the United States (Amazon Web Services, Northern Virginia): the database, the sign-in service, private storage for photos, the small server programs the app talks to, and the logs. Supabase works for us under its data processing terms and doesn’t use the data for anything of its own.
| What | Kept until |
|---|---|
| Each person’s email, for signing in | They delete their account |
| Name and business details (work phone, brokerage or dealership, license state, social handles) | They delete their account |
| Posts, captions, the schedule, and what they approved | They delete the post or their account |
| Photos and videos, in private storage, with location data taken out before upload | They delete the post or their account |
| The check record: which checks ran on each shared post and what they flagged, as names and levels, never words | With the post |
| A manager’s reminders: who sent it, about which post, and when | 35 days |
| A dealership’s website address, and the cars read from it | A year after a car leaves the website, or the team ends |
| Server logs (never caption text or anything typed) | 30 days |
| Backups, if turned on | 30 days |
We never sell data, show ads, or track anyone across other apps and sites.
Who can see what
| Who | What they can see |
|---|---|
| Each person | Everything of their own. |
| Their team’s owner and admins | From the day the person joined with a seat: their name and that their seat is paid; which Loops are on; each post that went out, with its date and caption (captions for 30 days) and what the checks flagged; how many posts they marked posted this week and this month, of those planned, and the 3 months before; their last post and weeks in a row. An owner or admin can send one reminder a day, three a week at most, when a post is due today. |
| Loop31 staff | For support, billing or a deletion request, a few staff can look up an account by its exact email: counts, dates, the plan, the team, and the writing-help answer. Never the person’s name, captions or photos. Every lookup is recorded. |
| Other teams, other people | Nothing. |
Where the fences are. These limits are set in the database itself, on every table (Postgres row-level security), not only in the app. Automated tests check each “no” before every release: for example, that a manager can’t read a person’s drafts, a person without a seat, or another team’s people.
What managers never see
- drafts, or posts a person skipped
- their photos
- their own listings, or vehicles they’ve added (a brokerage’s managers see how many listings an agent added from the brokerage’s website, never which; a dealership’s managers see counts of the cars offered and claimed)
- their phone number or setup answers
- anyone who pays for Loop31 on their own, or a person whose seat was taken back (their rows leave the manager’s view at once)
- their Facebook or Instagram: Loop31 can’t see them
Before anyone joins a team, the app shows them this, word for word, with the team’s name:
“Fall Creek Auto will see your name, that your seat is paid, which Loops are on, and the posts that go out from today on, with their dates and captions. They can send you one reminder a day when a post is due. They never see your drafts, photos, your own listings, vehicles, or anything you haven’t posted.”
Passwords and social accounts
- No passwords. The app and the team portal sign in with a 6-digit code sent to the person’s email. A code works for 10 minutes.
- No social logins. Loop31 never asks for a Facebook, Instagram or TikTok password and never posts to a personal profile. When someone taps Share, the app hands the post to that app on their own phone.
The outside companies
| Who | What they get |
|---|---|
| Supabase | Hosts everything above. |
| Resend | Sends the sign-in codes and the Monday email to managers (names and counts, never captions or photos). |
| OpenAI and Anthropic | Caption text, and only if the person said yes to writing help in the app (for the “Other” line of work, also the words of their own business website, if they give it). Never a name, phone, email, photo, customer review or account ID. Neither trains its models on it. |
| Pixabay | The words of a photo search, sent through our server. The photos then load onto the phone from Pixabay, so Pixabay sees the phone’s IP address. |
| NHTSA | The VINs of cars read from a dealership’s website, to confirm the year, make and model. |
| Apple | Delivers the app and sends us crash reports. |
Exactly what goes to each one, and when, is in the privacy policy, under “Who we share it with”.
Deleting
- A person deletes their account in the app (Me, then Delete account). Everything we hold for them goes, their sign-in last. Backups roll off within 30 days.
- A manager takes a seat back in the portal. That person’s posts and counts leave the manager’s view at once; their own account stays theirs.
- Anyone who can’t open the app, or a customer whose review was shared, can write to support@loop31.com and we remove the data.
What we don’t have
- No security certification, such as SOC 2 or ISO 27001. Loop31 is a small company in beta, and this page says what it does instead.
- No single sign-on with your company’s accounts, and no Android app yet.
If your group reviews vendors, send your questions to support@loop31.com.