Privacy Policy
EggMatic (“EggMatic”, “we”, “us”) is a private workspace at app.eggmatic.net where ad teams manage creatives, ad copy and client approvals. This policy explains what information the service handles, why, and the choices you have.
1. Who this applies to
- Team members: people an EggMatic administrator has invited to sign in.
- Client reviewers: people who open a private review link to approve work or request changes. They don’t sign in.
2. Information we collect
Account information
When a team member signs in with Google we receive their verified email address, which we match against the team list. We also keep what team members add to their own profile, such as a display name, job title and photo, and their notification settings.
Work content
Creatives (images, videos and other files), ad copy, briefs, comments, approvals, tasks, chat messages and attachments that people add to the workspace, along with a history of who did what and when.
Client review information
The decisions and comments a reviewer leaves on a review link, any name they enter, and when the link was opened.
Technical information
A sign-in session cookie, a one-way hash of the visitor’s IP address (used only to limit repeated sign-in attempts), and standard server logs kept for security and troubleshooting.
3. Information from Google
EggMatic uses Google APIs only for the purposes below, and only after the relevant person grants access.
- Google Sign-In (
openid,email,profile): to confirm who is signing in. We store the verified email address only, to match it to the team list. - Google Drive (
drive.file): when an administrator connects a Google Drive account, EggMatic stores the team’s uploaded creatives in an “EggMatic Creatives” folder and database backups in an “EggMatic Backups” folder in that Drive. With this permission EggMatic can only see and change files and folders it created itself, not anything else in the Drive. - Google Drive, read-only (
drive.readonly, optional): only if an administrator turns on importing from an existing Drive folder. EggMatic then reads the files in the folders the administrator chooses, to add them to the workspace. It never edits or deletes those files. - Gmail (
gmail.send, optional): only if an administrator sets up sending through a Gmail mailbox. EggMatic then sends notification and review emails from that mailbox. It doesn’t read the mailbox.
EggMatic’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
We use Google user data only to provide the features described above. We don’t sell it, use it for advertising, or use it to train AI or machine-learning models. People don’t read it, except with your permission, when needed for security or to fix a problem you reported, or when the law requires it.
You can withdraw EggMatic’s access to your Google account at any time at myaccount.google.com/permissions. Administrators can also disconnect Google Drive in EggMatic’s Settings.
4. Other services the workspace can connect
An administrator may choose to connect these. Each one is off until it’s set up.
- Slack: short activity messages (for example “new creative uploaded”) are posted to a channel the team chooses.
- Meta Ads: read-only ad performance figures for the team’s client ad accounts, shown in reports.
- Email (SMTP): notification and review emails sent through the email provider the team sets up.
5. How we use information
- To run the workspace: sign people in, store and show work, move it through review, and record its history.
- To send the notifications people have asked for, in the app, by email or in Slack.
- To keep the service secure, prevent abuse, make backups and fix problems.
We don’t use anyone’s information for advertising, and we don’t sell or rent it.
6. Who we share it with
We share information only as needed to run the service:
- Hosting: the service runs on servers we rent from Oracle Cloud Infrastructure.
- Google: for sign-in, and Drive storage when it’s connected.
- Slack, Meta or an email provider: only if an administrator connects them, and only what each feature needs.
- Client reviewers: see only the work the team chooses to send to their review link.
- The law: when we must comply with a legal obligation, or to protect people’s safety or the service.
7. Storage and security
- All traffic uses HTTPS. The workspace database is stored on our server and is not publicly accessible.
- Connection secrets (such as the Drive connection and Slack or Meta tokens) are encrypted in the database.
- The database is backed up every 4 hours. The last 7 copies are kept on the server, and copies are kept in the connected Google Drive for 30 days.
- Review links contain a long random code and can be given an end date.
No system is perfectly secure, but we work to protect information and will notify affected people if a breach requires it.
8. How long we keep it
We keep workspace content while the workspace is in use. When an administrator deletes an item, a client or a team member’s access, it’s removed from the live system, and then from backups as they expire (within about 30 days). Server logs are kept for a limited time for security.
9. Cookies
EggMatic uses only the cookies it needs to work: a session cookie that keeps you signed in, and a short-lived cookie that protects the Google sign-in step. Your browser also stores display preferences, such as the theme and sidebar width. We don’t use analytics or advertising cookies.
10. Your choices and rights
- Team members can view and edit their profile in Settings.
- You can ask for a copy of your personal information, ask us to correct or delete it, or object to how it’s used, by writing to [email protected]. Depending on where you live you may have further rights under local law, including the right to complain to a data-protection authority.
- You can withdraw Google access at any time, as described in section 3.
11. Children
EggMatic is a business tool and isn’t meant for anyone under 16. We don’t knowingly collect children’s information.
12. Changes to this policy
If we change this policy we’ll update the date at the top. If a change is significant, we’ll tell team members in the app before it takes effect.
13. Contact
Questions or requests about privacy: [email protected].