Website visits
The public site hosts product information and guides. Netlify may process IP addresses, browser information, and request logs to deliver and secure the site. The site loads fonts from Google Fonts, which receives the network information needed to serve those files. The sample workspace uses demonstration posts.
Accounts and scheduled posts
When app features become available, PublishGrid will use the email and account information you provide to authenticate you and manage your account. Drafts, uploaded images, scheduled times, and publishing status are used to store, schedule, and deliver the posts you choose to publish. Netlify hosts the site and app infrastructure, Supabase provides authentication and storage, and Resend delivers service messages such as publishing and account connection alerts. Stripe handles checkout when purchases are available.
Connecting LinkedIn
PublishGrid will ask for your authorization before connecting to LinkedIn. When you connect or reconnect, PublishGrid will receive authorization credentials and the account identifier needed to connect your profile. When you schedule a post, PublishGrid will send the selected text and any attached image to LinkedIn at the scheduled time. PublishGrid will use the response to report the outcome to you. LinkedIn handles posts you publish under its privacy policy.
Disconnecting and deleting data
You can revoke authorization in your LinkedIn settings. When the app connection is available, you can also disconnect your profile from PublishGrid. To request access, correction, or deletion of your PublishGrid data, contact us through the company page below. On a deletion request or account closure, PublishGrid will remove LinkedIn data and authorization tokens collected through its integration unless a legal obligation requires retention. Posts already published on LinkedIn can be managed on LinkedIn.
Contact
For privacy questions or requests, contact PublishGrid on LinkedIn. Include enough information for us to identify the account or request. Keep passwords and authorization tokens out of your message.