How Markloop handles your information

Feedback submissions may include the reviewer name, comment text, page URL, page title, selected element label, DOM selector, click position, viewport size, browser language, platform, user agent, and a screenshot of the current viewport.

Dashboard access may include the user name, email address, login method, allowed domain, invited email status, workspace settings, issue comments, activity history, and audit events.

We use this information to display feedback in context, manage issue workflows, provide reviewer share links, secure dashboard access, troubleshoot the service, and improve product quality.

Markloop captures viewport screenshots so teams can understand exactly what a reviewer saw. Reviewers and site owners should avoid submitting sensitive personal, payment, health, or confidential information through feedback screenshots or comments.

Markloop uses an HttpOnly session cookie for dashboard authentication. Team member login is powered by Google sign-in, and administrator access uses a separate credential.

Markloop may use hosting, authentication, database, analytics, and infrastructure providers such as Vercel, Appwrite, and Google to operate the service. These providers process data only as needed to provide their services.

Feedback, screenshots, comments, projects, access settings, and audit records are retained while a workspace remains active or until they are deleted by an authorized user. Deleted records may remain in backups for a limited period.

Authorized workspace users can delete or archive feedback cards from the dashboard. For access, correction, or deletion requests, contact the workspace owner or Markloop support.

Markloop uses access controls, signed session cookies, owner-managed allowlists, and provider-level infrastructure safeguards. No online service can guarantee absolute security, but we work to limit access to authorized users.

Questions about this policy can be sent to anju.pranesh@gmail.com.