Your information
Privacy notice
Last updated 7 September 2026
Contentfeed is in development. This notice covers this website, enquiries and invited workspace testing. Public publisher registration and paid subscriptions are not open.
Who is responsible
MB “Daugiau intelekto”, company code 306430321, at Žygio g. 92-62, Vilnius, Lithuania, is responsible for the personal information covered by this notice. Contact us at nerijus.tilvikas@gmail.com.
A publisher that receives articles through our API is responsible for its own website and reader data. This notice does not cover that publisher’s tracking, subscriptions or other services.
When you visit or contact us
Our hosting provider, Vercel, processes technical request information needed to serve and protect the website, such as IP address, requested URL, browser information and request time. We use this information to operate the site, diagnose failures and prevent abuse, based on our legitimate interests in a secure, reliable service.
If you email us, we receive your address, message and any information you choose to include. We use it to answer your enquiry and, where relevant, take steps you request before an agreement. For business representatives, we also rely on our legitimate interest in responding to business enquiries. Our current contact mailbox is hosted by Google. Please do not send passwords, API keys or unnecessary sensitive information.
We do not automatically add people who contact us to a mailing list. This website does not currently use advertising pixels, session recording or an application analytics service.
Invited workspace testing
Where workspace access is enabled, Google sign-in and Neon Auth identify you. We receive your verified email and account identifier. The identity service also handles the profile, session and authentication information needed for sign-in. Google has its own privacy notice for its services.
We record your organisation membership and role to control access. Editorial profiles, manuscript edits, coverage selections and approval decisions are associated with the person who made them. Other authorised members of that organisation can see relevant work and its history, including the saving user’s email.
API access records include key labels, a hash and identifying suffix, creation and revocation details, last-use time and request counts. We use these records to authenticate integrations, enforce limits and investigate problems. The full key is shown when created; keep it on your server. Copying it places it in your device’s clipboard.
These activities support the testing arrangement and our legitimate interests in access control, editorial accountability and preventing misuse. Signing in alone does not grant access to an organisation. Do not place unrelated personal or sensitive information in profile instructions or manuscripts.
Cookies and AI processing
Workspace sign-in uses essential cookies for the session, sign-in challenge and a short-lived signed cache of identity and session information. These cookies support authentication; they are not advertising cookies. You can remove them in your browser, which may sign you out. Signing out clears local authentication cookies and attempts to revoke the remote session; it does not delete your account or editorial history.
Private drafting and review use OpenAI to process selected match facts or clearly labelled fictional examples, together with editorial instructions. Instructions and draft text can be sent for processing; free-text fields are not automatically anonymised. Our application does not send your login credentials or browsing history in these requests. Disabling response storage in an API request does not mean the provider retains no data.
Service providers and processing locations
We use Vercel for website hosting, Neon for the database and workspace identity service, Google for sign-in and the contact mailbox, and OpenAI for private drafting and review. Access is limited to the information needed for each service. We may also disclose information when legally required or necessary to protect people, investigate misuse or resolve a dispute.
Our application database is configured in Frankfurt. This does not mean all processing takes place in the European Economic Area: provider operations, support and infrastructure can involve other countries. Providers describe their processing in their applicable privacy notices and terms. You can contact us for information about locations and safeguards relevant to your data. Selecting a European database region does not establish those safeguards for every provider.
How long information is kept
We keep enquiry records while needed to answer the enquiry, manage a resulting relationship or resolve a related dispute. Workspace records support access management and the history needed to explain edits, approvals and corrections. Relevant retention criteria include whether the enquiry remains open, access is still needed, a publication needs correction, a dispute is unresolved or a legal obligation applies. Ending a session or revoking access does not erase those records.
There is currently no self-service account-deletion function. Contact us to request deletion or restriction. Editorial audit records and backups need separate assessment: removing information from an active account does not necessarily remove every historical copy immediately. If information must be retained, we will explain the reason and the applicable period or criteria. Hosting and identity logs are also subject to provider retention arrangements.
Your rights
Depending on the circumstances, you can request access, correction, erasure, restriction or portability of your personal data, and object to processing based on legitimate interests. Where processing relies on consent, you can withdraw it without affecting earlier lawful processing. We do not use this website to make solely automated decisions about you that have legal or similarly significant effects.
Send a request to nerijus.tilvikas@gmail.com. We may need proportionate information to verify your identity. We will respond within the applicable legal deadline, normally one month, and explain any permitted extension or refusal. You can complain to the Lithuanian State Data Protection Inspectorate or another competent supervisory authority.
We will update this notice as the service changes and provide additional information before introducing materially different uses of personal data.