Ulika
Docs

Privacy Policy

This is Ulika's comprehensive privacy notice (aviso de privacidad integral) under Mexico's Ley Federal de Protección de Datos Personales en Posesión de los Particulares. It explains what personal data Ulika handles, why, and what you can do about it.

Last updated: November 4, 2026

On this page

  1. 1. Who is responsible for your data
  2. 2. Personal data we collect
  3. 3. What we use it for
  4. 4. Processors and transfers
  5. 5. Cookies and similar technologies
  6. 6. Security and retention
  7. 7. Your rights (ARCO), consent and limiting use
  8. 8. Changes to this notice
  9. 9. Contact

Who is responsible for your data

The controller (responsable) of your personal data is Mauricio Cervera Pagaza, an individual doing business as “Ulika”, in Mexico. You can reach the controller for any matter in this notice, including legal notices and data requests, at legal@ulika.co. That email is also the address where we receive requests and notices related to your personal data.

This notice covers the Ulika website and app at ulika.co, the Ulika command line, and the Ulika GitHub App. It does not cover the websites you edit with Ulika: for the visitors of those sites, you decide what is collected and you are the one who owes them a privacy notice.

Personal data we collect

We collect the following, from you directly or from the services you connect:

CategoryWhat it includesWhere it comes from
AccountName, email address, a generated avatar colour and initials. If you sign in with GitHub: your GitHub numeric id, your GitHub username and the date you linked it, and your primary email only when GitHub reports it as verified. Your password is held by our sign-in service in hashed form; Ulika does not store it.You, when you register or sign in; GitHub, when you use Continue with GitHub.
Workspace and teamWorkspace name, members and their roles, and invitations (the invited email address; the invitation link itself is stored only as a hash).You and the people you invite.
GitHub connectionThe GitHub App installation id and account, the name, default branch and language of the repositories you select, and build and deployment results GitHub reports. Ulika reads the repository's source files as text, in memory, to find editable content, and does not keep a copy of the repository.GitHub, through the GitHub App installation you approve.
Site contentThe editable fields Ulika finds (text, links, image references and where they live in your source), your drafts, published releases and version history, collection items, page SEO data, and the analytics or pixel identifiers you enter. It can include personal data if your site contains it, such as a team member's name and photo.Your repository and what you type or upload.
MediaImages and videos you upload.You.
Hosting connectionIf you connect Vercel: an access token (stored encrypted), project and deployment identifiers, and the build variable, deploy hook, webhook and preview bypass secret Ulika creates (secrets stored encrypted or hashed).Vercel, through the connection you approve.
Command line and agent tokensA workspace or agent token, stored by Ulika only as a hash, plus the name and approval date. The command line also saves the token in a file on your own computer (see Cookies and similar technologies).You, when you approve a machine or an agent.
Website you checkThe web address you enter in the public website check, and the result of analysing that public site. If you then register, it is carried across in a signed cookie for 30 minutes.You.
EmailsYour email address and the messages we send you. If you subscribe to the newsletter on the landing page, your email address in a mailing list kept by our email provider.You.
Technical data and logsStandard request data processed by our hosting provider (such as IP address, browser and timestamps). Rate limits use the client address only in memory or as a hash, and the database holds no address. When a screen breaks, your browser can send an error report with the error message, stack trace, page path without query string, browser user agent and a short reference code, which we write to our server logs. Connection runs record events, outcomes and counters, never tokens, repository file contents or draft values.Your browser and our servers.

We do not intentionally collect sensitive personal data (for example health, racial origin, beliefs or biometric data) and ask you not to put it in content you connect to Ulika. Ulika is intended for people who are 18 or older.

Ulika does not currently send your content to any third-party AI or language-model provider. The assistant in the editor runs without one. If you use your own AI coding agent with the Ulika command line, that agent’s provider receives what you give it, under its own terms.

What we use it for

Primary purposes, which are necessary for the service you asked for:

  • creating and securing your account, signing you in, and managing your workspace, team and invitations;
  • connecting your GitHub repository and hosting project, finding editable content, storing drafts and versions, and publishing to your repository and site;
  • storing and serving your uploaded media;
  • sending service emails: account confirmation, password reset, invitations, and notices about your connections and publishes;
  • keeping the service secure and reliable: preventing abuse, applying rate limits, diagnosing errors and fixing bugs;
  • answering your requests and support questions, and complying with legal obligations.

Secondary purposes, which are not necessary for the service:

  • optional onboarding emails, such as a welcome note from the founder and a setup reminder, which you can switch off from the link in those emails or when you set up your workspace;
  • newsletter emails, if you subscribe on the landing page.

If you do not want your data used for the secondary purposes, tell us at legal@ulika.co or use the email preferences link. Declining never affects the service. We do not sell your personal data and we do not use it for advertising.

Processors and transfers

We use the following providers to run Ulika. They process personal data on our behalf (as processors, or encargados) and only to provide their service to us:

ProviderWhat it does for Ulika
SupabaseSign-in (accounts and password hashes), the Postgres database that stores your workspace, projects, content and connection records, private storage for uploaded media, and account emails such as confirmation and password reset.
VercelHosts the Ulika app and runs its scheduled jobs, and processes the standard request data and logs that come with hosting.
ResendSends our lifecycle and invitation emails and keeps the newsletter mailing list.

Two more services receive data because you connect them, and each acts under its own terms and privacy policy. When you tell Ulika to act on your GitHub or Vercel account, Ulika sends them what that action needs, such as a branch, a pull request, the content file you publish, or a build variable.

  • GitHub hosts your repositories, runs the GitHub App “Ulika CMS” and the GitHub sign-in, and sends Ulika webhooks.
  • Vercel, on your own account, hosts your site if you connect it.

The marketing pages stream background video from a content delivery network (Amazon CloudFront), which receives your IP address and browser details, as any web request does. Ulika sets no cookie through it.

These providers may process data outside Mexico, including in the United States. We do not transfer your personal data to anyone else, except where a competent authority requires it by law. If that changes, we will update this notice and, where the law requires it, ask for your consent first.

Cookies and similar technologies

Ulika uses only the cookies and browser storage it needs to work. It uses no advertising cookies, no analytics service and no third-party trackers of its own.

NamePurposeLifetime
ulika_authKeeps you signed in. Signed, HttpOnly cookie.Up to 14 days
ulika_workspaceRemembers which workspace you have open.Up to 14 days
ulika_return_toReturns you to the page you were heading to after registering.1 hour
ulika_site_checkCarries the result of the public website check across registration.30 minutes
ulika_github_stateProtects the GitHub round trip against forged requests.10 minutes
ulika_recoveryLets you finish a password reset.15 minutes
ulika-themeLocal storage: your light or dark preference.Until you clear it
ulika-docs-helpful:*Local storage: remembers your answer to “Was this helpful?” on a documentation page. Nothing is sent anywhere.Until you clear it
marketing-integrations:v1:*Session storage: keeps unsaved Integrations settings in the editor while the tab is open.Until the tab closes

When you open a protected preview inside the editor, Vercel can set its own bypass cookie for your deployment’s domain. The Ulika command line saves the token it receives in ~/.ulika/config.json on your computer, in a folder only you can use. ulika logout deletes it from that machine.

Security and retention

  • Long-lived secrets we must keep, such as a Vercel access token, are encrypted at rest. Command line, agent and build tokens are stored only as hashes and are never shown again.
  • Your repository is read in memory for one request and is not written to disk or kept as a copy.
  • Access is checked on the server against your role, and sign-in and invitation endpoints are rate limited.

No system is perfectly secure. We keep your personal data while your account is active and as long as needed to provide the service. Deleting a project removes its fields, drafts, versions, media records and delivery state. To delete your account and personal data, write to legal@ulika.co. We may keep what the law requires us to keep, and log data stays with the provider that holds it for that provider’s retention period. More detail is in the security overview.

Your rights (ARCO), consent and limiting use

You have the right to:

  • Access the personal data we hold about you and how we use it;
  • Rectify it if it is inaccurate or incomplete;
  • Cancel it, so that it is blocked and then deleted, when it is no longer needed or the law allows;
  • Oppose its use for specific purposes, including the secondary purposes above.

You can also revoke the consent you gave us, and ask us to limit the use or disclosure of your data. Revoking consent for something necessary to the service may mean we can no longer provide it, and it does not affect uses that were lawful before you revoked.

How to exercise them. Send an email to legal@ulika.co with the subject “ARCO request” (or “Revoke consent” or “Limit use”), from the email address of your Ulika account if you have one. Include your name, a clear description of the data and the right you want to exercise, and, for rectification, the correction and any proof of it. We may ask for something that proves your identity, or that of your representative. We will answer by email within the periods set by law and, if the request is accepted, carry it out within the period the law sets after that. Exercising your rights is free, though the law allows us to charge for justified delivery costs when you ask for copies.

If you think your rights were not respected, you can file a complaint with the authority in charge of personal data protection in Mexico, currently the Secretaría Anticorrupción y Buen Gobierno, or the authority that replaces it.

Changes to this notice

We may update this notice, for example when we add a feature or a provider. We will change the “Last updated” date at the top and tell you about material changes by email or inside the product. If a change introduces a new purpose that needs your consent, we will ask for it before using your data that way. Our Terms of Service also apply to your use of Ulika.

Contact

Questions about this notice or your data: legal@ulika.co.

© 2026 UlikaTerms of Service · Privacy Policy