Privacy policy

The workspace

milutin.dev is an internal workspace operated for an invited team. The workspace operator is responsible for membership, content, and server administration. The workspace administrator decides privacy, access, correction, and deletion requests.

This site publishes no public contact address, so there is no form or inbox here. Signed-in members can reach the administrator inside the workspace. Anyone else, including a person whose email was added to the member list without their knowledge, can ask any milutin.dev member to relay the request. Either route reaches the same administrator.

Google sign-in

We request only Google identity and email permissions. Google supplies an account identifier, email address, and email verification status. milutin.dev uses these to verify sign-in and bind an active local member to that Google identity. We store this identity connection, but do not retain Google access, refresh, or ID tokens after authentication. We do not import your Google profile name or photo or access your Gmail, Drive, contacts, or calendars. milutin.dev never receives your Google password.

Information stored in milutin.dev

Your membership includes the email, first and last name entered by the team or updated by you, active status, and creation and update times. Shared content includes posts, uploaded images and videos, filenames, authorship, editing ownership, and update times. Search indexes the title and body of stored posts.

Each post records a visit count and the latest visit time for each reader. Other members can see the post's total views, reader names, and latest visits. Member profiles show local names and authored posts. Saved posts are private to the member who saves them. Short-lived visit receipts prevent duplicate counting. Save receipts use request hashes and identifiers to prevent duplicate publication, including after a post is deleted; they contain no post text. Authentication records include sessions, expiry times, IP addresses, and browser user-agent information. Operational logs may include technical request and error information used to run and protect the service.

Time off

Time off records include requested dates, full-day or hourly duration, type, optional note, status, decisions, and the latest change attribution. We also store annual allowances, adjustments with explanations, holidays, and assigned approvers. Active members see approved availability, names, dates, and duration. Only the requester, their current assigned approvers, and the administrator can see pending plans, type, notes, balances, and decision details. Time off is not included in post search or sent to embedding services. Cancelled and rejected records remain stored; deleting a pending request removes that request.

Use, access, and hosting

Information is used to provide sign-in, enforce permissions, display and search team knowledge, show collaboration activity, and operate manual backups. Active members can read shared posts and attached files. The administrator can see the account management directory, manage access and export data. The server operator can access stored data while administering the service.

Application data and server-side backups are stored on a DigitalOcean server in New York, United States. The application does not sell information, use advertising analytics, or send post content to Google for sign-in. Google handles authentication under its own privacy policy. Embedded YouTube videos contact YouTube from your browser when their player loads, even before playback; external links can take you to other services with their own data practices.

Answering questions from posts needs an outside service. When the administrator configures one, the text of posts is sent to it so the workspace can be searched by meaning, and the service processes that text under its own terms; the configured provider is OpenRouter, which routes the text to the embedding model the administrator selects, unless the administrator names a different provider. While no such service is configured, post text stays on the server and is never sent anywhere. Attached files are never sent either way, and member names, email addresses and activity are never part of what is sent.

Cookies and local preferences

Essential cookies support sign-in and your session. milutin.dev also stores your light/dark theme and per-member page-width preferences in your browser. It does not use advertising or analytics cookies. Google and YouTube may use their own cookies when you interact with those services.

Retention and your choices

milutin.dev stores the latest version of a post, without revision history. The author or administrator can permanently delete a post, including its bookmarks and visits. Membership records and contributions remain stored until the operator removes them; deactivating a member removes access but does not erase their contributions. Signing out invalidates the current session. You can update your local name in My profile and ask the operator to correct or delete other information. There is no self-service account deletion. You can also disconnect this application in your Google account, which does not itself delete data already stored in milutin.dev.

Backups are created or imported only when the administrator requests them. They contain member names and emails, posts, media, private bookmarks, retained activity, and all Time off records, and remain until deleted. The administrator can download copies outside the server. Deleting live data does not automatically remove it from existing backup copies, and restoring a backup can bring that data back. Coordinate deletion requests and retained copies with the operator.