PingMe watches public posts on LinkedIn and Reddit for the keywords you choose and delivers each match, a ping, to your Discord server. Doing that means handling two kinds of personal data: yours, as the person running a workspace, and that of the people whose public posts match your keywords. This policy explains both, in plain terms.
It applies to the website pingme.so, the PingMe dashboard, the PingMe Discord bot and the early-access waitlist.
Contents
Table of Contents
1. Who We Are
The data controller is Anthony Decat EI, 6 rue d'Armaillé, 75017 Paris, France (SIREN 943 086 975). Full details are in the Legal Notice.
We have not appointed a data protection officer. For anything about your data, write to [email protected].
2. Data We Collect
We collect only what the product needs to run. Nothing below is bought from data brokers or enriched from other sources.
Waitlist
Your email address and which form on the site you used
A keyed hash of your IP address and your browser user agent, used only to rate-limit signups. The IP address itself is never stored.
Discord account
Your Discord user ID, username and avatar, obtained when you sign in with Discord
The list of Discord servers you manage, so you can pick where pings go
The Discord access and refresh tokens that let us read that list. They are stored encrypted and never shown to anyone, including us.
Workspace configuration
Your monitors: keywords, sources, subreddits, freshness tier, daily ping cap
Your destinations: the Discord server, channels and roles you chose, and the bot's permissions there
Pipeline stages, follow-up questions and message templates you write
Activity and billing records
Every ping delivered, with the Discord message it became, the outcome buttons pressed and which team member pressed them. This ledger is also the basis of your bill.
Each monitor run: when it ran, what it fetched, what it cost us, and any error
An activity log of what the system did in your workspace (deliveries, cap holds, failures)
Once billing is enabled: invoices and payment status. Card details will be handled by our payment processor and never reach our servers.
Technical data
Server logs from our hosting providers (IP address, request path, timestamp), kept for security and debugging
One session cookie, described in section 10
3. Data About Post Authors
When a public post matches one of your keywords, PingMe stores what it needs to show you the match and to avoid sending it twice: the post's text, its URL and date, and the author's public display name, profile URL and avatar as shown on the platform. If you move an author into your outreach pipeline, we also store the stage, the notes and follow-up answers your team adds, and which of your message templates you used.
We only fetch posts the platform makes public. We do not log in as you or as anyone else on LinkedIn or Reddit, we do not read private messages, and we do not send anything on those platforms on your behalf.
If you are a post author and would rather not appear in PingMe pings, write to [email protected] and we will remove your existing records and block your profile from future matches.
4. How We Use Data
Running the service: signing you in, checking your monitors on schedule, delivering pings to Discord, tracking outcomes and follow-ups
Billing: counting delivered pings and watched queries, applying the free allowance and your daily cap, issuing invoices
Cost control: measuring what each monitor costs us so we can adjust how often it runs
Support and reliability: reading the activity log and run history when something goes wrong
Early access: emailing you when your waitlist spot opens. We do not send marketing newsletters.
We do not sell personal data, use it for advertising, or use post content to train models.
5. Legal Basis
Contract (GDPR art. 6(1)(b)): your account, workspace configuration, pings and billing records exist to deliver the service you asked for.
Legitimate interest (art. 6(1)(f)): processing public posts and their authors' public profile details so that you can find conversations relevant to your business; security logging; cost measurement. We limit this to public content and to the minimum fields needed to show a match.
Legal obligation (art. 6(1)(c)): keeping accounting records once billing is enabled.
Consent (art. 6(1)(a)): the waitlist email. You can withdraw it at any time by asking us to delete your entry.
6. Who We Share Data With
We share data only with the providers that run PingMe, and only what each one needs:
Discord Inc. (United States): sign-in and delivery. Every ping is a message posted in your server, so Discord receives its content.
Apify Technologies s.r.o. (Czech Republic): the data collection platform that fetches public LinkedIn posts for your keywords. It receives your keywords, never your identity.
Reddit, Inc. (United States): Reddit posts are read through Reddit's public feeds.
Vercel Inc. (United States): hosts the website and dashboard.
Hetzner Online GmbH (Germany): hosts the database and the monitoring worker. This is where your data is stored at rest.
A payment processor, once billing is enabled. We will name it here before the first invoice.
Members of your Discord server see the pings delivered to it and the outreach pipeline you share with them. Who that is depends on your Discord permissions, not on us. We may also disclose data when the law requires it.
7. International Transfers
Your data is stored in the European Union. Discord and Vercel process some of it in the United States. Those transfers rely on the European Commission's adequacy decision for the EU-US Data Privacy Framework where the provider is certified, and on Standard Contractual Clauses otherwise.
8. Retention
Waitlist: until you are invited and create an account, or until you ask us to remove you.
Account and workspace data: for as long as your account exists. Deleted within 30 days of a deletion request or of closing your account.
Pings, contacts and outreach records: for as long as the workspace exists, so your team keeps its history. Deleted with the workspace.
Billing records: 10 years after the invoice, as French accounting law requires (article L.123-22 of the Commercial Code).
Activity and server logs: 12 months at most.
9. Security
All traffic is encrypted in transit (TLS)
Discord tokens and third-party API keys are encrypted at rest with AES-256-GCM, with the key held outside the database
The database is only reachable by our own services, never directly from the browser
Passwords are never involved: sign-in is delegated to Discord
Secrets and stack traces are kept out of the activity log
If a breach affects your data, we will tell you and the CNIL as the GDPR requires.
10. Cookies
PingMe sets one cookie, pingme_session, after you sign in. It keeps you logged in to the dashboard and nothing else. It is strictly necessary, so no consent banner is needed for it.
We use no analytics cookies, no advertising cookies and no third-party trackers. Your theme preference is kept in your browser's local storage and never leaves it.
11. Your Rights
Under the GDPR you can ask us to:
Access
Get a copy of the personal data we hold about you
Rectify
Correct data that is inaccurate or incomplete
Erase
Delete your data, subject to the retention above
Port
Receive your data in a machine-readable format
Object
Object to processing based on legitimate interest
Restrict
Pause processing while a request is examined
These rights apply whether you are a PingMe user or the author of a post that appeared in a ping. Write to [email protected]; we answer within one month. You can also lodge a complaint with the CNIL, the French supervisory authority, at cnil.fr.
12. Children
PingMe is a business tool and is not intended for anyone under 18. We do not knowingly collect data from children. If you believe a child has signed up, contact us and we will delete the account.
13. Changes to This Policy
When this policy changes, we update the date at the top of the page. If the change affects what we collect or who we share it with, we will also tell you by email or in the dashboard before it takes effect.
14. Contact
Questions, requests and complaints about personal data go to [email protected], or by post to Anthony Decat EI, 6 rue d'Armaillé, 75017 Paris, France.