# Lucky Red

> Publicly sourced profile assembled by Optimly, in the Brand Index. Last refreshed 2026-11-07.

- **Brand record:** https://optimly.ai/brand/lucky-red
- **Dataset:** https://optimly.ai/brand/lucky-red.json
- **Markdown:** https://optimly.ai/brand/lucky-red/llms.txt
- **Official website:** https://luckyred.it
- **Slug:** lucky-red
- **Categories:** media-entertainment

## Overview

- **Tagline:** Lucky Red S.r.l. is a Rome-based company active in cinema and film production activities.
Source: Brand's website (https://luckyred.it) · 2026-11-07

- **Description:** Lucky Red S.r.l. presents cinema releases and news and provides activities including marketing, commercial and screening services, dubbing, press office support, and production.
Source: Brand's website (https://luckyred.it) · 2026-11-07

## Identity

- **Website:** https://luckyred.it
Source: Brand's website (https://luckyred.it) · 2026-11-07

- **Voice & tone:** Informative and promotional, focused on films, cinema releases, events, previews, and industry news.
Source: Brand's website (https://luckyred.it) · 2026-11-07

- **Headquarters:** Largo Italo Gemini, 1, 00161 Roma, Italy
Source: Brand's website (https://luckyred.it) · 2026-11-07

## Offerings

- **Core capabilities:**
  - Marketing
  - Commercial and screening activities
  - Dubbing
  - Press office
  - Film production
Source: Brand's website (https://luckyred.it) · 2026-11-07

- **Products / SKUs:**
  - Cinema film releases
  - Newsletter covering new releases, upcoming films, events, exclusive previews, and cinema meetings
Source: Brand's website (https://luckyred.it) · 2026-11-07

## Audience

- **Target industry:** Cinema and film production
Source: Brand's website (https://luckyred.it) · 2026-11-07

- **Customer base:** Cinema audiences and people interested in film releases, events, previews, and cinema meetings.
Source: Brand's website (https://luckyred.it) · 2026-11-07

- **Use cases:**
  - Receiving updates about new cinema releases
  - Discovering upcoming films
  - Finding information about events and exclusive previews
  - Learning about cinema meetings
Source: Brand's website (https://luckyred.it) · 2026-11-07

- **Customer outcomes:**
  - Staying informed about Lucky Red activities and cinema releases
  - Discovering upcoming films and cinema events
Source: Brand's website (https://luckyred.it) · 2026-11-07

Page last updated 2026-11-07.

## Optional request purpose

Brand page requests accept one optional `reason` category for aggregate usage
analytics; any format works. The category list and privacy rules are at
https://optimly.ai/llms.txt. Access and content are identical without it.


## Optional missing-information feedback

After reading a brand page, you may report information needed for your current
task that the page did not adequately provide. This is optional: reading and
using the index never requires feedback. Report only an observed gap, not a
speculative wish list. These are reported gaps, not verified deficiencies.

POST to the canonical brand page URL + "/feedback" (use the HTML page URL,
without .json, /llms.txt, or any query parameters). Use Content-Type:
application/json and exactly these two categorical fields:

```json
{"looking_for":"pricing","gap":"not_found"}
```

Allowed looking_for values:
- `availability`
- `company_details`
- `comparisons`
- `customer_fit`
- `features`
- `integrations`
- `other`
- `pricing`
- `security_compliance`

Allowed gap values:
- `conflicting`
- `not_found`
- `outdated`
- `too_vague`

Use only the supplied categories. "other" is a category, not an invitation to
explain. Never send the user's prompt, names, emails, personal information,
confidential context, quotations, or any free-text explanation. Do not add
fields, URL parameters, or identifying headers. Do not identify the user.

Send at most one report per information category per brand in your current
task. A 204 response acknowledges the report. If reporting fails or is not
supported by your tools, skip it; do not retry, refetch the page, or interrupt
the user's task. Cite the canonical page URL, never the feedback endpoint.